From: Wilfried Weissmann <Wilfried.Weissmann@gmx.at>
To: Wil Reichert <wilreichert@yahoo.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: highpoint driver problem, 2.4.21-ac4
Date: Sun, 06 Jul 2003 00:07:33 +0200 [thread overview]
Message-ID: <3F074C25.5060004@gmx.at> (raw)
In-Reply-To: 20030703184427.3cb71051.wilreichert@yahoo.com
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
Wil Reichert wrote:
> Thats the kernel I'm using.
could you try the attachted patch, and report if this changes something?
bye,
wilfried
>
> Wil
>
> On Thu, 03 Jul 2003 21:21:30 +0200
> Wilfried Weissmann <Wilfried.Weissmann@gmx.at> wrote:
>
>
>>Wil Reichert wrote:
>> >>> The on-board Highpoint controller (HPT372A) on my DFI NF2 is
>> >>> having issue. Loading the hptraid module results in a 'No such
>> >>> device' message while the hpt366 module segfaults and leaves an
>> >>> oops in my logs. These errors occur regardless of the disk/raid
>> >>> configuration in the hpt BIOS. Following are the oops trace, an
>> >>> lsmod, the .config and a lspci -vvv.
>> >>
>> >> The crash occurs in the hpt366 module. Loading hptraid will not
>> >> work because it depends on the kernel to claim the disks of the
>> >> raid volume (that is what hpt366 would do). I will add autoloading
>> >> of the ide-controller module in the next raid-driver release.
>> >> However, I do not know why the kernel oopses. You might want to try
>> >> to build the hpt366 code into the kernel instead of a module. If it
>> >> works it would probably mean that "ide_hwif_t *hwif" was not
>> >> properly initalized.
>> >
>> > I initially had all the hpt modules built into the kernel, but that
>> > would also produce an oops and die immediately after ID'ing the two
>> > drives I have on attached. Would any more information be of use to
>> > you?
>>
>>2.4.21-ac4 contains several fixes for the hpt37x. Please try this patch out.
>>
>>bye,
>>Wilfried
[-- Attachment #2: linux-2.4.21-ac4-idedmafix.patch --]
[-- Type: text/plain, Size: 489 bytes --]
--- linux/drivers/ide/setup-pci.c.orig 2003-07-06 00:04:06.000000000 +0200
+++ linux/drivers/ide/setup-pci.c 2003-07-06 00:04:12.000000000 +0200
@@ -172,7 +172,7 @@ static int ide_setup_pci_baseregs (struc
* is already in DMA mode we check and enforce IDE simplex rules.
*/
-static unsigned long __init ide_get_or_set_dma_base (ide_hwif_t *hwif)
+static unsigned long ide_get_or_set_dma_base (ide_hwif_t *hwif)
{
unsigned long dma_base = 0;
struct pci_dev *dev = hwif->pci_dev;
next prev parent reply other threads:[~2003-07-05 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4V9E.47E.39@gated-at.bofh.it>
[not found] ` <4V9E.47E.37@gated-at.bofh.it>
[not found] ` <4WyE.5oC.19@gated-at.bofh.it>
2003-07-03 19:21 ` highpoint driver problem, 2.4.21-ac4 Wilfried Weissmann
[not found] ` <20030703184427.3cb71051.wilreichert@yahoo.com>
2003-07-05 22:07 ` Wilfried Weissmann [this message]
[not found] ` <20030706132507.240683d1.wilreichert@yahoo.com>
2003-07-07 17:41 ` Wilfried Weissmann
2003-07-07 17:54 ` Wilfried Weissmann
[not found] <4FHn.4MD.1@gated-at.bofh.it>
2003-07-02 18:50 ` Wilfried Weissmann
2003-07-02 20:36 ` Wil Reichert
2003-07-02 2:27 Wil Reichert
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=3F074C25.5060004@gmx.at \
--to=wilfried.weissmann@gmx.at \
--cc=linux-kernel@vger.kernel.org \
--cc=wilreichert@yahoo.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;
as well as URLs for NNTP newsgroup(s).