[sym2] Re: Problem with 2.6.14 and up...

[sym2] Re: Problem with 2.6.14 and up...

[Matthew Wilcox]

Hi Jose, I was forwarded your bug report below.  It doesn't have quite
enough information in it for me to diagnose, but I have some suggestions
anyway ...

1. Can you send me your dmesg?  I want to see what devices these are and
   what transfer agreement they negotiate.
2. Can you try a later kernel?  If you have git, you can pull from
   git://git.kernel.org/pub/scm/linux/kernel/git/willy/sym2.git
   otherwise http://www.parisc-linux.org/~willy/sym2-2.2.2.diff applies
   to a 2.6.15-rc1 kernel.
3. Can you try an earlier kernel?  It'd be interesting to know if, say,
   2.6.8 worked.
4. Can you try the sym2 driver in 2.4.32?  You'll have to say Y to
   "SYM53C8XX Version 2 SCSI support".

----- Forwarded message from Andrew Morton <akpm@osdl.org> -----

> > Date: Mon, 21 Nov 2005 17:24:47 +0100
> > From: Jos? Luis S?nchez  <jsanchez@todounix.homeip.net>
> > To: linux-kernel@vger.kernel.org
> > Subject: Problem with 2.6.14 and up...
> > 
> > 
> > Hi,
> > 
> > >From 2.6.14 I have a nasty problem with my SCSI devices. First, see my HW:
> > 
> > ----------------------------------
> > 00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
> > (rev 03)
> > 00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge 
> > (rev 03)
> > 00:04.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
> > 00:04.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
> > 00:04.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
> > 00:04.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
> > 00:0a.0 SCSI storage controller: LSI Logic / Symbios Logic 53c875 (rev 26)
> > 00:0b.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 
> > 64)
> > 00:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 06)
> > 00:0d.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 
> > 06)
> > 01:00.0 VGA compatible controller: nVidia Corporation NV28 [GeForce4 Ti 4200 
> > AGP 8x] (rev a1)
> > ------------------------
> > 
> > I'm using the ncr53c8xx SCSI driver. When I run K3b, the program stalls a few 
> > minutes and this appears in the messages file:
> > 
> > sr0: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
> > Uniform CD-ROM driver Revision: 3.20
> > sr 0:0:1:0: Attached scsi CD-ROM sr0
> > sr1: scsi3-mmc drive: 24x/16x writer cd/rw xa/form2 cdda tray
> > sr 0:0:2:0: Attached scsi CD-ROM sr1
> > sd 0:0:0:0: Attached scsi generic sg0 type 0
> > sr 0:0:1:0: Attached scsi generic sg1 type 5
> > sr 0:0:2:0: Attached scsi generic sg2 type 5
> >  0:0:5:0: Attached scsi generic sg3 type 1
> > sr 0:0:2:0: phase change 2-1 12@01bbcf60 resid=6.
> > sr 0:0:2:0: ABORT operation started.
> > sr 0:0:2:0: ABORT operation timed-out.
> > sr 0:0:2:0: DEVICE RESET operation started.
> > sr 0:0:2:0: DEVICE RESET operation timed-out.
> > sr 0:0:2:0: BUS RESET operation started.
> > sym0: SCSI BUS reset detected.
> > sym0: SCSI BUS has been reset.
> > sr 0:0:2:0: BUS RESET operation complete.
> > sr 0:0:2:0: phase change 2-1 12@01bbcf60 resid=6.
> > Device not ready. Make sure there is a disc in the drive.
> > Device not ready. Make sure there is a disc in the drive.
> > sr 0:0:2:0: phase change 2-1 12@01bbcf60 resid=6.
> > sr 0:0:2:0: phase change 2-3 12@01bbcf60 resid=2.
> > sr 0:0:2:0: phase change 2-3 12@01bbcf60 resid=2.
> > sr 0:0:2:0: phase change 2-3 12@01bbcf60 resid=2.
> > ....
> > 
> > I'm very sure what the SCSI card, the cabling and the devices are OK, why 
> > don't have any problem with 2.4.32 kernel.
> > 
> > Ideas?
> > 
> > Jos? Luis
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/

----- End forwarded message -----

Re: [sym2] Re: Problem with 2.6.14 and up...

[Matthew Wilcox]

On Wed, Nov 23, 2005 at 06:43:27AM -0700, Matthew Wilcox wrote:
> 2. Can you try a later kernel?  If you have git, you can pull from
>    git://git.kernel.org/pub/scm/linux/kernel/git/willy/sym2.git
>    otherwise http://www.parisc-linux.org/~willy/sym2-2.2.2.diff applies
>    to a 2.6.15-rc1 kernel.

