From: Greg KH <greg@kroah.com>
To: "Sam (Uli) Freed" <spam@freed.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB serial OOPS
Date: Sat, 28 Jun 2003 09:28:19 -0700 [thread overview]
Message-ID: <20030628162819.GA1546@kroah.com> (raw)
In-Reply-To: <3EFD3800.4080107@freed.net>
On Sat, Jun 28, 2003 at 09:38:56AM +0300, Sam (Uli) Freed wrote:
> Hi all + Greg,
>
> I have a laptop with a "USB Socking station" attached (basically a
> hub+serial+paralel.).
>
> I have managed to use the Serial ONCE to sync my PalmPilot, out of at
> least 60 attempts. 2-3 of these attempts ended in an OOPS, and here it
> is in a neat "tar cvzf" format. The only caveat is that is went through
> an "apm -s" cycle between the oops and the report.
Can you not compress these files next time? It's real hard to read them
this way. Large text emails are no problem.
Anyway, can you try this with 2.5? I think the bug is fixed there but
it would be nice to verify.
thanks,
greg k-h
prev parent reply other threads:[~2003-06-28 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3EFCAF3D.9060207@freed.net>
[not found] ` <20030627225144.GC11296@kroah.com>
2003-06-28 6:38 ` USB serial OOPS Sam (Uli) Freed
2003-06-28 16:28 ` Greg KH [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=20030628162819.GA1546@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spam@freed.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;
as well as URLs for NNTP newsgroup(s).