From: Julian Wollrath <jwollrath@web.de>
To: Borislav Petkov <bp@alien8.de>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Oops with v6.6-rc6+
Date: Sun, 22 Oct 2023 20:18:03 +0200 [thread overview]
Message-ID: <20231022201803.41b8df95@mayene> (raw)
In-Reply-To: <20231022172240.GBZTVaYH1Ext47Z5o4@fat_crate.local>
Hi,
Am Sun, 22 Oct 2023 19:22:40 +0200
schrieb Borislav Petkov <bp@alien8.de>:
> On Sun, Oct 22, 2023 at 01:06:25PM -0400, James Bottomley wrote:
> > How to reproduce would be helpful. Was this a cat of
> > /proc/scsi/scsi?
% cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: Samsung Model: Portable SSD T5 Rev: 0
Type: Direct-Access ANSI SCSI revision: 06
and as far as I can reconstruct the oops correlated with attaching that
drive via USB. But attaching the drive again, does not reproduce it.
>
> Probably some tool did something weird:
>
> CPU: 2 PID: 13243 Comm: colord-sane Not tainted 6.6.0-rc6+ #9
> ^^^^^^^^^^^
>
> judging by https://www.freedesktop.org/software/colord/intro.html
Maybe, right after the part of the log in my mail before I see
note: colord-sane[13243] exited with irqs disabled
note: colord-sane[13243] exited with preempt_count
usbcore: registered new interface driver usb-storage
scsi host0: uas
usbcore: registered new interface driver uas
scsi 0:0:0:0: Direct-Access Samsung Portable SSD T5 0 PQ: 0 ANSI: 6
Cheers,
Julian
--
() ascii ribbon campaign - against html e-mail
/\ - against proprietary attachments
prev parent reply other threads:[~2023-10-22 18:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-22 15:27 Oops with v6.6-rc6+ Julian Wollrath
2023-10-22 16:18 ` Borislav Petkov
2023-10-22 17:06 ` James Bottomley
2023-10-22 17:22 ` Borislav Petkov
2023-10-22 18:18 ` Julian Wollrath [this message]
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=20231022201803.41b8df95@mayene \
--to=jwollrath@web.de \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.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