I also noticed that akpm put out 2.6.15-rc2-mm1 today which includes the
sym2 patches, so you could try that instead.

Re: [sym2] Re: Problem with 2.6.14 and up...

[José Luis Sánchez]

[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]

Hi Matthew,

El Miércoles, 23 de Noviembre de 2005 14:43, Matthew Wilcox escribió:
> Hi Jose, I was forwarded your bug report below.  It doesn't have quite
> enough information in it for me to diagnose, but I have some suggestions
> anyway ...
>
> 1. Can you send me your dmesg?  I want to see what devices these are and
>    what transfer agreement they negotiate.

Attached to this e-mail, is dmesg. For your information, my distribution is a 
Slackware 10.2 without tweaks.

> 2. Can you try a later kernel?  If you have git, you can pull from
>    git://git.kernel.org/pub/scm/linux/kernel/git/willy/sym2.git
>    otherwise http://www.parisc-linux.org/~willy/sym2-2.2.2.diff applies
>    to a 2.6.15-rc1 kernel.

Yes, I try it later, but with patience, why a P-III 500 Mhz isn't a fast 
machine to compile the linux kernel 2.6.

> 3. Can you try an earlier kernel?  It'd be interesting to know if, say,
>    2.6.8 worked.

Same as the point 2. :)

> 4. Can you try the sym2 driver in 2.4.32?  You'll have to say Y to
>    "SYM53C8XX Version 2 SCSI support".

I'm sorry, but that's my fault. The driver used is SYM53C88XX_2, not the 
ncr53C8xx. In 2.6 kernel isn't possible to select the NCR driver from 'make 
menuconfig'.

But with the kernel 2.4 I haven't any problem with this card, what works 
perfectly with WinXP (ouch!) and Solaris 10 x86.

If I can help to you, don't hesitate to ask me. :)

Best regards

[-- Attachment #2: dmesg.txt --]
[-- Type: text/plain, Size: 10263 bytes --]

Linux version 2.6.15-rc2 (root@mafalda) (gcc versión 3.3.6) #3 PREEMPT Mon Nov 21 16:36:18 CET 2005
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003fffd000 (usable)
 BIOS-e820: 000000003fffd000 - 000000003ffff000 (ACPI data)
 BIOS-e820: 000000003ffff000 - 0000000040000000 (ACPI NVS)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
127MB HIGHMEM available.
896MB LOWMEM available.
On node 0 totalpages: 262141
  DMA zone: 4096 pages, LIFO batch:2
  DMA32 zone: 0 pages, LIFO batch:2
  Normal zone: 225280 pages, LIFO batch:64
  HighMem zone: 32765 pages, LIFO batch:16
DMI 2.0 present.
Allocating PCI resources starting at 50000000 (gap: 40000000:bfff0000)
Built 1 zonelists
Kernel command line: BOOT_IMAGE=Linux-2.6.15 ro root=307 lapic
Local APIC disabled by BIOS -- reenabling.
Found and enabled local APIC!
mapped APIC to ffffd000 (fee00000)
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Detected 501.211 MHz processor.
Using tsc for high-res timesource
Console: colour dummy device 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1035392k/1048564k available (2261k kernel code, 12328k reserved, 637k data, 208k init, 131060k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Calibrating delay using timer specific routine.. 1003.74 BogoMIPS (lpj=2007489)
Mount-cache hash table entries: 512
CPU: After generic identify, caps: 0383fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: After vendor identify, caps: 0383fbff 00000000 00000000 00000000 00000000 00000000 00000000
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 512K
CPU: After all inits, caps: 0383fbff 00000000 00000000 00000040 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
mtrr: v2.0 (20020519)
CPU: Intel Pentium III (Katmai) stepping 03
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... OK.
NET: Registered protocol family 16
PCI: PCI BIOS revision 2.10 entry at 0xf0720, last bus=1
PCI: Using configuration type 1
usbcore: registered new driver usbfs
usbcore: registered new driver hub
Linux Plug and Play Support v0.97 (c) Adam Belay
Generic PHY: Registered new driver
SCSI subsystem initialized
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI quirk: region e400-e43f claimed by PIIX4 ACPI
PCI quirk: region e800-e80f claimed by PIIX4 SMB
PIIX4 devres B PIO at 0290-0297
Boot video device is 0000:01:00.0
PCI: Using IRQ router PIIX/ICH [8086/7110] at 0000:00:04.0
PCI: Bridge: 0000:00:01.0
  IO window: disabled.
  MEM window: c6000000-c7dfffff
  PREFETCH window: c7f00000-cfffffff
apm: BIOS version 1.2 Flags 0x0b (Driver version 1.16ac)
highmem bounce pool size: 64 pages
SGI XFS with no debug enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Limiting direct PCI/PCI transfers.
USB Universal Host Controller Interface driver v2.3
PCI: Found IRQ 5 for device 0000:00:04.2
PCI: Sharing IRQ 5 with 0000:00:0d.0
PCI: Setting latency timer of device 0000:00:04.2 to 64
uhci_hcd 0000:00:04.2: UHCI Host Controller
uhci_hcd 0000:00:04.2: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:04.2: irq 5, io base 0x0000d400
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usb 1-2: new low speed USB device using uhci_hcd and address 2
usbcore: registered new driver hiddev
input: Logitech USB-PS/2 Optical Mouse as /class/input/input0
input: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:04.2-2
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
vesafb: framebuffer at 0xc8000000, mapped to 0xf8800000, using 1536k, total 131072k
vesafb: mode is 1024x768x8, linelength=1024, pages=3
vesafb: protected mode interface info at c000:ea60
vesafb: scrolling: redraw
vesafb: Pseudocolor: size=8:8:8:8, shift=0:0:0:0
vesafb: Mode is VGA compatible
Console: switching to colour frame buffer device 128x48
fb0: VESA VGA frame buffer device
isapnp: Scanning for PnP cards...
isapnp: No Plug & Play device found
Real Time Clock Driver v1.12
PNP: No PS/2 controller found. Probing ports directly.
serio: i8042 AUX port at 0x60,0x64 irq 12
serio: i8042 KBD port at 0x60,0x64 irq 1
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
PCI: Found IRQ 10 for device 0000:00:0b.0
3c59x: Donald Becker and others. www.scyld.com/network/vortex.html
0000:00:0b.0: 3Com PCI 3c905B Cyclone 100baseTx at f8982000. Vers LK1.1.19
PCI: Setting latency timer of device 0000:00:0b.0 to 64
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PIIX4: IDE controller at PCI slot 0000:00:04.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: ST320414A, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ST320414A, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
hda: max request size: 128KiB
hda: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(33)
hda: cache flushes not supported
 hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
hdc: max request size: 128KiB
hdc: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(33)
hdc: cache flushes not supported
 hdc: hdc1
PCI: Found IRQ 12 for device 0000:00:0a.0
PCI: Setting latency timer of device 0000:00:0a.0 to 64
sym0: <875> rev 0x26 at pci 0000:00:0a.0 irq 12
sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking
sym0: SCSI BUS has been reset.
scsi0 : sym-2.2.1
  Vendor: SEAGATE   Model: ST39140W          Rev: 1487
  Type:   Direct-Access                      ANSI SCSI revision: 02
 target0:0:0: tagged command queuing enabled, command queue depth 16.
 target0:0:0: Beginning Domain Validation
 target0:0:0: asynchronous.
 target0:0:0: wide asynchronous.
 target0:0:0: Domain Validation skipping write tests
 target0:0:0: FAST-20 WIDE SCSI 40.0 MB/s ST (50 ns, offset 15)
 target0:0:0: Ending Domain Validation
  Vendor: TOSHIBA   Model: DVD-ROM SD-M1401  Rev: 1009
  Type:   CD-ROM                             ANSI SCSI revision: 02
 target0:0:1: Beginning Domain Validation
 target0:0:1: asynchronous.
 target0:0:1: Domain Validation skipping write tests
 target0:0:1: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 16)
 target0:0:1: Ending Domain Validation
  Vendor: YAMAHA    Model: CRW8424S          Rev: 1.0j
  Type:   CD-ROM                             ANSI SCSI revision: 02
 target0:0:2: Beginning Domain Validation
 target0:0:2: asynchronous.
 target0:0:2: Domain Validation skipping write tests
 target0:0:2: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 15)
 target0:0:2: Ending Domain Validation
  Vendor: HP        Model: C5683A            Rev: C005
  Type:   Sequential-Access                  ANSI SCSI revision: 02
 target0:0:5: Beginning Domain Validation
 target0:0:5: asynchronous.
 target0:0:5: Domain Validation skipping write tests
 target0:0:5: FAST-20 SCSI 20.0 MB/s ST (50 ns, offset 16)
 target0:0:5: Ending Domain Validation
SCSI device sda: 17783240 512-byte hdwr sectors (9105 MB)
SCSI device sda: drive cache: write back
SCSI device sda: 17783240 512-byte hdwr sectors (9105 MB)
SCSI device sda: drive cache: write back
 sda: sda1
