From: florin@iucha.net (Florin Iucha)
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jiri Kosina <jikos@jikos.cz>,
linux-usb-devel@lists.sourceforge.net,
Adrian Bunk <bunk@stusta.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] 2.6.20-rc4: known unfixed regressions (v2)
Date: Sun, 14 Jan 2007 16:57:01 -0600 [thread overview]
Message-ID: <20070114225701.GA6053@iucha.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0701101052310.3289-100000@iolanthe.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Wed, Jan 10, 2007 at 10:54:34AM -0500, Alan Stern wrote:
> It's still possible that this is hardware related; perhaps some component
> just began to wear out. If you return to an earlier kernel, does the
> problem go away?
As reported in my original e-mail and verified just minutes ago, the
copy succeeds with 2.6.19 (kernel.org vanilla, compiled with the same
config as 2.6.20-rcX). I will begin bisecting between .19 and .20-rc1
after re-reading Jiri's messages.
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2007-01-14 22:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070109214431.GH24369@iucha.net>
[not found] ` <Pine.LNX.4.44L0.0701101052310.3289-100000@iolanthe.rowland.org>
2007-01-14 22:57 ` Florin Iucha [this message]
2007-01-14 23:58 ` heavy nfs[4]] causes fs badness Was: 2.6.20-rc4: known unfixed regressions (v2) Florin Iucha
2007-01-15 0:14 ` Jiri Kosina
2007-01-15 2:02 ` Florin Iucha
2007-01-15 15:58 ` Alan Stern
2007-01-24 3:04 ` Florin Iucha
2007-01-24 19:07 ` Alan Stern
2007-01-15 0:14 ` Trond Myklebust
2007-01-15 2:11 ` Horst H. von Brand
2007-01-15 15:46 ` Florin Iucha
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=20070114225701.GA6053@iucha.net \
--to=florin@iucha.net \
--cc=bunk@stusta.de \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--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