From: Oliver Neukum <oneukum@suse.com>
To: djraszit <djraszit@gmail.com>, Michal Pecio <michal.pecio@gmail.com>
Cc: Oliver Neukum <oneukum@suse.com>,
Alan Stern <stern@rowland.harvard.edu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] uas: JMS578 returns reproducibly incorrect data after host reboot
Date: Mon, 12 Oct 2026 11:58:12 +0200 [thread overview]
Message-ID: <3cdb8068-7af2-4754-96f9-5177a09cc3bf@suse.com> (raw)
In-Reply-To: <CAFKhL9dYWLYhkj_687Out_hS3fxORgpCpggag2NwoVYbapyvYg@mail.gmail.com>
On 17.09.26 19:20, djraszit wrote:
> So the current comparison is:
>
> USB_MSD_PWR_OFF_TIME=1000, bus-powered Genesys:
> -> BAD-data after reboot
> -> invalid alternate GPT
> -> BAD direct-read hash
>
> USB_MSD_PWR_OFF_TIME=1000, externally powered Genesys:
> -> 5 consecutive reboots GOOD
>
> USB_MSD_PWR_OFF_TIME=0, VBUS supplied by the Pi:
> -> previously reproducible "Cannot enable" after consecutive reboots
>
> USB_MSD_PWR_OFF_TIME=0, externally powered Genesys:
> -> several consecutive reboots GOOD
Hi,
if we come back to this , is there anything the kernel can do,
even conceptually speaking?
Regards
Oliver
next prev parent reply other threads:[~2026-10-12 9:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFKhL9eUM91rtywaz_7Mz+4mJH2b2csmOmc3+86ii3a0Ka3Q6g@mail.gmail.com>
2026-09-14 8:00 ` Oliver Neukum
[not found] ` <CAFKhL9f6aLZgerw_7bohbQWvzMxSfd-m-LFcuNP1_p1vWkN4=Q@mail.gmail.com>
[not found] ` <1320caa3-85b5-47dc-aa2d-56d3b003c6ef@neukum.org>
2026-09-15 17:52 ` djraszit
2026-09-15 21:38 ` Michal Pecio
2026-09-16 17:56 ` djraszit
2026-09-16 18:47 ` Michal Pecio
2026-09-17 10:23 ` Oliver Neukum
2026-09-17 16:02 ` djraszit
2026-09-17 16:56 ` Michal Pecio
2026-09-17 17:20 ` djraszit
2026-10-12 9:58 ` Oliver Neukum [this message]
2026-09-13 14:39 djraszit
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=3cdb8068-7af2-4754-96f9-5177a09cc3bf@suse.com \
--to=oneukum@suse.com \
--cc=djraszit@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michal.pecio@gmail.com \
--cc=stern@rowland.harvard.edu \
/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®