Hallo Christian,

Am Montag, 27. Dezember 2004 03:47 schrieben Sie:

Marc Dietrich schrieb:

quoted

I also tried to change the irq routings in prep_pci.c like in the latest
patch with the sym53c8xx_2 driver,
	Slot 12 -> IRQ 15 (sym53c825)
	Slot 15 -> IRQ 11 (dec 21140)
but this didn't helped.

i'm still working these out too, gotta find some time...

maybe this helps:

I used the config file you sent me (and added serial console).

when booting a working 2.4.24-pre1 I get:

[...]
PCI: Probing PCI hardware
Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
PCI: moved device 00:0b.1 resource 4 (101) to 1480
PCI: moved device 00:0b.1 resource 5 (101) to 1490
PCI: moved device 00:11.0 resource 0 (1208) to 0
[...]
SCSI subsystem driver Revision: 1.00
new devtbl    [4096] @c049e000.
PCI: Enabling device 00:0c.0 (0000 -> 0003)
sym53c8xx: at PCI bus 0, device 12, function 0
sym53c8xx: setting PCI_COMMAND_MASTER PCI_COMMAND_PARITY...(fix-up)
sym53c8xx: changing PCI_LATENCY_TIMER from 0 to 80.
sym53c8xx: 53c825a detected
sym53c825a-0: rev 0x13 on pci bus 0 device 12 function 0 irq 15
new MPOOL     [ 188] @c049f000.
new VTOB      [  12] @c049f100.
new NCB       [2408] @c049c000.
new SQUEUE    [2336] @c049d000.
new VTOB      [  12] @c049f110.
new DQUEUE    [2336] @c049a000.
new TARGTBL   [ 256] @c049b000.
new VTOB      [  12] @c049f120.
new SCRIPT    [3504] @c0498000.
new SCRIPTH   [1504] @c049b800.
new CCB       [1300] @c0499000.
sym53c825a-0: ID 7, Fast-10, Parity Checking


while booting a non working 2.6.10 I get:

I already changed the irq of slot 12 to 15 and slot 14 to irq 11.

[...]
PCI: Probing PCI hardware
Setting PCI interrupts for a "Utah (Powerstack II Pro4000)"
PCI: Cannot allocate resource region 5 of device 0000:00:01.1
SCSI subsystem initialized
[...]
PCI: Enabling device 0000:00:02.0 (0000 -> 0003)
sym0: <825a> rev 0x13 at pci 0000:00:02.0 irq 15
new MPOOL     [ 180] @c7d99000.
new VTOB      [  12] @c7d99100.
new HCB       [1784] @c7d9a000.
sym0: No NVRAM, ID 7, Fast-10, SE, parity checking
new VTOB      [  12] @c7d99110.
new SQUEUE    [3600] @c7d9b000.
new VTOB      [  12] @c7d99120.
new DQUEUE    [3600] @c7d9c000.
new TARGTBL   [ 256] @c7d9a800.
new VTOB      [  12] @c7d99130.
new SCRIPTA0  [3024] @c7d9d000.
new VTOB      [  12] @c7d99140.
new SCRIPTB0  [1324] @c7d9e000.
new SCRIPTZ0  [  32] @c7d9a900.
new CCBH      [1024] @c7d99400.
new CCB       [ 988] @c7d9ac00.
new SNS_BBUF  [  32] @c7d9a920.
[...]
new BADLUNTBL [ 256] @c7d9aa00.
sym0: SCSI BUS has been reset.
scsi0 : sym-2.1.18m
elevator: using anticipatory as default io scheduler
sym0:0:0:ccb @c7d9ac00 using tag 256.
sym0: queuepos=2.
sym0:0:0: ABORT operation started.
sym0:0:0: ABORT operation timed-out.
sym0:0:0: DEVICE RESET operation started.
sym0:0:0: DEVICE RESET operation timed-out.
sym0:0:0: BUS RESET operation started.
sym0:0:0: BUS RESET operation timed-out.
sym0:0:0: HOST RESET operation started.
sym0:0:0:ccb @c7d9ac00 freeing tag 256.
sym0: SCSI BUS has been reset.
[ hangs here ]



Indeed, there seems to be something wrong with the pci resources - but I can't 
say what. I attached the compete boot logs. I also attached the lspci -v 
output.

Greetings

Marc