Skip to contentSkip to conversation

Need testers with MESH SCSI

DISCUSSION Benjamin Herrenschmidt 3 participants 5 messages Dec 22, 2000 – Dec 27, 2000 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): [email protected]

#1 lore raw

Well, would have been a nice christmas present... BUT STILL:
(after applying the new mesh_init() to scsi/mesh.c)

mesh: target 6 aborted

which means that my UMAX Astra 1200S Scanner still does not work under linuxppc...

My System: Performa 6400, Kernel 2.2.15pre19

(a couple of months ago I found a message on the list how to enable scsi-debugging/logging, which magically made the scanner work -- slow and lots of debugs in log/messages. There must be a better way...)

Greetings

Wolfgang Haeuptli

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#2 lore raw
Quoted 9 lines

Well, would have been a nice christmas present... BUT STILL:
(after applying the new mesh_init() to scsi/mesh.c)

mesh: target 6 aborted

which means that my UMAX Astra 1200S Scanner still does not work under linuxppc...

Can you try increasing the udelay() calls in mesh_init() to see if it helps ? There maybe something else going on, but it's worth trying.

Ben.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#3 lore raw
Quoted 10 lines · Benjamin Herrenschmidt
Quoted 7 lines

Well, would have been a nice christmas present... BUT STILL:
(after applying the new mesh_init() to scsi/mesh.c)

mesh: target 6 aborted

which means that my UMAX Astra 1200S Scanner still does not work under linuxppc...

Can you try increasing the udelay() calls in mesh_init() to see if it helps ? There maybe something else going on, but it's worth trying.

Note that there can be other problems with the mesh as well: I remember I once had some early 2.3.x kernels that could not init the mesh when cold-booted, only when warm-booted. So I had to boot an older kernel first each time I had powered down my box :-)

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#4 lore raw
Quoted 2 lines

Note that there can be other problems with the mesh as well: I remember

I once

Quoted 3 lines

had some early 2.3.x kernels that could not init the mesh when cold-booted, only when warm-booted. So I had to boot an older kernel first each time I had powered down my box :-)

There were issues with powering up the MESH on some powerbooks that were fixed some time ago, but maybe your issue is unrelated.

Looking at Darwin's MESH driver, they have a whole bunch of workarounds for known issues (either with common device protocol errors, or MESH internal races).

Ben.

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

#5 lore raw
Quoted 8 lines · Benjamin Herrenschmidt
Quoted 1 line

Note that there can be other problems with the mesh as well: I remember

I once

Quoted 3 lines

had some early 2.3.x kernels that could not init the mesh when cold-booted, only when warm-booted. So I had to boot an older kernel first each time I had powered down my box :-)

There were issues with powering up the MESH on some powerbooks that were fixed some time ago, but maybe your issue is unrelated.

Yes, since I don't have a Powerbook, but a LongTrail.

Quoted 3 lines

Looking at Darwin's MESH driver, they have a whole bunch of workarounds for known issues (either with common device protocol errors, or MESH internal races).

I still see the

    mesh: halt_dma: data_ptr=-256 (nb=20736, ms=c06ff278)

(i.e. the DMA ptr shows it did 256 bytes too much), but I never noticed any file corruption during the 3.5 years I've been using this machine. Let's call it a harmless hardware bug.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/