mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, allen.lkml@gmail.com
Subject: Re: [PATCH 6.1 000/221] 6.1.77-rc2 review
Date: Sun, 4 Feb 2024 22:27:00 +0100	[thread overview]
Message-ID: <30066ce7-0f8a-40a7-b5b2-5494940c4cd5@o2.pl> (raw)
In-Reply-To: <20240203174756.358721205@linuxfoundation.org>

W dniu 3.02.2024 o 18:52, Greg Kroah-Hartman pisze:
> This is the start of the stable review cycle for the 6.1.77 release.
> There are 221 patches in this series, all will be posted as a response
> to this one.  If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Mon, 05 Feb 2024 17:47:20 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> 	https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.1.77-rc2.gz
> or in the git tree and branch at:
> 	git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Hello,

Tested-on a HP 17-by0001nw laptop with an Intel Kaby Lake CPU and Ubuntu 20.04.

Used technologies: ext4, vfat, mdraid on top of a NVMe and SATA drive (in a
write-mostly mode).

Suspend to disk and suspend to RAM work.

Nitpicks:

- the laptop once failed to shut down completely, it hung with a black screen
(the kernel messages from the shutdown disappeared). This did not happen again
with 2-3 tries. IIRC this has happened on this laptop in the past.

- I have been running long SMART tests on 2 external USB hard drives.
One of them, a TOSHIBA USB 3.0 hard drive briefly disconnected with the
following dmesg messages:

usb 2-2: USB disconnect, device number 4
xhci_hcd 0000:00:14.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
sd 2:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
sd 2:0:0:0: [sdc] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
device offline error, dev sdc, sector 263659521 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
Buffer I/O error on dev sdc2, logical block 1, lost async page write
sd 2:0:0:0: [sdc] Synchronizing SCSI cache
sd 2:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
usb 2-2: new SuperSpeed USB device number 5 using xhci_hcd

The hard drive was later reset out of the blue:

usb 2-1: reset SuperSpeed USB device number 7 using xhci_hcd

This may have been caused by faulty cabling / USB sockets.

Tested-by: Mateusz Jończyk <mat.jonczyk@o2.pl>

Greetings,

Mateusz Jończyk


  parent reply	other threads:[~2024-02-04 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-03 17:52 Greg Kroah-Hartman
2024-02-03 19:50 ` SeongJae Park
2024-02-03 21:27 ` Pavel Machek
2024-02-03 21:32 ` Florian Fainelli
2024-02-04 14:01 ` Yann Sionneau
2024-02-04 16:57 ` Naresh Kamboju
2024-02-04 17:06   ` Naresh Kamboju
2024-02-04 17:03 ` Naresh Kamboju
2024-02-04 21:27 ` Mateusz Jończyk [this message]
2024-02-05  9:20 ` Ron Economos
2024-02-05 10:03 ` Shreeya Patel
2024-02-05 13:18 ` Jon Hunter

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=30066ce7-0f8a-40a7-b5b2-5494940c4cd5@o2.pl \
    --to=mat.jonczyk@o2.pl \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®