From: Guido Diepen <guido@jcwodan.nl>
To: linux-hotplug@vger.kernel.org
Subject: [Partially Solved] Re: Question regarding PDC202xx problems
Date: Tue, 03 Oct 2006 20:05:59 +0000 [thread overview]
Message-ID: <200610032205.59478.guido@jcwodan.nl> (raw)
Hi,
I did not have a lot of time for testing anymore before. This evening I
finally had some time left for more testing. I hope the results might help
other people that run into the same problem
> >> till a couple of days my debian machine was running my own compiled
> >> 2.6.10-nitro2 kernel. When I tried to upgrade the machine everything
> >> booted fine, except for the fact that my extra PCI IDE controller
> >> (PDC20268 chipset, using the PDC202XX_new driver in the kernel) gave
> >> problems. I got all kinds of DMA errors and IDE channel resets after
> >> which
> >> my machine completely locked up.
> >
> > This may be triggered by one of the *_id programs probing the device.
Indeed it was one of the *_id programs that caused the problem. After
disabling udev during boot I went into single user mode for testing.
When I used the program vol_id on the second partition of on of the harddisks
(/dev/hdg) that is on the additional IDE control (PDC20268 chipset) I found
that I get exactly the same lockup that I had experienced before. For some
strage reason I was able to run the vol_id program on /dev/hdg1 without any
problems, but as soon as I ran it on /dev/hdg2 it locked up my machine.
The solution that works for now for me is to add the option --disable-raid
within the persistent.rules file to the occurrence of vol_id. I am not sure
whether this is the best solution, but for sure something does go wrong
within the raid-detecting part.
Hope this can be of any use. If more information is needed, please let me
know.
Regards,
Guido Diepen
--
Aviation is proof that given the will, we have the
capacity to achieve the impossible.
--Eddie Rickenbacker
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CIDÞVDEV
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
reply other threads:[~2006-10-03 20:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200610032205.59478.guido@jcwodan.nl \
--to=guido@jcwodan.nl \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).