Bug#958732: marked as done (linux-image-5.5.0-2-amd64: invalid opcode: 0000 [#1] SMP PTI kernel crash (stilll called an Oops?))

MP PTI kernel crash (stilll called an Oops?) 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 administrat

Bug#949369: marked as done (i915: kernel crash in i915_active_acquire())

Your message dated Thu, 20 Feb 2025 12:50:01 +0100 (CET) with message-id <20250220115001.e2b61be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #949369, regarding i915: kernel crash in i915_active_acquire() to be mar

Bug#976095: marked as done (linux-image-amd64: kernel crash refcount_t: underflow; use-after-free.)

Your message dated Wed, 19 Feb 2025 16:03:01 +0100 (CET) with message-id <20250219150301.5011dbe2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #976095, regarding linux-image-amd64: kernel crash refcount_t: underflo

Bug#1060066: marked as done (linux-image-6.1.0-17-amd64: kernel crash)

Your message dated Fri, 5 Jan 2024 21:00:54 +0100 with message-id and subject line Re: Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash) has caused the Debian Bug report #1060066, regarding linux-image-6.1.0-17-amd64: kernel crash to be marked as done. This means that you

Bug#1060066: Acknowledgement (linux-image-6.1.0-17-amd64: kernel crash)

Hello, Please close this case, false alarm, the debian/kernel is OK, appears to be an HW issue that needs a workaround. I've sent a note to linux-kernel@ Jan 5 06:18:52 atom kernel: [295306.524933] pcieport :00:06.0: AER: Corrected error received: :00:06.0 Jan 5 06:18:52 atom kernel: [2

Bug#1060066: linux-image-6.1.0-17-amd64: kernel crash

Package: linux-image-6.1.0-17-amd64 Distribution: Debian Stable Kernel: 6.1.0-17-amd64 I have reverted back to 6.1.0-16-amd64. Currently, I am not using a remote syslog server so the crash dump is in a picture: https://imgur.com/a/0ClFFOw Regards, Justin

Bug#1058991: marked as done (firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau)

Your message dated Tue, 19 Dec 2023 17:20:44 + with message-id and subject line Bug#1058991: fixed in firmware-nonfree 20230625-2 has caused the Debian Bug report #1058991, regarding firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau to be marked as

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Control: tag -1 +patch On dinsdag 19 december 2023 17:14:22 CET you wrote: > > If you manually create those links from the above "+Link:" lines, > > would that fix the issues? > > I've added only the ga107 symlinks (since this is what is needed > for my machine) with > ... > and this fixes all th

Processed: Re: Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Processing control commands: > tag -1 +patch Bug #1058991 [firmware-misc-nonfree] firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau Added tag(s) patch. -- 1058991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058991 Debian Bug Tracking Sys

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

On 2023-12-19 14:32:31 +0100, Diederik de Haas wrote: > If you manually create those links from the above "+Link:" lines, > would that fix the issues? I've added only the ga107 symlinks (since this is what is needed for my machine) with for i in acr nvdec sec2 do mkdir /usr/lib/firmware/nvidia/

Processed: Re: Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Processing control commands: > severity -1 important Bug #1058991 [firmware-misc-nonfree] firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau Severity set to 'important' from 'grave' > tag -1 moreinfo Bug #1058991 [firmware-m

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Control: severity -1 important Control: tag -1 moreinfo On Tuesday, 19 December 2023 13:57:51 CET Vincent Lefevre wrote: > Another piece of information: this is a regression. > > With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107" > gives > > Dec 19 04:57:07 qaa kernel: nouveau

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Another piece of information: this is a regression. With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107" gives Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: NVIDIA GA107 (b77000a1) Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: firmware: failed to load nvidia/ga107/nvdec/s

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

On 2023-12-19 04:32:02 +0100, Vincent Lefevre wrote: > firmware-misc-nonfree triggers the following warnings: > > update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64 [...] > W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin > for module nouveau [...] > while ht

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

Package: firmware-misc-nonfree Version: 20230625-1 Severity: grave Justification: renders package unusable firmware-misc-nonfree triggers the following warnings: update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for module

Bug#970557: marked as done (linux-image-5.8.0-1-amd64: kernel crash in nouveau)

Your message dated Fri, 22 Sep 2023 17:10:37 +0200 (CEST) with message-id <20230922151037.983c8be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #970557, regarding linux-image-5.8.0-1-amd64: kernel crash in nouveau

