Re: 2.4.4-ac5 aic7xxx causes hang on my machine

[Doug Ledford]

Alan Cox wrote:
> 
> > > IRQ11 appearing on IRQ10 sounds exactly like the INTA-D line setting for IRQ
> > > 11 is wrong and we connected it to IRQ 10
> >
> > Which brings me back to my question in my previous email.  Why are we
> > remapping working configs again?  I'm at a loss here.  This isn't a hot plug
> > capably motherboard, we don't have to worry about new PCI cards getting thrown
> > in, and yet we are remapping the IRQs.  Why?
> 
> Ok and how do you propose to implement
> 
>         int gee_whiz_this_configuration_works(void)

The obvious one would be

int gee_whiz_this_configuration_works(struct pdev *pdev) {
	return(device_is_bootable_device(pdev));
}

> Now how about checking the BIOS tables and seeing if they are wrong. If so then
> someone can do something about it. Right now this is speculation and needs
> verifying.

Which is what I said also in my last email.  I'm more than happy to write this
off as a BIOS bug, and it is highly likely that the fact that Windows doesn't
see a problem is because of the exact test I mentioned above.  The BIOS has to
setup all possible boot devices, only devices non-essential to the boot
process (sound cards, modems, crap like that) get left unconfigured.  Not
touching already configured devices would seem to be a reasonable thing to do
in my opinion.  Not that I think configuring things is wrong, but it does make
you vulnerable to BIOS table bugs like this likely exposes, where as if you
didn't touch boot devices, then buggy BIOSes wouldn't bring your kernel to a
halt as easily.

-- 

 Doug Ledford <[e-mail]>  http://people.redhat.com/dledford
      Please check my web site for aic7xxx updates/answers before
                      e-mailing me about problems