linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Peter <pk@q-leap.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops still occurs with usb-serial converter
Date: Mon, 21 Oct 2002 07:55:48 -0700	[thread overview]
Message-ID: <20021021145548.GA30857@kroah.com> (raw)
In-Reply-To: <S.0001127744@wolnet.de>

On Mon, Oct 21, 2002 at 12:02:38PM +0200, Peter wrote:
> Hello,
> 
> The attached kernel oops still occurs (was reported with kernel 2.4.19
> on July, 29th):
> 
> Hardware:
>   Dell Inspiron 2600 Laptop
>   USB-Serial Converter: UC-232A
> 
> Software:
>   minicom (V1.82.1)
>   kernel: 2.4.20-pre11
> 
> modules loaded:
> pl2303                 10104   1
> usbserial              17468   0 [pl2303]
> uhci                   23600   0 (unused)

Does the same problem happen with usb-uhci instead of uhci?

thanks,

greg k-h

  reply	other threads:[~2002-10-21 14:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21 10:02 oops still occurs with usb-serial converter Peter
2002-10-21 14:55 ` Greg KH [this message]
     [not found]   ` <15796.7272.489462.627051@gargle.gargle.HOWL>
2002-10-21 15:27     ` Greg KH

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=20021021145548.GA30857@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pk@q-leap.com \
    /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).