public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thom Borton <borton@phys.ethz.ch>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: PCMCIA CD-ROM does not work
Date: Mon, 10 Nov 2003 20:55:38 +0100	[thread overview]
Message-ID: <200311102055.38852.borton@phys.ethz.ch> (raw)
In-Reply-To: <Pine.LNX.4.44.0310131027060.3684-100000@logos.cnet>


Hello Marcelo

The problem seems to be one of those self-healing things that occur 
once in a while. I just tried 2.4.23-pre9 and the CD-ROM drive works 
again. Plug in the PCMCIA card, double beep, mount disk, read it, 
unmount, unplug card. A mysterious syslog message about a "bad 
special flag" that had always shown up has also disappeared.

Seems like someone has worked on it :-)

Anyways, thanks to all kernel developers,

Thom

P.S.: For those interested, the problem was about a PCMCIA CD-ROM on a 
Sony Vaio PCG-Z600NE that stopped working with 2.4.21/22. 

On Monday 13 October 2003 14:35, you wrote:
> On Sat, 11 Oct 2003, Thom Borton wrote:
> > Hey
> >
> > If have now compiled a series of kernels starting from 2.4.18 up
> > to 2.4.22. The drive stops working with 2.4.21. That is indeed
> > where the "drivers/ide/legacy" directory was introduced.
> >
> > What do you mean by binary search? What's a "pre"?
>
> Try 2.4.21-pre1, 2.4.21-pre2, 2.4.21-pre3 etc. to find exactly
> where it stopped working. You can find the patches against 2.4.20
> at
>
> ftp.kernel.org/pub/linux/kernel/v2.4/testing/old/
>
> > Further: In 2.4.22 I get an Oops and the whole system stops when
> > I unplug the pcmcia card -> hard reset.
> >
> > It says:
> >
> > ///////////
> > remove_proc_entry: hde/identify busy, count=1
> > remove_proc_entry: ide2/hde busy, count=1
> > Unable to handle kernel paging request at virtual address
> > 655f6373 printing eip:
> > c011c5b5
> > *pde = 00000000
> > Oops: 0002
> > CPU:     0
> > .......
> > .......
> >  <0>Kernel panic: Aiee, killing interrupt handler!
> > In interrupt handler - not syncing
> > ///////////
> >
> > Sound's scarry, but doesnt tell me a lot, except that I have to
> > reboot the system.
>
> Can you please post the full kernel panic message?

-- 
Thom Borton
Switzerland


  parent reply	other threads:[~2003-11-10 19:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10 14:52 PCMCIA CD-ROM does not work Thom Borton
2003-10-10 15:09 ` Dave Jones
2003-10-10 15:44   ` Thom Borton
2003-10-10 16:06     ` Bartlomiej Zolnierkiewicz
2003-10-10 16:27     ` Dave Jones
2003-10-10 16:43       ` Thom Borton
2003-10-10 16:47         ` Dave Jones
2003-10-11 11:14           ` Thom Borton
2003-10-13 12:35             ` Marcelo Tosatti
2003-10-15  7:40               ` Thom Borton
2003-11-10 19:55               ` Thom Borton [this message]
2003-10-10 16:04 ` Russell King
2003-10-10 16:35   ` Thom Borton

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=200311102055.38852.borton@phys.ethz.ch \
    --to=borton@phys.ethz.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.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