From: Isaac Manjarres <isaacmanjarres@google.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Saravana Kannan <saravanak@google.com>,
stable@kernel.org, kernel-team@android.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] driver core: Fix bus_type.match() error handling
Date: Thu, 18 Aug 2022 17:38:15 -0700 [thread overview]
Message-ID: <Yv7bd6Yl8+thp2CY@google.com> (raw)
In-Reply-To: <20220818225932.GA3433999@roeck-us.net>
On Thu, Aug 18, 2022 at 03:59:32PM -0700, Guenter Roeck wrote:
> Requesting system reboot
> sd 0:0:0:0: [sda] Synchronizing SCSI cache
> ci_hdrc ci_hdrc.1: remove, state 4
> usb usb2: USB disconnect, device number 1
> ci_hdrc ci_hdrc.1: USB bus 2 deregistered
> ci_hdrc ci_hdrc.0: remove, state 1
> usb usb1: USB disconnect, device number 1
> usb 1-1: USB disconnect, device number 2
> sd 0:0:0:0: [sda] Synchronizing SCSI cache
> sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=DRIVER_OK
>
> [ stuck here until qemu is killed ]
>
Hi Guenter,
I'm actually observing the behavior described above even without my patch.
The tip of my tree is currently at 573ae4f13f63 ("tee: add overflow check in
register_shm_helper()"). I used git bisect to find what commit was
causing the problem, and narrowed it down to this series[1].
I reverted all 4 patches in that series, and I no longer see this hang
with my tree.
[1]: https://lore.kernel.org/all/20220712221936.1199196-1-bvanassche@acm.org/
Are these patches part of the tree you're using for testing and
observing this hang in?
Thanks,
Isaac
next prev parent reply other threads:[~2022-08-19 0:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20220815211927eucas1p275ed3f63f1baf76b319a828c214c651f@eucas1p2.samsung.com>
2022-08-15 21:19 ` [PATCH v2] driver core: Fix bus_type.match() error handling Isaac J. Manjarres
2022-08-16 4:25 ` Guenter Roeck
2022-08-16 5:17 ` Isaac Manjarres
2022-08-16 11:13 ` Guenter Roeck
2022-08-16 17:13 ` Isaac Manjarres
2022-08-17 1:05 ` Guenter Roeck
2022-08-17 1:12 ` Isaac Manjarres
2022-08-18 22:59 ` Guenter Roeck
2022-08-19 0:38 ` Isaac Manjarres [this message]
2022-08-19 11:28 ` Guenter Roeck
2022-08-19 17:45 ` Isaac Manjarres
2022-08-19 20:01 ` Bart Van Assche
2022-08-19 20:55 ` Guenter Roeck
2022-08-19 22:08 ` Guenter Roeck
2022-08-20 0:07 ` Bart Van Assche
2022-08-20 11:48 ` Guenter Roeck
2022-08-21 21:39 ` Bart Van Assche
2022-08-25 9:22 ` Marek Szyprowski
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=Yv7bd6Yl8+thp2CY@google.com \
--to=isaacmanjarres@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=m.szyprowski@samsung.com \
--cc=rafael@kernel.org \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=saravanak@google.com \
--cc=stable@kernel.org \
--cc=tomeu.vizoso@collabora.com \
--cc=ulf.hansson@linaro.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