Subject: Re: Bug Report with kernel 6.3.5

From: Bagas Sanjaya <[email-masked]>
Date: Thu, 29 Jun 2023 18:29:15 +0700

On Sun, Jun 04, 2023 at 12:42:25PM +0700, Bagas Sanjaya wrote:
> On Sun, Jun 04, 2023 at 07:51:36AM +0300, Martin Zaharinov wrote:
> > Hi Team one bug report 
> > 
> > after upgrade from kernel 6.2.12 to 6.3.5 
> > After fell hour system get this error.
> > 
> > If is possible to check.
> > 
> > 
> > Jun  4 01:46:52  [12810.275218][  T587] INFO: task nginx:3977 blocked for more than 609 seconds.
> > Jun  4 01:46:52  [12810.275350][  T587]       Tainted: G           O       6.3.5 #1
> > Jun  4 01:46:52  [12810.275436][  T587] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> > Jun  4 01:46:52  [12810.275527][  T587] task:nginx         state:D stack:0     pid:3977  ppid:1      flags:0x00000006
> > Jun  4 01:46:52  [12810.275624][  T587] Call Trace:
> > Jun  4 01:46:52  [12810.275707][  T587]  <TASK>
> > Jun  4 01:46:52  [12810.275786][  T587]  __schedule+0x352/0x820
> > Jun  4 01:46:52  [12810.275878][  T587]  schedule_preempt_disabled+0x61/0xe0
> > Jun  4 01:46:52  [12810.275963][  T587]  __mutex_lock.constprop.0+0x481/0x7a0
> > Jun  4 01:46:52  [12810.276049][  T587]  ? __lock_sock_fast+0x1a/0xc0
> > Jun  4 01:46:52  [12810.276135][  T587]  ? lock_sock_nested+0x1a/0xc0
> > Jun  4 01:46:52  [12810.276217][  T587]  ? inode_wait_for_writeback+0x77/0xd0
> > Jun  4 01:46:52  [12810.276307][  T587]  eventpoll_release_file+0x41/0x90
> > Jun  4 01:46:52  [12810.276416][  T587]  __fput+0x1d9/0x240
> > Jun  4 01:46:52  [12810.276517][  T587]  task_work_run+0x51/0x80
> > Jun  4 01:46:52  [12810.276624][  T587]  exit_to_user_mode_prepare+0x123/0x130
> > Jun  4 01:46:52  [12810.276732][  T587]  syscall_exit_to_user_mode+0x21/0x110
> > Jun  4 01:46:52  [12810.276847][  T587]  entry_SYSCALL_64_after_hwframe+0x46/0xb0
> > Jun  4 01:46:52  [12810.276954][  T587] RIP: 0033:0x15037529155a
> > Jun  4 01:46:52  [12810.277056][  T587] RSP: 002b:000015036bbb6400 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
> > Jun  4 01:46:52  [12810.277185][  T587] RAX: 0000000000000000 RBX: 000015036bbb7420 RCX: 000015037529155a
> > Jun  4 01:46:52  [12810.277311][  T587] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000013
> > Jun  4 01:46:52  [12810.277440][  T587] RBP: 00001503647343d0 R08: 1999999999999999 R09: 0000000000000000
> > Jun  4 01:46:52  [12810.277567][  T587] R10: 000015037531baa0 R11: 0000000000000293 R12: 0000000000000ba5
> > Jun  4 01:46:52  [12810.277693][  T587] R13: 0000150348731f48 R14: 0000000000000000 R15: 000000001f5b06b0
> > Jun  4 01:46:52  [12810.277820][  T587]  </TASK>
> > 
> 
> Can you clearly describe this regression? And your nginx setup? And most
> importantly, can you please bisect between v6.2 and v6.3 to find the
> culprit? Can you also check the mainline?
> 
> Anyway, thanks for the regression report. I'm adding it to regzbot:
> 
> #regzbot ^introduced: v6.2.12..v6.3.5
> #regzbot title: nginx blocked for more than 10 minutes on 6.3.5
> 

No reply from Martin (MIA), thus removing from regzbot tracking:

#regzbot inconclusive: reporter MIA when being asked to provide regression details

Thanks.

-- 
An old man doll... just what I always wanted! - Clara