Skip to contentSkip to conversation

AlphaPC+Sym53c8xx driver failure

DISCUSSION Kelledin 2 participants 5 messages Nov 1, 2002 – Nov 2, 2002 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 3DC2E30E.13470.26B6B20E@localhost

Kelledin

author
#1 lore raw
Quoted 3 lines · Martin Brulisauer

Did you apply the core_cia.c patch?
You can find it at
http://knowledge.bruli.net/uploads/core_cia-patch.txt

Thx, I did not know about that one...

Are there any other commonly-used patches to get 2.4 working on the Alpha? It seems Alpha support is just not seriously maintained in the stock kernel...

Signature · 3 lines
Kelledin
"If a server crashes in a server farm and no one pings it, does 
it still cost four figures to fix?"
author
#2 lore raw
Quoted 10 lines · Kelledin
Quoted 3 lines · Martin Brulisauer

Did you apply the core_cia.c patch?
You can find it at
http://knowledge.bruli.net/uploads/core_cia-patch.txt

Thx, I did not know about that one...

Are there any other commonly-used patches to get 2.4 working on the Alpha? It seems Alpha support is just not seriously maintained in the stock kernel...

Sadly, no luck on it. It doesn't seem to improve my situation at all. =(

Signature · 3 lines
Kelledin
"If a server crashes in a server farm and no one pings it, does 
it still cost four figures to fix?"
author
#3 lore raw

AlphaPC+Sym53c8xx driver failure, continued

Quoted 6 lines
Quoted 3 lines
Quoted 3 lines

Did you apply the core_cia.c patch?
You can find it at
http://knowledge.bruli.net/uploads/core_cia-patch.txt

Sadly, no luck on it. It doesn't seem to improve my situation at all. =(

I booted the Debian hack of 2.4.18 and got a little bit more informative set of debug messages:

ncr53c810-0: waiting 10 seconds for SCSI devices to settle...
freeing devtbl [8192] @fffffc0000dee000
scsi0: ncr53c8xx-3.4.3b-20010512
ncr53c810-0-<0,0>: CMD=12 ncr53c810-0: command processing resumed

ncr53c810-0-<0,0>: CMD=12 <6>ncr53c810-0-<0,0>: ccb \
    @fffffc0000de8000 using tag 255
ncr53c810-0: queuepos=3.
scsi : aborting command due to timeout: pid 0, scsi0, channel \
    0, id 0, lun 0 Inquiry 00 00 00 ff 00

ncr53c8xx_abort: pid=0 serial_number=1 serial_number_at_timeout=1
ncr53c810-0: abort ccb=fffffc0000de8000 (cancel)

...and again, that's all she wrote.

Would anyone know where to find the actual maintainer for the ncr53c8xx driver? It would appear to be Gerard Roudier, but I'd like to make sure before bugging him directly...

Signature · 3 lines
Kelledin
"If a server crashes in a server farm and no one pings it, does 
it still cost four figures to fix?"
author
#4 lore raw

Re: AlphaPC+SCSI, continued--SCSI layer broken?

Quoted 23 lines · Kelledin
Quoted 6 lines
Quoted 3 lines
Quoted 3 lines

Did you apply the core_cia.c patch?
You can find it at
http://knowledge.bruli.net/uploads/core_cia-patch.txt

Sadly, no luck on it. It doesn't seem to improve my situation at all. =(

I booted the Debian hack of 2.4.18 and got a little bit more informative set of debug messages:

ncr53c810-0: waiting 10 seconds for SCSI devices to settle...
freeing devtbl [8192] @fffffc0000dee000
scsi0: ncr53c8xx-3.4.3b-20010512
ncr53c810-0-<0,0>: CMD=12 ncr53c810-0: command processing resumed ncr53c810-0-<0,0>: CMD=12 <6>ncr53c810-0-<0,0>: ccb \
@fffffc0000de8000 using tag 255
ncr53c810-0: queuepos=3.
scsi : aborting command due to timeout: pid 0, scsi0, channel \ 0, id 0, lun 0 Inquiry 00 00 00 ff 00
ncr53c8xx_abort: pid=0 serial_number=1 serial_number_at_timeout=1 ncr53c810-0: abort ccb=fffffc0000de8000 (cancel)

Quoted 1 line

...and again, that's all she wrote.

Well, never mind the ncr53c8xx driver--the problem appears to be in the SCSI core code. I threw in a QLogic ISP1040 controller and had much the same results. Only difference is, I'm not sure how to gather debug output from the qlogicisp driver. All I have is the QLogic driver freezing at about the same point...

Signature · 3 lines
Kelledin
"If a server crashes in a server farm and no one pings it, does 
it still cost four figures to fix?"
#5 lore raw

Re: AlphaPC+Sym53c8xx driver failure, continued

In reply to Kelledin

Hello Kelledin , Two Questions

Quoted 1 line

scsi0: ncr53c8xx-3.4.3b-20010512

Why are you using this driver ? Tho it should work . But I am not sure if Gerard is maintaining it beyond bugs .

Won't the sym53x8xx-2 work/compile/...? Hth , JimL

+------------------------------------------------------------------+
| James W. Laferriere | System Techniques | Give me VMS |
| Network Engineer | P.O. Box 854 | Give me Linux |
| [email protected] | Coudersport PA 16915 | only on AXP |
+------------------------------------------------------------------+