sd 0:0:0:0: Attached scsi disk sda
mice: PS/2 mouse device common for all mice
NET: Registered protocol family 2
IP route cache hash table entries: 65536 (order: 6, 262144 bytes)
TCP established hash table entries: 262144 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 262144 bind 65536)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Using IPI Shortcut mode
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 208k freed
kjournald starting.  Commit interval 5 seconds
input: AT Translated Set 2 keyboard as /class/input/input1
Adding 530104k swap on /dev/hda6.  Priority:42 extents:1 across:530104k
EXT3 FS on hda7, internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
XFS mounting filesystem hda3
Ending clean XFS mount for filesystem: hda3
XFS mounting filesystem hda8
Ending clean XFS mount for filesystem: hda8
PCI: Found IRQ 10 for device 0000:00:0b.0
nvidia: module license 'NVIDIA' taints kernel.
NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module  1.0-7676  Fri Jul 29 12:58:54 PDT 2005
PCI: Found IRQ 5 for device 0000:00:0d.0
PCI: Sharing IRQ 5 with 0000:00:04.2
PCI: Setting latency timer of device 0000:00:0d.0 to 64
sr0: scsi3-mmc drive: 40x/40x cd/rw xa/form2 cdda tray
Uniform CD-ROM driver Revision: 3.20
sr 0:0:1:0: Attached scsi CD-ROM sr0
sr1: scsi3-mmc drive: 24x/16x writer cd/rw xa/form2 cdda tray
sr 0:0:2:0: Attached scsi CD-ROM sr1
sd 0:0:0:0: Attached scsi generic sg0 type 0
sr 0:0:1:0: Attached scsi generic sg1 type 5
sr 0:0:2:0: Attached scsi generic sg2 type 5
 0:0:5:0: Attached scsi generic sg3 type 1
st: Version 20050830, fixed bufsize 32768, s/g segs 256
st 0:0:5:0: Attached scsi tape st0<4>st0: try direct i/o: yes (alignment 512 B), max page reachable by HBA 1048575

Re: [sym2] Re: Problem with 2.6.14 and up...

[José Luis Sánchez]

El Miércoles, 23 de Noviembre de 2005 15:35, Matthew Wilcox escribió:
> On Wed, Nov 23, 2005 at 06:43:27AM -0700, Matthew Wilcox wrote:
> > 2. Can you try a later kernel?  If you have git, you can pull from
> >    git://git.kernel.org/pub/scm/linux/kernel/git/willy/sym2.git
> >    otherwise http://www.parisc-linux.org/~willy/sym2-2.2.2.diff applies
> >    to a 2.6.15-rc1 kernel.
>
> I also noticed that akpm put out 2.6.15-rc2-mm1 today which includes the
> sym2 patches, so you could try that instead.

I've tried the patch in a 2.6.15-rc2 (patched OK) with the same result, a bus 
reset and a bunch of "phase change..." messages. Any probe what I can try to 
stress the driver?

Another minor glitch never reported is what the device id 5 is a DDS-4 DAT, 
with a UW interface. But the driver reports a synchronous speed of 20 MB/sec, 
I don't know why...
In Solaris 10 x86 this DAT works very well at 40 MB/sec. This problem exists 
from all the 2.4 kernel series.

Thanks for your help.
Jose Luis
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [sym2] Re: Problem with 2.6.14 and up...

[Matthew Wilcox]

On Wed, Nov 23, 2005 at 05:23:44PM +0100, Jos? Luis S?nchez wrote:
> El Mi?rcoles, 23 de Noviembre de 2005 15:35, Matthew Wilcox escribi?:
> > On Wed, Nov 23, 2005 at 06:43:27AM -0700, Matthew Wilcox wrote:
> > > 2. Can you try a later kernel?  If you have git, you can pull from
> > >    git://git.kernel.org/pub/scm/linux/kernel/git/willy/sym2.git
> > >    otherwise http://www.parisc-linux.org/~willy/sym2-2.2.2.diff applies
> > >    to a 2.6.15-rc1 kernel.
> >
> > I also noticed that akpm put out 2.6.15-rc2-mm1 today which includes the
> > sym2 patches, so you could try that instead.
> 
> I've tried the patch in a 2.6.15-rc2 (patched OK) with the same result, a bus 
> reset and a bunch of "phase change..." messages. Any probe what I can try to 
> stress the driver?

Hmm.  Not sure at this point.  Let me think about it for a bit.

