[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

2.6.11.1-generic boot fails with "Unable to reserve I/O region"...



This is an Alphastation 200 4/233. Works fine with the 2.4.27-2-generic
kernel. Installed kernel-image-2.6.11-1-generic, it fails to boot
because it can't configure the onboard SCSI controller:

PCI: Unable to reserve I/O region #1:100@10100 for device 0000:00:06.0


I added another SCSI controller in a PCI slot and moved the drive to
there, now it runs fine except it still fails to bring up the onboard
SCSI.

Under 2.4, lspci shows this for the onboard controller:
0000:00:06.0 Non-VGA unclassified device: LSI Logic / Symbios Logic 53c810 (rev 01)
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR+
        Latency: 32
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 8000 [size=256]
        Region 1: Memory at 0000000001211000 (32-bit, non-prefetchable) [size=256]

Under 2.6, it's:
0000:00:06.0 Non-VGA unclassified device: LSI Logic / Symbios Logic 53c810 (rev 01)
        Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR- FastB2B-
        Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at 10100 [size=256]
        Region 1: Memory at 0000000082811100 (32-bit, non-prefetchable) [size=256]


So somehow 2.6 is seeing the wrong I/O addressing for this device, if
I'm reading this right.

There was a post last year sometime about a similar problem, the
resolution there seemed to be that the config needed
"CONFIG_ALPHA_SRM=y". I notice that the Debian config
(/boot/config-2.6.11-1-generic) does not include that. So I built a
kernel from the 2.6.12.3 sources, but that has the same problem.
Changing to 'avanti' from 'generic' doesn't help either.

I started hacking into the sources to try to see where it's going wrong,
I'll continue doing that if I have to. But it's looking like it'll be a
long job, maybe someone here has already worked out how to fix this?







Reply to: