Linux-ide Archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux IDE and libata <linux-ide@vger.kernel.org>
Cc: Damien Le Moal <dlemoal@kernel.org>,
	Hannes Reinecke <hare@suse.de>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Tejun Heo <tj@kernel.org>,
	Totallyreal Name <kotversuchung@gmail.com>,
	loqs <kernel_bugzilla@entropy-collector.net>
Subject: Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty" shutdown
Date: Wed, 25 Oct 2023 07:40:11 +0700	[thread overview]
Message-ID: <cd397c88-bf53-4768-9ab8-9d107df9e613@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla that seems to have been
handled already there [1]. Quoting from it:

> I have noticed that after each shutdown SMART would log +1 on each raw_value of drives that count power related issues.
> 
> Here are some of the smart values where i noticed increase among different drives
> 
> POR_Recovery_Count 
> Unexpect_Power_Loss_Ct  
> Power-Off_Retract_Count 
> 
> That doesn't happen on previous Kernels.. and it stops as soon as i switch back to LTS.
> I seeked through the Bug Reports but couldn't really find the issue. So i don't know if this has been reported or patched already.

Another reporter had found the culprit:

> 
> 
> This has been reported as being introduced in stable 6.5.8 [1].  Reverting commit 	bbbf096ea227607cbb348155eeda7af71af1a35b is reported to solve the issue [2]. bbbf096ea227607cbb348155eeda7af71af1a35b [3] is mainline commit aa3998dbeb3abce63653b7f6d4542e7dcd022590 [4] which was introduced in 6.6-rc4 which matches the original report.
> 
> [1]: https://bugs.archlinux.org/task/80064
> [2]: https://bugs.archlinux.org/task/80064#comment223100
> [3]: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=bbbf096ea227607cbb348155eeda7af71af1a35b
> [4]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aa3998dbeb3abce63653b7f6d4542e7dcd022590

See Bugzilla for the full thread.

Anyway, I'm adding this regression to regzbot:

#regzbot introduced: aa3998dbeb3abc https://bugzilla.kernel.org/show_bug.cgi?id=218038
#regzbot title: dirty shutdown due to disabling manage_system_start_stop on SCSI devices
#regzbot link: https://bugs.archlinux.org/task/80064

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218038

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

             reply	other threads:[~2023-10-25  0:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-25  0:40 Bagas Sanjaya [this message]
2023-10-25  2:11 ` Fwd: bbbf096ea227607cbb348155eeda7af71af1a35b results in "dirty" shutdown Damien Le Moal
2023-10-27  7:41 ` Damien Le Moal
2023-10-27  8:08   ` Linux regression tracking (Thorsten Leemhuis)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cd397c88-bf53-4768-9ab8-9d107df9e613@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=dlemoal@kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=hare@suse.de \
    --cc=kernel_bugzilla@entropy-collector.net \
    --cc=kotversuchung@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=regressions@lists.linux.dev \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).