From: Michael Frank <mhf@linuxmail.org>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] 2.6.0-test4 - PL2303 OOPS - see also 2.4.22: OOPS on disconnect PL2303 adapter
Date: Sat, 6 Sep 2003 16:01:44 +0800 [thread overview]
Message-ID: <200309061601.44440.mhf@linuxmail.org> (raw)
In-Reply-To: <20030906054813.GC20197@kroah.com>
On Saturday 06 September 2003 13:48, Greg KH wrote:
> On Sat, Sep 06, 2003 at 10:31:19AM +0800, Michael Frank wrote:
> > It's not loaded on boot, but only when needed. The scripts:
> >
> > usb1)
> > if [ ! -e /proc/bus/usb ]; then
> > echo Loading USB
> > modprobe usbcore
> > mount -t usbdevfs usbdevfs /proc/bus/usb
> > modprobe ohci_hcd
> > modprobe sd_mod
> > modprobe pl2303
> > modprobe lp
> > fi
> > ;;
> >
> > usb0)
> > echo Unloading USB
> > rmmod usb-storage sd_mod scsi-mod
> > rmmod pl2303 usbserial
> > rmmod lp parport
> > rmmod ohci_hcd
> > umount usbdevfs
> > rmmod usbcore
> > ;;
> >
> > Perhaps this is too dumb and I should do some checking along the way,
> > however joe user should be unable to oops things up...
>
> I agree. Can you add that oops to a new bug at bugzilla.kernel.org?
>
Yes, will do, and more testing as well.
Regards
Michael
next prev parent reply other threads:[~2003-09-06 9:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 17:39 2.6.0-test4 - PL2303 OOPS - see also 2.4.22: OOPS on disconnect PL2303 adapter Michael Frank
2003-09-01 18:53 ` Jan-Benedict Glaw
2003-09-02 16:43 ` [linux-usb-devel] " Greg KH
2003-09-02 22:13 ` Michael Frank
2003-09-02 23:52 ` Greg KH
2003-09-03 6:32 ` Michael Frank
2003-09-05 23:08 ` Greg KH
2003-09-06 2:31 ` Michael Frank
2003-09-06 5:48 ` Greg KH
2003-09-06 8:01 ` Michael Frank [this message]
2003-09-06 7:38 ` Jan-Benedict Glaw
2003-09-06 7:55 ` Michael Frank
2003-09-06 10:55 ` Jan-Benedict Glaw
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=200309061601.44440.mhf@linuxmail.org \
--to=mhf@linuxmail.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.