Bug#898336: hpwdt NMI kernel crash on shutdown/reboot

Just FYI, this bug still happens on the new Debian 12 Bookworm Alpha2, currently Debian Testing. Solution is the same as previously stated: Disable (blacklsit) hpwdt Kernel module.

Bug#928891: marked as done (linux-image-amd64: Kernel crash when using any disk that uses reiserfs)

Your message dated Sun, 27 Nov 2022 09:58:49 +0100 (CET) with message-id <20221127085849.b1945be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #928891, regarding linux-image-amd64: Kernel crash when using any disk tha

Bug#899301: marked as done (linux-image-4.16.0-1-amd64: kernel crash more times a month, irreproducibly, does not dump)

Your message dated Sat, 26 Nov 2022 20:45:38 +0100 (CET) with message-id <20221126194538.55263be2...@eldamar.lan> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #899301, regarding linux-image-4.16.0-1-amd64: kernel crash more times a

Processed: Re: Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Processing control commands: > found -1 4.9.88-1+deb9u1 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by samba Marked as found in versions linux/4.9.88-1+deb9u1. > notfound -1 4.9.88-1 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Control: found -1 4.9.88-1+deb9u1 Control: notfound -1 4.9.88-1 Hi Salvatore, On zondag 20 november 2022 16:38:25 CET Salvatore Bonaccorso wrote: > On Sun, Nov 20, 2022 at 04:26:45PM +0100, Diederik de Haas wrote: > > Control: notfound -1 4.9.88-1+deb9u1 > > Control: found -1 4.9.88-1 > > Hmm th

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Hi Diederik, On Sun, Nov 20, 2022 at 04:26:45PM +0100, Diederik de Haas wrote: > Control: notfound -1 4.9.88-1+deb9u1 > Control: found -1 4.9.88-1 Hmm this one I do not understand, as 4.9.88-1+deb9u1 was a very targetted fix for two CVEs and reverting the "random: fix crng_ready() test" changes r

Processed: Re: Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Processing control commands: > notfound -1 4.9.88-1+deb9u1 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by samba No longer marked as found in versions linux/4.9.88-1+deb9u1. > found -1 4.9.88-1 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems s

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Control: notfound -1 4.9.88-1+deb9u1 Control: found -1 4.9.88-1 On zondag 20 november 2022 13:55:09 CET Salvatore Bonaccorso wrote: > Seems the BSP was productive :). Yeah, once I set up the VM and created the script, it was actually quite easy. > If you have spare cycles, might you > check if d

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Hi, On Sun, Nov 20, 2022 at 12:30:53PM +0100, Diederik de Haas wrote: > Control: found -1 5.14.9-2 > Control: found -1 5.15.5-2 > Control: fixed -1 5.15.15-2 > Control: fixed -1 5.16.11-1 > Control: fixed -1 5.18.16-1 > Control: fixed -1 6.0.3-1 > > On zondag 20 november 2022 12:18:50 CET you wr

Processed: Re: Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Processing control commands: > found -1 5.14.9-2 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by samba Marked as found in versions linux/5.14.9-2. > found -1 5.15.5-2 Bug #900821 [src:linux] apache reads wrong data over cifs filesystems served by samba Marked as f

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Control: found -1 5.14.9-2 Control: found -1 5.15.5-2 Control: fixed -1 5.15.15-2 Control: fixed -1 5.16.11-1 Control: fixed -1 5.18.16-1 Control: fixed -1 6.0.3-1 On zondag 20 november 2022 12:18:50 CET you wrote: > Control: found -1 5.14.9-2 5.15.5-2 > Control: fixed -1 5.15.15-2 5.16.11-1 5.18

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Control: found -1 5.14.9-2 5.15.5-2 Control: fixed -1 5.15.15-2 5.16.11-1 5.18.16-1 6.0.3-1 On zaterdag 19 november 2022 21:22:46 CET Diederik de Haas wrote: > found 900821 5.10.70-1 > fixed 900821 5.10.84-1 I continued testing with kernels from backports and updated metadata accordingly. Inter

Bug#900821: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

