From: "Maciej Rutecki" <maciej.rutecki@gmail.com>
To: "Alan Stern" <stern@rowland.harvard.edu>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, usb-storage@lists.one-eyed-alien.net
Subject: Re: [Re: Linux 2.6.26-rc2] Write protect on on
Date: Sat, 17 May 2008 08:59:22 +0200 [thread overview]
Message-ID: <8db1092f0805162359k2def1738s91cc78d48bea2581@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0805162056230.13416-100000@netrider.rowland.org>
2008/5/17 Alan Stern <stern@rowland.harvard.edu>:
> The best way to gather more data is to use usbmon and trace what
> happens when you plug in the drive (see Documentation/usb/usbmon.txt).
> If you collect traces under both 2.6.25.4 and 2.6.26-rc2 then we can
> compare them to see what has changed.
>
> You don't have to trace the mount command; the activity at plug-in time
> will be sufficient.
>
> Alan Stern
>
>
2.6.25.4 (works fine):
http://unixy.pl/maciek/download/kernel/2.6.25.4/syslog_debug.txt
http://unixy.pl/maciek/download/kernel/2.6.25.4/usbmon.txt
2.6.26-rc2 ("write protect is on" problem; can't mount device):
http://unixy.pl/maciek/download/kernel/2.6.26-rc2/syslog_debug.txt
http://unixy.pl/maciek/download/kernel/2.6.26-rc2/usbmon.txt
--
Maciej Rutecki
http://www.maciek.unixy.pl
next prev parent reply other threads:[~2008-05-17 6:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 14:55 Maciej Rutecki
2008-05-17 1:03 ` Alan Stern
2008-05-17 6:59 ` Maciej Rutecki [this message]
2008-05-17 13:49 ` Alan Stern
2008-05-18 16:27 ` Boaz Harrosh
2008-05-19 15:18 ` Alan Stern
2008-05-19 16:08 ` Boaz Harrosh
2008-05-19 16:36 ` Linus Torvalds
2008-05-19 17:03 ` Boaz Harrosh
2008-05-19 17:27 ` Linus Torvalds
2008-05-19 17:45 ` Boaz Harrosh
2008-05-19 18:16 ` Matthew Wilcox
2008-05-22 8:23 ` James Bottomley
2008-05-19 19:17 ` Alan Stern
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=8db1092f0805162359k2def1738s91cc78d48bea2581@mail.gmail.com \
--to=maciej.rutecki@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
--cc=usb-storage@lists.one-eyed-alien.net \
/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®