Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #85002 > unrolled thread

Bug#1091893: linux-image-6.1.0-28-amd64: Watchdog detected hard LOCKUP on CPU 8, then CPU 0

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1091893: linux-image-6.1.0-28-amd64: Watchdog detected hard LOCKUP on CPU 8, then CPU 0 Salvatore Bonaccorso <carnil@debian.org> - 2025-01-02 07:30 +0100
    Processed: Re: Bug#1091893: linux-image-6.1.0-28-amd64: Watchdog  detected hard LOCKUP on CPU 8, then CPU 0 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-01-02 07:30 +0100

#85002 — Bug#1091893: linux-image-6.1.0-28-amd64: Watchdog detected hard LOCKUP on CPU 8, then CPU 0

Control: tags -1 + moreinfo
Control: severity -1 important

Hi,

On Wed, Jan 01, 2025 at 11:18:37PM -0500, Neal Murphy wrote:
> Package: src:linux
> Version: 6.1.119-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> I plugged in my SSK NVME-to-USB3 adapter. I mounted it, checked it (without
> writing anything), and unmounted it. The system displayed the '... has data to
> be written ...' msg for quite a while. Around then, the system displayed the
> watchdog error on CPU 8. Shortly after, it displayed a watchdog error on CPU 0
> and the system became unresponsive requiring a hard reset.
> 
> When I got the SSK, it worked well on the desktop. Months later, I had problems
> with it, but didn't get any kernel oopses. The drive works OK on my Asus
> laptop, so I'm beginning to suspect my desktop's hardware.
> 
> I'm reporting this because flaky hardware usually shouldn't cause a system
> lockup.

Assuming you as well cannot access anymore the system remotely try to
reproduce it and forward e.g. the kernel logs by means of netconsole
to another host.

Can you please attach this kernel log then to this report.

Can you reproduce the issue as well with more recent stable series
versions? Can you try 6.12.6-1 from unstable as well.

Regards,
Salvatore

[toc] | [next] | [standalone]

#85003 — Processed: Re: Bug#1091893: linux-image-6.1.0-28-amd64: Watchdog detected hard LOCKUP on CPU 8, then CPU 0

Processing control commands:

> tags -1 + moreinfo
Bug #1091893 [src:linux] linux-image-6.1.0-28-amd64: Watchdog detected hard LOCKUP on CPU 8, then CPU 0
Added tag(s) moreinfo.
> severity -1 important
Bug #1091893 [src:linux] linux-image-6.1.0-28-amd64: Watchdog detected hard LOCKUP on CPU 8, then CPU 0
Ignoring request to change severity of Bug 1091893 to the same value.

-- 
1091893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1091893
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web