intf "\nBug 900821 triggered! Calculated SHA256: %s\n" "$SHA256_CALC" exit 1 fi done printf "\nTest completed\n" ``` I tried it out on the installed kernel, 5.10.149-2 aka 5.10.0-19-amd64, and found out it all worked as expected. Idem ditt

Processed: Found working and failing 5.10 versions and got kernel crash, report from BSP Tilburg (https://deb.li/iiOID)

Processing commands for cont...@bugs.debian.org: > user debian-rele...@lists.debian.org Setting user to debian-rele...@lists.debian.org (was didi.deb...@cknow.org). > usertag 900821 + bsp-2022-11-nl-tilburg There were no usertags set. Usertags are now: bsp-2022-11-nl-tilburg. > found 900821 5.10.7

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Hi, I finally managed to identify the root cause of this issue and do have a patch and a more detailed description of the issue attched to the kernel bugtracker. The attached patch is applicable to stable (5.10.92) and experimental (5.17-rc4) kernels. As I did not receive any response to the o

Bug#781845: marked as done (linux-image-3.16.0-4-powerpc: kernel crash on powerpc)

Your message dated Sat, 16 Oct 2021 02:28:10 -0700 (PDT) with message-id <616a9b2a.1c69fb81.af1a0.3...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #781845, regarding linux-image-3.16.0-4-powerpc: kernel crash on powe

Bug#898336: hpwdt NMI kernel crash on shutdown/reboot 4.16.5-1~bpo9+1

I can confirm (somewhat) similar issues with the newest Debian 11 (Bullseye) and Kernel 5.10 on HP Proliant DL380 G7 servers. Boot does sometimes work, then it doesn't work (with a freeze caused by NMI), leading to a very unstable OS. After disabling hpwdt (module blacklist), the problems were gon

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

On 5/17/21 10:17 AM, Valentin Kleibel wrote: The bug has been reported upstream: linux-kernel: https://lkml.org/lkml/2021/4/13/672 linux-block: https://lore.kernel.org/linux-block/b6aea08d-7190-e341-8780-13ba8e015...@vrvis.at/T/#u kernel.org bugzilla: https://bugzilla.kernel.org/show_bug.cgi?

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Hello, Thanks for your help. The bug has been reported upstream: linux-kernel: https://lkml.org/lkml/2021/4/13/672 linux-block: https://lore.kernel.org/linux-block/b6aea08d-7190-e341-8780-13ba8e015...@vrvis.at/T/#u kernel.org bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=212665 After

Bug#839158: marked as done (linux-image-4.8.0-rc8-amd64-unsigned: Kernel crash randomly)

Your message dated Sat, 15 May 2021 02:17:17 -0700 (PDT) with message-id <609f919d.1c69fb81.14df.1...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #839158, regarding linux-image-4.8.0-rc8-amd64-unsigned: Kernel

Bug#796325: marked as done (linux-image-3.16-3-amd64: Kernel crash in skb_warn_bad_offload(?) since upgrading to 3.16.0-4-amd64)

Your message dated Sun, 09 May 2021 05:24:24 -0700 (PDT) with message-id <6097d478.1c69fb81.50ff6.b...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #796325, regarding linux-image-3.16-3-amd64: Kernel cr

Bug#988126: linux-image-4.9.0-15-amd64: kernel crash in update_group_capacity

Package: src:linux Version: 4.9.258-1 Severity: important Dear Maintainer, We have about 40 servers running the same operating system and this is the first time we see this crash in the kerneli (it happened the 05/04/2021, and never happened again, although the machine on which it appeared has

Bug#988125: linux-image-4.9.0-15-amd64: kernel crash in update_group_capacity

Package: src:linux Version: 4.9.258-1 Severity: important Tags: upstream Dear Maintainer, We have about 40 servers running the same operating system and this is the first time we see this crash in the kerneli (it happened the 05/04/2021, and never happened again, although the machine on which i

Bug#764377: marked as done (linux-image-3.2.0-4-686-pae: Kernel crash with tulip in the stack trace)

Your message dated Sun, 25 Apr 2021 11:59:10 -0700 (PDT) with message-id <6085bbfe.1c69fb81.769a9.2...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #764377, regarding linux-image-3.2.0-4-686-pae: Kernel crash with tu

Bug#758932: marked as done (udisksd: Disconnecting USB disk results in kernel crash)

Your message dated Sun, 25 Apr 2021 10:27:16 -0700 (PDT) with message-id <6085a674.1c69fb81.8e1c.a...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #758932, regarding udisksd: Disconnecting USB disk results in kernel cr

Bug#763192: closed by Salvatore Bonaccorso (Re: Bug#763192: [LXC] [nfsd] kernel crash when running nfs-kernel-server in one LXC Container)

Hi Jean-Marc, On Fri, Apr 23, 2021 at 09:23:35PM +0200, Jean-Marc LACROIX (jeanmarc.lacr...@free.fr) wrote: > > > Le 23/04/2021 à 20:27, Debian Bug Tracking System a écrit : > > This is an automatic notification regarding your Bug report > > which was filed against the src:linux package: > > >

Bug#763192: closed by Salvatore Bonaccorso (Re: Bug#763192: [LXC] [nfsd] kernel crash when running nfs-kernel-server in one LXC Container)

Le 23/04/2021 à 20:27, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the src:linux package: #763192: NFSv4 server recovery not supported in container It has been closed by Salvatore Bonaccorso . Their explanation is

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Hi $ ./scripts/get_maintainer.pl ./drivers/block/aoe/ Justin Sanders (supporter:ATA OVER ETHERNET (AOE) DRIVER) Jens Axboe (maintainer:BLOCK LAYER) linux-bl...@vger.kernel.org (open list:BLOCK LAYER) linux-ker...@vger.kernel.org (open list) Thanks for your help. The bug has been reported ups

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Hi Valentin, On Tue, Apr 13, 2021 at 01:42:49PM +0200, Valentin Kleibel wrote: > Hi Salvatore, > > > Thanks for the report. I assume you can reproduce the issue as well > > with 5.10.28-1 in unstable? > > I did not test this before as the aoe driver code was not changed at all in > the last 7 mo

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Hi Salvatore, Thanks for the report. I assume you can reproduce the issue as well with 5.10.28-1 in unstable? I did not test this before as the aoe driver code was not changed at all in the last 7 months. I can now report that the behavior is exactly the same running the kernel 5.10.0-6-amd6

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Hi Valentin, On Mon, Apr 12, 2021 at 06:40:53PM +0200, Valentin Kleibel wrote: > Package: linux-image-amd64 > Version: 5.10.26-1 > Source: linux > > Dear Maintainers, > > It seems we found a race condition in the aoe driver that leads to a kernel > crash. It is trigger

Bug#986837: aoe: kernel crash on blk_update_request: I/O error, BUG: scheduling while atomic

Package: linux-image-amd64 Version: 5.10.26-1 Source: linux Dear Maintainers, It seems we found a race condition in the aoe driver that leads to a kernel crash. It is triggered when an aoe device is unavailable and therefore produces an I/O error in the code that tries to remove the device

Processed: Re: linux-image-5.10.0-5-armmp-lpae: LTP causes kernel crash

Processing control commands: > found -1 5.10.26-1 Bug #986326 [src:linux] linux-image-5.10.0-5-armmp-lpae: LTP causes kernel crash Marked as found in versions linux/5.10.26-1. > tags -1 + sid Bug #986326 [src:linux] linux-image-5.10.0-5-armmp-lpae: LTP causes kernel crash Added tag(

Bug#976095: linux-image-amd64: kernel crash refcount_t: underflow; use-after-free.

Hi Xavier, On Sun, Dec 06, 2020 at 08:35:57PM +0100, Xavier Chantry wrote: > I just tested 5.9.6-1~bpo10+1 from buster-backports and it seems to work, > thanks ! But then your and the referenced issue should be two different issues? The nouveau issue you referenced was only fixed in 5.9.9-1, did

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

...and my (probably) final report to this mailing list: The most recent crashes/hangs I experienced have no relation to Debian release or Linux kernel, but most likely a hardware issue. I initially experienced a crash similar to what the original report in this bug-thread showed. Suspecting th

Bug#976095: linux-image-amd64: kernel crash refcount_t: underflow; use-after-free.

I just tested 5.9.6-1~bpo10+1 from buster-backports and it seems to work, thanks ! On Thu, Dec 3, 2020 at 11:33 PM Salvatore Bonaccorso wrote: > Hi Xavier, > > On Sun, Nov 29, 2020 at 06:32:36PM +0100, Xavier Chantry wrote: > > Package: linux-image-amd64 > > Version: 5.8.10-1~bpo10+1 > > Severit

Bug#976095: linux-image-amd64: kernel crash refcount_t: underflow; use-after-free.

Hi Xavier, On Sun, Nov 29, 2020 at 06:32:36PM +0100, Xavier Chantry wrote: > Package: linux-image-amd64 > Version: 5.8.10-1~bpo10+1 > Severity: important > > Version 5.8.10-1~bpo10+1 contains a critical bug that completely freezes the > system with a very basic LibreOffice usage. > This is appare

Bug#976095: linux-image-amd64: kernel crash refcount_t: underflow; use-after-free.

Package: linux-image-amd64 Version: 5.8.10-1~bpo10+1 Severity: important Version 5.8.10-1~bpo10+1 contains a critical bug that completely freezes the system with a very basic LibreOffice usage. This is apparently fixed here : https://www.mail-archive.com/nouveau@lists.freedesktop.org/msg36460.html

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

Unfortunately, my machine crashed again last night. No special activity, no stressing things going on - just full 100% standstill. Nothing visible in either syslog or kern.log. On screen just the regular login prompt (no GUI, just terminal login) but the cursor was absent and the system didn't

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

i upgraded myself today to 4.19.0-12 (or 4.19.152-1 according to upstream version numbers) no issue yet. this blog contains some interesting info: http://blog.pi3.com.pl/?p=720 both CVE's mentioned are fixed now in debian https://security-tracker.debian.org/tracker/CVE-2020-25220 https://securit

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

Unfortunately I'm not 100% convinced yet. I suffered from hangs with the 4.19.0-10 kernel; on 4.19.0-11 I got at least a similar warning message on screen (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968335#27), and last saturday I also got a completely hanging system - without any f

Bug#968335: kernel crash: WARNING: CPU: 0 PID: 0 at lib/percpu-refcount.c:155 percpu_ref_switch_to_atomic_rcu+0xf8/0x120

screenshot I made of a kernel crash ~3 weeks ago showed the same message as in the original bug report. With the new hardware, I suffered from a crash this weekend (still the 4.19.0-10-amd64 kernel). I wasn't able to reproduce the issue at will - it just happened randomly, it seems. But

Processed: kernel crash in nouveau

Processing control commands: > found -1 5.8.10-1 Bug #970557 [src:linux] linux-image-5.8.0-1-amd64: kernel crash in nouveau Marked as found in versions linux/5.8.10-1. -- 970557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970557 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#970557: kernel crash in nouveau

Control: found -1 5.8.10-1 On 2020-09-18 18:07:35 +0200, Vincent Lefevre wrote: > Package: src:linux > Version: 5.8.7-1 > Severity: important > > A short time after updating the kernel and rebooted, the kernel > crashed in nouveau while I wasn't using the machine (I only had > an ssh session). D

Bug#970557: linux-image-5.8.0-1-amd64: kernel crash in nouveau

Package: src:linux Version: 5.8.7-1 Severity: important A short time after updating the kernel and rebooted, the kernel crashed in nouveau while I wasn't using the machine (I only had an ssh session). Sep 18 17:56:26 ypig kernel: [ 1445.181686] [ cut here ] Sep 18 17:56:26

Bug#958732: linux-image-5.5.0-2-amd64: invalid opcode: 0000 [#1] SMP PTI kernel crash (stilll called an Oops?)

Package: src:linux Version: 5.5.17-1 Severity: normal Kernel crash: Apr 24 12:58:24 shelf kernel: [ 8109.802668] [ cut here ] Apr 24 12:58:24 shelf kernel: [ 8109.802673] invalid opcode: [#1] SMP PTI Apr 24 12:58:24 shelf kernel: [ 8109.802676] CPU: 4 PID: 5665

Bug#949369: Info received (Bug#949369: i915: kernel crash in i915_active_acquire())

@John try to install Linux Kernel 5.5.13 (aka 5.5.0-1) from sid https://packages.debian.org/sid/kernel/linux-image-5.5.0-1-amd64-unsigned https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.12/CHANGES Chris Wilson (1): drm/i915/execlists: Track active elements during dequeue Matt Rope

Bug#949369: i915: kernel crash in i915_active_acquire()

FYI My bug report https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868551 I ported the patch https://launchpadlibrarian.net/470860672/ubuntu-focal-1868551-i915_active_acquire.patch Official Issue #827 https://gitlab.freedesktop.org/drm/intel/issues/827 Good article on the subject https://li

Bug#949369: i915: kernel crash in i915_active_acquire()

Seen today with 5.4.19-1 (sid) on Intel HD 630 Graphics (i7 7700). Console nonrecoverable but system up and could be mostly shut down via remote access. Oops attached. Kind regards, -- Ben Caradoc-Davies Director Transient Software Limited New Zealand Mar 13 10:57:33 r

Bug#949369: i915: kernel crash in i915_active_acquire()

See also similar report and discussion and patch here: https://gitlab.freedesktop.org/drm/intel/issues/827 Especially the remark "obj->frontbuffer is no longer protected by the struct_mutex". Are they the upstream? I do not know if this is exactly the same bug as reported here, or whether the

Bug#949369: i915: kernel crash in i915_active_acquire()

On 13/03/2020 11:37, Ben Caradoc-Davies wrote: Seen today with 5.4.19-1 (sid) on Intel HD 630 Graphics (i7 7700). Console nonrecoverable but system up and could be mostly shut down via remote access. Oops attached. Note: no Nvidia hardware or drivers present. This is an IGP-only system. -- Be

Bug#949369: i915: kernel crash in i915_active_acquire()

Source: linux Followup-For: Bug #949369 Dear Maintainer, I experienced the same crash after upgrading to kernel series 5.4.x (namely to 5.4.8) in mid of January. The crashes of the system were quite frequent (every few hours, making the system unusable). After few experiments I ended up with

Bug#949369: i915: kernel crash in i915_active_acquire()

Dear maintainers, I experienced the same crash today. I have the Lenovo t470p with the i915 (Intel HD 630 graphics) and the NVIDIA 940MX dedicated graphics card. I statically switch between intel and nvidia with xrandr and sddm scrpts (using https://wiki.debian.org/NvidiaGraphicsDrivers/Optim

Bug#949369: i915: kernel crash in i915_active_acquire()

ers, thanks for your hard work with the linux package, it is > > really appreciated. > > > > I had this kernel crash today that let the system unusable. > [...] > > Is this reproducible without the Nvidia proprietary driver? > I was unable to reproduce the issue even witho

Processed: Re: Bug#949369: i915: kernel crash in i915_active_acquire()

Processing control commands: > tag -1 moreinfo Bug #949369 [src:linux] i915: kernel crash in i915_active_acquire() Added tag(s) moreinfo. -- 949369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949369 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#949369: i915: kernel crash in i915_active_acquire()

Control: tag -1 moreinfo On Mon, 2020-01-20 at 11:03 +0100, Arturo Borrero Gonzalez wrote: > Source: linux > Version: 5.4.8-1 > Severity: normal > Tags: upstream > > Dear maintainers, thanks for your hard work with the linux package, it is > really appreciated. > > I

Bug#949369: i915: kernel crash in i915_active_acquire()

Source: linux Version: 5.4.8-1 Severity: normal Tags: upstream Dear maintainers, thanks for your hard work with the linux package, it is really appreciated. I had this kernel crash today that let the system unusable. kernel: [ 973.595610] #PF: supervisor read access in kernel mode kernel

Processed: debian xen kernel crash

Processing commands for cont...@bugs.debian.org: > submitter 944612 ! Bug #944612 [src:linux] linux-image-5.2.0-3-amd64: netdev watchdog triggers on xen with different nics leading to different failures Changed Bug submitter to 'Alexander Dahl ' from 'Alexander Dahl '. > submitter 944618 ! Bug #

Bug#928891: linux-image-amd64: Kernel crash when using any disk that uses reiserfs

On Sun, 2019-05-12 at 18:34 +0200, Thanatermesis wrote: > Package: linux-image-amd64 > Version: 4.19+104 > Severity: important > > Dear Maintainer, > > When using any partition which uses reiserfs, the kernel crashes > > This happens very easily by just using the reiser (v3) filesystem, some > o

Bug#928891: linux-image-amd64: Kernel crash when using any disk that uses reiserfs

Package: linux-image-amd64 Version: 4.19+104 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Dear Maintainer, When using any partition which uses reiserfs, the kernel crashes This happens very easily by just using the reiser (v3) filesystem, some of my external hard disks us

Bug#921542: marked as done (tc qdisc kernel crash)

Your message dated Tue, 12 Mar 2019 18:00:11 + with message-id and subject line Bug#921542: fixed in linux 4.19.28-1 has caused the Debian Bug report #921542, regarding tc qdisc kernel crash to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#921542: tc qdisc kernel crash

On Sun, Feb 10, 2019 at 7:54 AM Ben Hutchings wrote: > > Control: tag -1 confirmed upstream > Control: found -1 4.20-1~exp1 > > Adrian (cc'd) reported (https://bugs.debian.org/921542) that a script > using tc could trigger a kernel crash. I've simplified the

Bug#921542: tc qdisc kernel crash

Control: tag -1 confirmed upstream Control: found -1 4.20-1~exp1 Adrian (cc'd) reported (https://bugs.debian.org/921542) that a script using tc could trigger a kernel crash. I've simplified the script he provided down to: --- BEGIN --- #!/bin/sh -ex modprobe ifb while true; do

Processed: Re: tc qdisc kernel crash

Processing control commands: > tag -1 confirmed upstream Bug #921542 [src:linux] tc qdisc kernel crash Added tag(s) upstream and confirmed. > found -1 4.20-1~exp1 Bug #921542 [src:linux] tc qdisc kernel crash Marked as found in versions linux/4.20-1~exp1. -- 921542: https://bugs.debian.o

Bug#921542: tc qdisc kernel crash

dd qdisc on leaf parent 2:5 ${ifaceIn} as SFQ" tc qdisc add dev $ifaceIn parent 2:5 sfq echo "Add filter on parent 2:0 ${ifaceIn} to match DSCP BE (ToS 0x0 / DSCP 0x0 mark) and send the traffic to class 2:5" tc filter add dev $ifaceIn parent 2:0 protocol ip prio 5 handle 0 tcindex ma

Bug#899301: linux-image-4.16.0-1-amd64: kernel crash more times a month, irreproducibly, does not dump

Package: src:linux Version: 4.16.5-1 Severity: important Dear Maintainer, kernel crashes in different conditions, sometimes while I am not using the laptop. I did a full scan of the memories several times and all seems fine. I did not manage to obtain a crash log either, My configuration is: root

Bug#884069: marked as done (Kernel crash on boot on IBM BladeCenter HS22)

Your message dated Thu, 14 Dec 2017 17:32:32 + with message-id and subject line Bug#883938: fixed in linux 3.16.51-3 has caused the Debian Bug report #883938, regarding Kernel crash on boot on IBM BladeCenter HS22 to be marked as done. This means that you claim that the problem has been

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

On Mon, 11 Dec 2017 08:37:30 +0100 Bernhard Schmidt wrote: > Control: severity -1 critical > Same issue for us with Dell PowerEdge R630. Regards, Thomas

Processed: Re: Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

Processing control commands: > severity -1 critical Bug #884069 [linux-image-3.16.0-4-amd64] Kernel crash on boot on IBM BladeCenter HS22 Severity set to 'critical' from 'normal' -- 884069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884069 Debian Bug Tra

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

Control: severity -1 critical On Mon, Dec 11, 2017 at 09:14:27AM +0200, Rolandas Naujikas wrote: Hi, > Package: linux-image-3.16.0-4-amd64 > Version: 3.16.51-2 > > Loading Linux 3.16.0-4-amd64 ... > Loading initial ramdisk ... > [0.604128] general protection fault: [#1] SMP > [0.60

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

Package: linux-image-3.16.0-4-amd64 Version: 3.16.51-2 Loading Linux 3.16.0-4-amd64 ... Loading initial ramdisk ... [0.604128] general protection fault: [#1] SMP [0.609303] Modules linked in: [0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW 3.16.0-4-amd64 #1 Debian 3.1

Bug#877809: marked as done (libreoffice writer java kernel crash)

Your message dated Fri, 01 Dec 2017 19:00:12 + with message-id and subject line Bug#865303: fixed in linux 4.14.2-1 has caused the Debian Bug report #865303, regarding libreoffice writer java kernel crash to be marked as done. This means that you claim that the problem has been dealt with

Bug#877809: libreoffice writer java kernel crash

able (2 bugs) #876051 [i|+|☣] [openjdk-8-jre-headless] i386 applications using JNI may crash due to Hotspot workaround for Exec Shield #876069 [i|+|☣] [openjdk-9-jre-headless] i386 applications using JNI may crash due to Hotspot workaround for Exec Shield directly on the top You yourself say "libr

Processed: Re: Bug#877809: libreoffice writer java kernel crash

Processing commands for cont...@bugs.debian.org: > reassign 877809 src:linux Bug #877809 [libreoffice] libreoffice writer java kernel crash Bug reassigned from package 'libreoffice' to 'src:linux'. No longer marked as found in versions libreoffice/1:5.4.1-1. Ignoring

Bug#837200: marked as done (linux-image-3.16.0-4-amd64: kernel crash: /build/linux-7z1rSb/linux-3.16.7-ckt25/net/sched/sch_generic.c:264 dev_watchdog+0x236/0x240())

Your message dated Sat, 10 Dec 2016 13:28:04 +0100 with message-id <8142821.uYxR0jVBiI@bagend> and subject line Likely hardware failure has caused the Debian Bug report #837200, regarding linux-image-3.16.0-4-amd64: kernel crash: /build/linux-7z1rSb/linux-3.16.7-ckt25/net/sched/sch_generic

Bug#839158: linux-image-4.8.0-rc8-amd64-unsigned: Kernel crash randomly

Package: src:linux Version: 4.8~rc8-1~exp1 Severity: normal Dear Maintainer, Randomly my kernel crash : Sep 29 17:11:59 debian org.gtk.vfs.Daemon[3071]: A connection to the bus can't be made Sep 29 17:11:59 debian gnome-session[3075]: Unable to init server: Could not connect: Connection re

Bug#837200: linux-image-3.16.0-4-amd64: kernel crash: /build/linux-7z1rSb/linux-3.16.7-ckt25/net/sched/sch_generic.c:264 dev_watchdog+0x236/0x240()

Package: src:linux Version: 3.16.36-1+deb8u1 Severity: important After the latest kernel upgrade I've now had 2 kernel crashes and on first look they seem rather similar and I don't recall that I got them before the kernel update of 03 Sep 2016, so it is likely that that change introduced it. Be

Bug#828973: marked as done (Kernel crash with older QLogic Fibre Channel cards)

Your message dated Wed, 31 Aug 2016 06:50:18 +0200 with message-id and subject line Re: Bug#828973: Acknowledgement (Kernel crash with older QLogic Fibre Channel cards) has caused the Debian Bug report #828973, regarding Kernel crash with older QLogic Fibre Channel cards to be marked as done

Bug#828973: Kernel crash with older QLogic Fibre Channel cards

Package: linux-image-4.6.0-1-amd64 Version: 4.6.2-2 Kernel crashes as soon as qla2xxx driver is loaded (and using older QLogic Fibre Channel card without MSI-X support). This was already reported in Ubuntu [1] and LKML [2]. There is a very simple patch available on LKML. The author of the patch wa

Re: [PATCH] Fix hppa kernel crash at boot in block/blk-merge.c

Hi Ben, On 14.04.2016 00:48, Ben Hutchings wrote: > On Thu, 2016-03-10 at 18:23 +0100, Helge Deller wrote: >> Since kernel 4.3 we have a problem on hppa that it crashes at bootup >> during the SCSI drive detection. >> There are multiple threads about this issue and this link is maybe a good >> st

Re: [PATCH] Fix hppa kernel crash at boot in block/blk-merge.c

On Thu, 2016-03-10 at 18:23 +0100, Helge Deller wrote: > Since kernel 4.3 we have a problem on hppa that it crashes at bootup > during the SCSI drive detection. > There are multiple threads about this issue and this link is maybe a good > start: > https://patchwork.kernel.org/patch/8402441/. > >

[PATCH] Fix hppa kernel crash at boot in block/blk-merge.c

miscompiles this function at O2, leading to a kernel crash at bootup. +* So, let's temporarily compile this function with O1 until the bug is fully analyzed and fixed. +*/ + __attribute__ ((optimize("O1"))) +#endif +blk_b

Bug#604817: marked as done (udev-acl: Start after hibernate cause kernel crash)

Your message dated Sun, 07 Feb 2016 22:43:07 + with message-id and subject line Closing bugs assigned to linux-2.6 package has caused the Debian Bug report #604817, regarding udev-acl: Start after hibernate cause kernel crash to be marked as done. This means that you claim that the problem

Bug#796325: linux-image-3.16-3-amd64: Kernel crash in skb_warn_bad_offload(?) since upgrading to 3.16.0-4-amd64

Package: src:linux Version: 3.16.5-1 Severity: normal Dear Maintainer, on 2015-08-13 I rebooted this computer to update the Kernel from 3.16-3 to 3.16.0-4. Since then I have from 200 to 2000 Events of these kind a day. This is the trace from the logs: Aug 21 06:27:36 node2 kernel: [1106326.225

  1   2   3   4   >