From: Chris Ross <lak1646@tebibyte.org>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Greg Ungerer <gerg@snapgear.com>,
linux-arm-kernel@lists.arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: Kernel panic reading bad disk sector
Date: Wed, 23 Nov 2005 10:26:48 +0000 [thread overview]
Message-ID: <438443E8.5040602@tebibyte.org> (raw)
In-Reply-To: <20051123095640.GA5022@flint.arm.linux.org.uk>
Russell King - ARM Linux escreveu:
> On Wed, Nov 23, 2005 at 09:25:40AM +0000, Chris Ross wrote:
>>Greg Ungerer escreveu:
>>>Chris Ross wrote:
>>>
>>>>According System.map it is in the function ide_dma_timeout_retry.
>>>
>>>Ok, that is good information. I would try and figure out which
>>>line of code in there is dereferencing a NULL pointer.
>>
>>It would seem to be this line
>>
>> rq->errors = 0;
because rq is set to NULL by earlier the line
ret = DRIVER(drive)->error(drive, "dma timeout retry",
hwif->INB(IDE_STATUS_REG));
> I'd strongly suggest that you talk to IDE folk about this - I
> suspect HWGROUP(drive)->rq should never be NULL while a request
> is being handled on drive.
Which list specifically? I've taken your advice and "promoted" this to
LKML so if that was wrong please correct it politely.
For those just tuning in this is about an ARM system with a Promise
20275 IDE controller which suffers a kernel panic when attempting to
read from a bad sector on the disk.
Regards,
Chris R.
next parent reply other threads:[~2005-11-23 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4381DA23.10201@tebibyte.org>
[not found] ` <4382B815.5000701@snapgear.com>
[not found] ` <43836758.6050001@tebibyte.org>
[not found] ` <4383C205.7020608@snapgear.com>
[not found] ` <43843594.9050009@tebibyte.org>
[not found] ` <20051123095640.GA5022@flint.arm.linux.org.uk>
2005-11-23 10:26 ` Chris Ross [this message]
2005-11-23 10:48 ` Kernel panic reading bad disk sector Chris Ross
2005-11-23 12:51 ` Chris Ross
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=438443E8.5040602@tebibyte.org \
--to=lak1646@tebibyte.org \
--cc=gerg@snapgear.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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