From: Wolfram Schlich <wolfram@schlich.org>
To: Linux-Kernel mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: Hardlocks with 2.4.21-pre5, pdc202xx_new (PDC20269) and shared IRQs
Date: Thu, 20 Mar 2003 13:06:46 +0100 [thread overview]
Message-ID: <20030320120646.ALLYOURBASEAREBELONGTOUS.E4264@bla.fasel.org> (raw)
In-Reply-To: <OAEPKDBINGEGKPCJJAJDKEBDJIAA.chris.newland@emorphia.com>
* Chris Newland <chris.newland@emorphia.com> [2003-03-20 11:25]:
> Hi Wolfram,
Hi!
> I had the same hardlock problem with dual athlons, MSI K7D Master, Promise
> TX2000 (PDC20271) with 2 HDDs on RAID0 on the Promise card and only a CDROM
> on the onboard IDE channel.
>
> It used to lock hard (2.4.18 vanilla kernel) on 'tar' when using a USB mouse
> but I haven't had a single lockup since plugging in a PS2 mouse :)
>
> PS. Whilst 2.4 kernels run fine for me, I can't get any 2.5 kernel to run
> yet.
>
> I get a VFS kernel panic on bootup (can't mount root device).
>
> I've installed Rusty's 2.5 modutils and tried compiling the 20271 driver
> both into the kernel and as a module.
>
> I read in Dave Jones' post-halloween notes that the Promise drivers are
> broken:
>
> <quote>
> - The hptraid/promise RAID drivers are currently non functional, and
> will probably be converted to use device-mapper.
> </quote>
>
> Is this still true?
I have no idea... I'm not using:
a) A Promise RAID controller (just the dumb ones)
b) Kernel 2.5
:-)
--
Mit freundlichen Gruessen / Yours sincerely
Wolfram Schlich; Friedhofstr. 8, D-88069 Tettnang; +49-(0)178-SCHLICH
next prev parent reply other threads:[~2003-03-20 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 22:16 Wolfram Schlich
2003-03-20 1:42 ` Alan Cox
2003-03-20 7:22 ` Wolfram Schlich
2003-03-20 8:51 ` Stephan von Krawczynski
2003-03-20 12:08 ` Wolfram Schlich
2003-03-20 10:23 ` Chris Newland
2003-03-20 12:06 ` Wolfram Schlich [this message]
2003-03-20 14:57 ` Alan Cox
2003-03-20 14:35 ` Wolfram Schlich
2003-03-25 18:32 ` Jan Kasprzak
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=20030320120646.ALLYOURBASEAREBELONGTOUS.E4264@bla.fasel.org \
--to=wolfram@schlich.org \
--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
all inboxes | Powered by JetHome®