> Another minor glitch never reported is what the device id 5 is a DDS-4 DAT, 
> with a UW interface. But the driver reports a synchronous speed of 20 MB/sec, 
> I don't know why...
> In Solaris 10 x86 this DAT works very well at 40 MB/sec. This problem exists 
> from all the 2.4 kernel series.

Seems to me that it's not negotiating wide, for some reason.
	cat /sys/class/spi_transport/target0:0:5/width
(should be 0)
Then try
	echo 1 >/sys/class/spi_transport/target0:0:5/width

You'll then have to get it to perform some IO to the device -- an
'mt status' should do the trick.

Re: [sym2] Re: Problem with 2.6.14 and up...

[Matthew Wilcox]

On Wed, Nov 23, 2005 at 04:56:22PM +0100, Jos? Luis S?nchez wrote:
> > 4. Can you try the sym2 driver in 2.4.32?  You'll have to say Y to
> >    "SYM53C8XX Version 2 SCSI support".
> 
> I'm sorry, but that's my fault. The driver used is SYM53C88XX_2, not the 
> ncr53C8xx. In 2.6 kernel isn't possible to select the NCR driver from 'make 
> menuconfig'.

Right.  We made the ncr53c8xx driver responsible only for 53c720 chips
in 2.6.  What I was hoping you could try was the SYM53C88XX_2 driver in
2.4.

> nvidia: module license 'NVIDIA' taints kernel.
> NVRM: loading NVIDIA Linux x86 NVIDIA Kernel Module  1.0-7676  Fri Jul 29 12:58:54 PDT 2005

mmm.  can you try to reproduce the problem without having the Nvidia
module loaded?

Re: [sym2] Re: Problem with 2.6.14 and up...

[José Luis Sánchez]

El Miércoles, 23 de Noviembre de 2005 15:35, Matthew Wilcox escribió:
> On Wed, Nov 23, 2005 at 06:43:27AM -0700, Matthew Wilcox wrote:
> > 2. Can you try a later kernel?  If you have git, you can pull from
> >    git://git.kernel.org/pub/scm/linux/kernel/git/willy/sym2.git
> >    otherwise http://www.parisc-linux.org/~willy/sym2-2.2.2.diff applies
> >    to a 2.6.15-rc1 kernel.
>
> I also noticed that akpm put out 2.6.15-rc2-mm1 today which includes the
> sym2 patches, so you could try that instead.

Well, I have probed the Linux kernels from 2.6.11 to 2.6.14, without using the 
NVidia display driver, only DRM and agpgart drivers. The problem appears at 
2.6.14, from 2.6.11 to 2.6.13 all works well. Now, I guess what is a problem 
related to the SCSI layer and not to the sym53c8xx_2 driver (2.6.14 don't 
have any patch to the sym2 driver).

Thanks for your help and patience. :)
Jose Luis
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [sym2] Re: Problem with 2.6.14 and up...

[Matthew Wilcox]

On Thu, Nov 24, 2005 at 12:13:17AM +0100, Jos? Luis S?nchez wrote:
> Well, I have probed the Linux kernels from 2.6.11 to 2.6.14, without using the 
> NVidia display driver, only DRM and agpgart drivers. The problem appears at 
> 2.6.14, from 2.6.11 to 2.6.13 all works well. Now, I guess what is a problem 
> related to the SCSI layer and not to the sym53c8xx_2 driver (2.6.14 don't 
> have any patch to the sym2 driver).

Hm.  Well, that makes me feel better.  I'd still like to find out why
your tape drive is only negotiating 20MB/s rather than the 40MB/s it
negotiates under Solaris though.  Did you try setting it to wide?

Re: [sym2] Re: Problem with 2.6.14 and up...

[José Luis Sánchez]

El Miércoles, 23 de Noviembre de 2005 17:43, Matthew Wilcox escribió:

> Seems to me that it's not negotiating wide, for some reason.
> 	cat /sys/class/spi_transport/target0:0:5/width
> (should be 0)
> Then try
> 	echo 1 >/sys/class/spi_transport/target0:0:5/width
>
> You'll then have to get it to perform some IO to the device -- an
> 'mt status' should do the trick.

mafalda:/home/jsanchez# echo 1> /sys/class/spi_transport/target0\:0\:5/width
mafalda:/home/jsanchez# mt status
SCSI 2 tape drive:
File number=-1, block number=-1, partition=0.
Tape block size 0 bytes. Density code 0x0 (default).
Soft error count since last status=0
General status bits on (50000):
 DR_OPEN IM_REP_EN
mafalda:/home/jsanchez# cat /sys/class/spi_transport/target0\:0\:5/width
0

Don't work...
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html