Re: kernel panics with debian kernels >2.2.25 on A4000T/060
On Wed, Oct 26, 2005 at 01:45:53PM +0200, Kars de Jong wrote:
> On wo, 2005-10-26 at 11:32 +0200, Ingo Juergensmann wrote:
> > That's a nice machine, but it's somewhat boring that I can only run kernel
> > 2.2.20 or 2.2.25 on it.
> >
> > I tried several prepackaged kernels from Debian, but all panic. I've put
> > some dmesg outputs on the net:
>
> Good, someone with a system other than MVME16x using an NCR53C710 :-)
>
> >From your dmesg:
>
> scsi-ncr53c7xx : NCR53c710 at memory 0xd0190040, io 0x0, irq 12
>
> This is the old ncr53c7xx driver, I believe it is broken on prepackaged
> Debian kernels because of a bogus virt_to_bus() call and/or the kernel
> being compiled with CONFIG_SINGLE_MEMORY_CHUNK=N. On early 2.4 kernels
> it did still work for me, but hasn't worked since 2.4.x (I don't
> remember x).
>
> I will try to rewrite the amiga7xx driver this evening to use the new
> 53c700 driver core. Should be pretty simple since it already works on
> MVE16x.
I'm doing the same for the BVME6000, as I have one of those to
test on. I also have an MVME177 (basically an MVME167 but with 68060),
so can test there too.
> It would be nice if you can test it, if it works I think we can safely
> get rid of the old ncr53c7xx driver.
Yep, having one less NCR scsi driver in the tree should please a few
people :)
Richard
Reply to: