From: Pavel Machek <pavel@ucw.cz>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Andrew Morton <akpm@zip.com.au>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-rc4, -mm: bad ide-cs problems
Date: Wed, 25 May 2005 15:05:41 +0200 [thread overview]
Message-ID: <20050525130541.GA1960@elf.ucw.cz> (raw)
In-Reply-To: <42946451.9070301@domdv.de>
Hi!
> > hde: cache flushes not supported
> > hde: hde1
> > ide-cs: hde: Vcc = 3.3, Vpp = 0.0
> > hde: hde1
> > hde: hde1
> > Unable to handle kernel NULL pointer dereference at virtual address
> > 00000010
> > printing eip:
> > c033d618
> > *pde = 00000000
> > Oops: 0000 [#1]
> > PREEMPT
> > Modules linked in:
> > CPU: 0
> > EIP: 0060:[<c033d618>] Not tainted VLI
> > EFLAGS: 00010292 (2.6.12-rc4)
> > EIP is at ide_drive_remove+0x8/0x10
> > eax: c07825f8 ebx: c0782704 ecx: c07826f0 edx: 00000000
> > esi: c07826e0 edi: c065fed8 ebp: 00000001 esp: dfce5e84
> > ds: 007b es: 007b ss: 0068
> > Process pccardd (pid: 932, threadinfo=dfce4000 task=dfc84a40)
> > Stack: c02dc4b4 c07826e0 c065fa00 c0782568 c02dc724 c07826e0 c0782a80
> > c02db5e2
> > c07826e0 df373a80 c02db628 c07825f8 c033bcfb c0782568 00000002
> > df373b80
> > df373b80 c0670680 c0670728 c034f63b df758200 00000000 c034f67a
> > c0386108
> > Call Trace:
> > [<c02dc4b4>] device_release_driver+0x74/0x80
>
> Pavel,
> I had a similar problem which I fixed amd posted to lkml a while ago
> though I seems to got ignored by the ide maintainer. Please see if this
> helps in your case:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=111409743421578&w=2
Yes, thanks, that works. Andrew, is there reason not to push that
patch into -mm/linus?
Pavel
next prev parent reply other threads:[~2005-05-25 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 11:27 2.6.12-rc4, -mm: bad ide-cs problems Pavel Machek
2005-05-25 11:28 ` Pavel Machek
2005-05-25 11:41 ` Andreas Steinmetz
2005-05-25 13:05 ` Pavel Machek [this message]
2005-05-25 13:27 ` Bartlomiej Zolnierkiewicz
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=20050525130541.GA1960@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=ast@domdv.de \
--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