public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Barry K. Nathan" <barryn@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] pl2303 oops in 2.4.20-pre10 (and 2.5 too)
Date: Wed, 9 Oct 2002 16:53:32 -0700	[thread overview]
Message-ID: <20021009235332.GA19351@kroah.com> (raw)
In-Reply-To: <20021009233624.GA17162@ip68-4-86-174.oc.oc.cox.net>

On Wed, Oct 09, 2002 at 04:36:24PM -0700, Barry K. Nathan wrote:
> On one of my systems, when minicom opens /dev/ttyUSB0 (a PL2303) and
> the kernel is 2.4.20-pre10 (compiled with Mandrake 9's gcc 3.2),
> minicom segfaults and the kernel oopses.

Can you enable debugging in the pl2303 driver (by loading it with
"debug=1") and send the kernel debug log for when the oops happens.

thanks,

greg k-h

  reply	other threads:[~2002-10-09 23:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-09 23:36 [BUG] pl2303 oops in 2.4.20-pre10 (and 2.5 too) Barry K. Nathan
2002-10-09 23:53 ` Greg KH [this message]
2002-10-11  2:39   ` Barry K. Nathan
     [not found]     ` <20021011170623.GB4123@kroah.com>
2002-10-12  6:30       ` Barry K. Nathan
2002-10-12 20:56         ` Barry K. Nathan
2002-10-13  0:42           ` [PATCH] 2.4.20-pre10: make PL-2303 hack work again Barry K. Nathan
2002-10-13  1:16             ` Greg KH
2002-10-13  1:54               ` Barry K. Nathan
2002-10-13  4:30               ` [PATCH/RFC] 2.5.42 partial fix for older pl2303 Barry K. Nathan
2002-10-13 20:25                 ` Greg KH
2002-10-14  2:49                   ` Barry K. Nathan
2002-10-14  4:17                     ` Barry K. Nathan
2002-10-15  5:52                       ` Greg KH
2002-10-13  0:49           ` [BUG] pl2303 oops in 2.4.20-pre10 (and 2.5 too) Greg KH
2002-10-13  1:26             ` Barry K. Nathan

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=20021009235332.GA19351@kroah.com \
    --to=greg@kroah.com \
    --cc=barryn@pobox.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