From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
To: linux-hotplug@vger.kernel.org
Subject: Re: 2.4.18 kernel oops when eject and hot-plug cardbus card again.
Date: Sun, 17 Nov 2002 13:02:47 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-103753822013055@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103733608411211@msgid-missing>
Tried 2.4.19 - it is better, doesn't oops, but after eject
(cardctl eject 0; modprobe -r aic7xxx; ... ; modprobe aic7xxx),
it won't detect the cd-writer hanging off the end of the SlimSCSI 1480A
card.
I have most of the scsi stuff (scsi disk, scsi cd, scsi generic, etc)
compiled into
the kernel. Would it make any difference if I have them as modules? I used
to have them compiled into the kernel for my 2.2.x+pcmcia-cs setup, and it
has been working fine then.
Greg KH wrote:
>On Fri, Nov 15, 2002 at 04:53:43AM +0000, Hin-Tak Leung wrote:
>
>
>>Hi. I have recently upgraded to 2.4.18+pci hotplug (the rest of the
>>system is mostly Slackware 8.1).
>>
>>
>
>Hm, could you try a more recent kernel (like 2.4.19 at the minimum?)
>2.4.18 was released last February, which was quite a while ago.
>
>thanks,
>
>greg k-h
>
>
>
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2002-11-17 13:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 4:53 2.4.18 kernel oops when eject and hot-plug cardbus card again Hin-Tak Leung
2002-11-15 6:12 ` Greg KH
2002-11-16 2:44 ` Hin-Tak Leung
2002-11-17 13:02 ` Hin-Tak Leung [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=marc-linux-hotplug-103753822013055@msgid-missing \
--to=hintak_leung@yahoo.co.uk \
--cc=linux-hotplug@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).