Re: antares qlogic sbus scsi controller ?
Eric,
Sunday evening I got around to trying your code
snippet out. I had to use a different variable
name to match up to what was in the file in
2.2.25, but otherwise seemed like a reasonable
match. The original code in my code tree is:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if(qpti_dev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
So I added a 'qpti_dev-irqs[0] = 0x35;'
and dropped the 'continue;' as per your code mod.
When I rebooted to a kernel that picked up this
scsi driver mod the new qlogic scsi driver got stuck
in an eternal error loop. I've got the box rigged
up as my main email/dhcp/dns/router/firewall
so, given that it was about midnight, I thrashed it
back to the original state without noting the exact
wording of the eternal error loop. I apologize for
not grabbing the exact text.
Heitzso
Eric Brower wrote:
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
My guess is sometimes in the above comment means On sun4c/d/m.
If you wanted to test in 2.2.x without the aforementioned patch, you
might be able to do something like (specific to your sun4m):
if (sdev-irqs[0] == 0) {
sdev-irqs[0] = 0x35;
printk(qpti%d: Adapter reports no interrupt,
blindly assigning irq 0x35\n);
}
...and see how the rest of the driver likes your card. This is just off
the top of my head-- no guarantees, of course.
antares qlogic sbus scsi controller ?
I have an sbus antares (actually a qlogic) fast/wide scsi2 controller in my ss20 that the bootprom finds and solaris found and used but my 2.2.25 kernel flags as missing an interrupt and skips over. I'm wondering whether I need a driver option in order to use the controller with the 2.2.X kernels. I've scanned kernel doc and googled around but haven't found the right clue. Any ideas would be appreciated. It would be real nice to get the speed bump from this controller! Thanks, Heitzso
Re: antares qlogic sbus scsi controller ?
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
Do you happen to have Solaris or Linux 'prtconf -pv' info for this
system? No workaround is mentioned, but perhaps this is due to no
intr property present in that FCode. Just a thought
E
Re: antares qlogic sbus scsi controller ?
I ran the prtconf as you suggested and the following stanza
comes up for the qlogic controller:
Node 0xffd7b350
scsi-initiator-id: 0007
device_type: 'scsi'
interrupts: 0003
wide: 00
clock-frequency: 02625a00
reg: 0002.0001.0450
model: 'QLGC,ISP1000'
name: 'QLGC,isp'
Node 0xffd7edf0
device_type: 'block'
name: 'sd'
Node 0xffd7f340
device_type: 'byte'
name: 'st'
Which would appear that the controller is available(??).
However, if I have an external case attached to that
controller with drives in it I still get the no interrupts
found skipping controller etc. message.
Thanks for digging up the message in the driver.
Still no scsi controller. I'll slide on it since
I'm not in a position to thrash the code.
Heitzso
Eric Brower wrote:
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
Do you happen to have Solaris or Linux 'prtconf -pv' info for this
system? No workaround is mentioned, but perhaps this is due to no
intr property present in that FCode. Just a thought
Re: antares qlogic sbus scsi controller ?
Yep-- missing the intr property.
I'd suggest you have two choices:
1) backport my interrupts-decoders patch from current BK 2.4.x to 2.2.x
2) migrate to a later BK 2.4.x kernel with the patch already included
(the patch has been in BK for around 9 months)
The interrupts-decoders patch (against 2.5.x, but same as against 2.4.x)
is changeset 1.838.172.14 at:
http://linux.bkbits.net:8080/linux-2.5/user=zaitcev/[EMAIL
PROTECTED]|index.html|stats|!+|index.html|[EMAIL PROTECTED]|[EMAIL PROTECTED]
E
Heitzso wrote:
I ran the prtconf as you suggested and the following stanza
comes up for the qlogic controller:
Node 0xffd7b350
scsi-initiator-id: 0007
device_type: 'scsi'
interrupts: 0003
wide: 00
clock-frequency: 02625a00
reg: 0002.0001.0450
model: 'QLGC,ISP1000'
name: 'QLGC,isp'
Node 0xffd7edf0
device_type: 'block'
name: 'sd'
Node 0xffd7f340
device_type: 'byte'
name: 'st'
Which would appear that the controller is available(??).
However, if I have an external case attached to that
controller with drives in it I still get the no interrupts
found skipping controller etc. message.
Thanks for digging up the message in the driver.
Still no scsi controller. I'll slide on it since
I'm not in a position to thrash the code.
Heitzso
Eric Brower wrote:
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
Do you happen to have Solaris or Linux 'prtconf -pv' info for this
system? No workaround is mentioned, but perhaps this is due to no
intr property present in that FCode. Just a thought
.
Re: antares qlogic sbus scsi controller ?
Eric Brower wrote:
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
My guess is sometimes in the above comment means On sun4c/d/m.
If you wanted to test in 2.2.x without the aforementioned patch, you
might be able to do something like (specific to your sun4m):
if (sdev-irqs[0] == 0) {
sdev-irqs[0] = 0x35;
printk(qpti%d: Adapter reports no interrupt,
blindly assigning irq 0x35\n);
}
...and see how the rest of the driver likes your card. This is just off
the top of my head-- no guarantees, of course.
E
Re: antares qlogic sbus scsi controller ?
I've glanced at the patch at
http://linux.bkbits.net:8080/linux-2.5/user=zaitcev/[EMAIL PROTECTED]
(please confirm the URL, the full URL below didn't go anywhere, thanks).
I'll look at equiv 2.2.25 code then decide whether to go simple
test route or full backport merge. May be a few days before
I get to it.
My main thrash is trying to figure out why
postfix-tls-openssl-saslauthd-pam stopped sending out the sasl
auth modes recently. I'm rigging the ss20 to be a hopefully
stable SOHO edge box with mail server.
Heitzso
Eric Brower wrote:
Yep-- missing the intr property.
I'd suggest you have two choices:
1) backport my interrupts-decoders patch from current BK 2.4.x to 2.2.x
2) migrate to a later BK 2.4.x kernel with the patch already included
(the patch has been in BK for around 9 months)
The interrupts-decoders patch (against 2.5.x, but same as against 2.4.x)
is changeset 1.838.172.14 at:
http://linux.bkbits.net:8080/linux-2.5/user=zaitcev/[EMAIL PROTECTED]|index.html|stats|!+|index.html|[EMAIL PROTECTED]|[EMAIL PROTECTED]
E
Heitzso wrote:
I ran the prtconf as you suggested and the following stanza
comes up for the qlogic controller:
Node 0xffd7b350
scsi-initiator-id: 0007
device_type: 'scsi'
interrupts: 0003
wide: 00
clock-frequency: 02625a00
reg: 0002.0001.0450
model: 'QLGC,ISP1000'
name: 'QLGC,isp'
Node 0xffd7edf0
device_type: 'block'
name: 'sd'
Node 0xffd7f340
device_type: 'byte'
name: 'st'
Which would appear that the controller is available(??).
However, if I have an external case attached to that
controller with drives in it I still get the no interrupts
found skipping controller etc. message.
Thanks for digging up the message in the driver.
Still no scsi controller. I'll slide on it since
I'm not in a position to thrash the code.
Heitzso
Eric Brower wrote:
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
Do you happen to have Solaris or Linux 'prtconf -pv' info for this
system? No workaround is mentioned, but perhaps this is due to no
intr property present in that FCode. Just a thought
Re: antares qlogic sbus scsi controller ?
The URL does not end at ...nav= so your email reader is probably not
hyperlinking the entire URL. Copy the entire line verbatim and it
should work fine (does for me).
I think the one-liner change should be good enough as a test point.
E
Heitzso wrote:
I've glanced at the patch at
http://linux.bkbits.net:8080/linux-2.5/user=zaitcev/[EMAIL PROTECTED]
(please confirm the URL, the full URL below didn't go anywhere, thanks).
I'll look at equiv 2.2.25 code then decide whether to go simple
test route or full backport merge. May be a few days before
I get to it.
My main thrash is trying to figure out why
postfix-tls-openssl-saslauthd-pam stopped sending out the sasl
auth modes recently. I'm rigging the ss20 to be a hopefully
stable SOHO edge box with mail server.
Heitzso
Eric Brower wrote:
Yep-- missing the intr property.
I'd suggest you have two choices:
1) backport my interrupts-decoders patch from current BK 2.4.x to 2.2.x
2) migrate to a later BK 2.4.x kernel with the patch already included
(the patch has been in BK for around 9 months)
The interrupts-decoders patch (against 2.5.x, but same as against
2.4.x) is changeset 1.838.172.14 at:
http://linux.bkbits.net:8080/linux-2.5/user=zaitcev/[EMAIL PROTECTED]|index.html|stats|!+|index.html|[EMAIL PROTECTED]|[EMAIL PROTECTED]
E
Heitzso wrote:
I ran the prtconf as you suggested and the following stanza
comes up for the qlogic controller:
Node 0xffd7b350
scsi-initiator-id: 0007
device_type: 'scsi'
interrupts: 0003
wide: 00
clock-frequency: 02625a00
reg: 0002.0001.0450
model: 'QLGC,ISP1000'
name: 'QLGC,isp'
Node 0xffd7edf0
device_type: 'block'
name: 'sd'
Node 0xffd7f340
device_type: 'byte'
name: 'st'
Which would appear that the controller is available(??).
However, if I have an external case attached to that
controller with drives in it I still get the no interrupts
found skipping controller etc. message.
Thanks for digging up the message in the driver.
Still no scsi controller. I'll slide on it since
I'm not in a position to thrash the code.
Heitzso
Eric Brower wrote:
Heitzso wrote:
I have an sbus antares (actually a qlogic)
fast/wide scsi2 controller in my ss20 that the
bootprom finds and solaris found and used but
my 2.2.25 kernel flags as missing an interrupt
and skips over.
I think you are talking seeing this:
/* Sometimes Antares cards come up not completely
* setup, and we get a report of a zero IRQ.
* Skip over them in such cases so we survive.
*/
if (sdev-irqs[0] == 0) {
printk(qpti%d: Adapter reports no interrupt,
skipping over this card., nqptis);
continue;
}
Do you happen to have Solaris or Linux 'prtconf -pv' info for this
system? No workaround is mentioned, but perhaps this is due to no
intr property present in that FCode. Just a thought
.
