From: Torrey Hoffman <thoffman@arnor.net>
To: Greg KH <greg@kroah.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: usbserial OOPS in 2.5.69-bk4
Date: 26 May 2003 10:53:47 -0700 [thread overview]
Message-ID: <1053971626.1815.3.camel@torrey.et.myrio.com> (raw)
In-Reply-To: <20030520001520.GA28148@kroah.com>
Well, things are better since I upgraded to 2.5.69-bk14
I haven't been able to cause an oops, and up until just a minute ago
things seemed to be working fine. But on my latest sync attempt, I got
this in the dmesg log:
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:0: new USB device on port 2, assigned address 3
usb 1-2: USB device not accepting new address=3 (error=-110)
hub 1-0:0: new USB device on port 2, assigned address 4
usb 1-2: USB device not accepting new address=4 (error=-110)
hub 1-0:0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 1-0:0: new USB device on port 2, assigned address 5
usb 1-2: USB device not accepting new address=5 (error=-110)
hub 1-0:0: new USB device on port 2, assigned address 6
usb 1-2: USB device not accepting new address=6 (error=-110)
and the sync failed.
I'll be upgrading to -bk[latest] later today anyway, and will let you
know if I see further problems with visor USB hotsync...
Torrey Hoffman
thoffman@arnor.net
On Mon, 2003-05-19 at 17:15, Greg KH wrote:
> On Mon, May 19, 2003 at 02:43:34PM -0700, Torrey Hoffman wrote:
> > I got a non-fatal oops while trying to hotsync my Handspring Visor.
> > My system is still running as I send this email, but the hotsync didn't
> > work.
>
> Can you try with the latest -bk tree? I can successfully sync using it,
> but did have some problems with a few of the older revs.
>
> thanks,
>
> greg k-h
--
Torrey Hoffman <thoffman@arnor.net>
prev parent reply other threads:[~2003-05-26 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 21:43 usbserial OOPS in 2.5.69-bk4 Torrey Hoffman
2003-05-20 0:15 ` Greg KH
2003-05-26 17:53 ` Torrey Hoffman [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=1053971626.1815.3.camel@torrey.et.myrio.com \
--to=thoffman@arnor.net \
--cc=greg@kroah.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).