2.5.43 aic7xxx segfault sd_synchronize_cache() called after SHT-> release()

2.5.43 aic7xxx segfault sd_synchronize_cache() called after SHT-> release()

[Adam Radford]

I think sd_synchronize_cache() is getting called after SHT->release()
function,
which couldn't possibly be right.  This causes adaptec, 3ware, etc, to
segfault
on rmmod.

See below for adaptec segfault output:

aic7xxx
CPU:    1
EIP:    0060:[<c025918b>]    Not tainted
EFLAGS: 00010202
EIP is at put_device+0x7b/0xa0
eax: 00000000   ebx: c8997028   ecx: 00000001   edx: c0465470
esi: c12f4174   edi: c8997000   ebp: 00000000   esp: c5b81ee4
ds: 0068   es: 0068   ss: 0068
Process rmmod (pid: 1085, threadinfo=c5b80000 task=c5d4a800)
Stack: c8997028 c0481e20 c02d0f3a c8997028 c8997028 c0481f3c c8997028
c0481f4c
       00000000 c66fe1e8 00000286 c798aa00 c0481e20 c12f4000 c13b5000
c02be9aa
       c12f4000 c5b81f30 00000002 00030002 00000002 08072009 c042399f
08071fff
Call Trace:
 [<c02d0f3a>] sg_detach+0x20a/0x240
 [<c02be9aa>] scsi_unregister_host+0x26a/0x5f0
 [<c01418d8>] __alloc_pages+0x88/0x270
 [<c892f12a>] exit_this_scsi_driver+0xa/0xc [aic7xxx]
 [<c893a740>] driver_template+0x0/0x70 [aic7xxx]
 [<c012029e>] free_module+0x1e/0x140
 [<c011f3db>] sys_delete_module+0x1db/0x4c0
 [<c010787f>] syscall_call+0x7/0xb

Code: 0f 0b 0d 01 86 69 3d c0 8b 83 d4 00 00 00 85 c0 74 04 53 ff
 Segmentation fault
[root@localhost boot]#

--
Adam Radford
Software Engineer
3ware, Inc.

Re: 2.5.43 aic7xxx segfault sd_synchronize_cache() called after SHT-> release()

[Patrick Mansfield]

On Wed, Oct 16, 2002 at 12:41:14PM -0700, Adam Radford wrote:
> I think sd_synchronize_cache() is getting called after SHT->release()
> function,
> which couldn't possibly be right.  This causes adaptec, 3ware, etc, to
> segfault
> on rmmod.
> 
> See below for adaptec segfault output:
> 
> aic7xxx
> CPU:    1
> EIP:    0060:[<c025918b>]    Not tainted
> EFLAGS: 00010202
> EIP is at put_device+0x7b/0xa0
> eax: 00000000   ebx: c8997028   ecx: 00000001   edx: c0465470
> esi: c12f4174   edi: c8997000   ebp: 00000000   esp: c5b81ee4
> ds: 0068   es: 0068   ss: 0068
> Process rmmod (pid: 1085, threadinfo=c5b80000 task=c5d4a800)
> Stack: c8997028 c0481e20 c02d0f3a c8997028 c8997028 c0481f3c c8997028
> c0481f4c
>        00000000 c66fe1e8 00000286 c798aa00 c0481e20 c12f4000 c13b5000
> c02be9aa
>        c12f4000 c5b81f30 00000002 00030002 00000002 08072009 c042399f
> 08071fff
> Call Trace:
>  [<c02d0f3a>] sg_detach+0x20a/0x240
>  [<c02be9aa>] scsi_unregister_host+0x26a/0x5f0
>  [<c01418d8>] __alloc_pages+0x88/0x270
>  [<c892f12a>] exit_this_scsi_driver+0xa/0xc [aic7xxx]
>  [<c893a740>] driver_template+0x0/0x70 [aic7xxx]
>  [<c012029e>] free_module+0x1e/0x140
>  [<c011f3db>] sys_delete_module+0x1db/0x4c0
>  [<c010787f>] syscall_call+0x7/0xb
> 
> Code: 0f 0b 0d 01 86 69 3d c0 8b 83 d4 00 00 00 85 c0 74 04 53 ff

Are you sure it is not a BUG? This looks just like what Badari reported
yesterday:

kernel BUG at drivers/base/core.c:251!
invalid operand: 0000
qla2200
CPU:    0
EIP:    0060:[<c023eb24>]    Not tainted
EFLAGS: 00010202
EIP is at put_device+0x64/0x90
eax: 00000000   ebx: f8a08028   ecx: f8a080c4   edx: 00000001
esi: c3aded54   edi: f8a08000   ebp: 00000003   esp: cb007ee4
ds: 0068   es: 0068   ss: 0068
Process rmmod (pid: 4803, threadinfo=cb006000 task=f62c98c0)
Stack: f8a08028 c0477a40 c02ce533 f8a08028 f8a08028 c0477b5c f8a08028 c0477b6c
       00000000 40153f6d 00000286 f68fc000 c0477a40 c3adec00 f4df0000 c02a7a9a
       c3adec00 cb007f30 00000002 00030002 00000001 08071002 c041685c 08070ffd  
Call Trace:
 [<c02ce533>] sg_detach+0x1e3/0x210
 [<c02a7a9a>] scsi_unregister_host+0x26a/0x5d0
 [<c01f4736>] __generic_copy_to_user+0x56/0x80
 [<c013e4e8>] __alloc_pages+0x98/0x270
 [<f89e7cba>] exit_this_scsi_driver+0xa/0x10 [qla2200]
 [<f8a00360>] driver_template+0x0/0x74 [qla2200]
 [<c011ea0e>] free_module+0x1e/0x130
 [<c011dc94>] sys_delete_module+0x1b4/0x410
 [<c01075e3>] syscall_call+0x7/0xb

I posted a patch to change the put_device() calls to device_unregister(),
st.c got fixed in 2.5.43, these are still not fixed in 2.5.43:

--- linux-2.5.43/drivers/scsi/scsi.c	Tue Oct 15 20:28:22 2002
+++ linux-2.5.43-unreg/drivers/scsi/scsi.c	Wed Oct 16 12:50:08 2002
@@ -2248,7 +2248,7 @@
 			if (shpnt->hostt->slave_detach)
 				(*shpnt->hostt->slave_detach) (SDpnt);
 			devfs_unregister (SDpnt->de);
-			put_device(&SDpnt->sdev_driverfs_dev);
+			device_unregister(&SDpnt->sdev_driverfs_dev);
 		}
 	}
 
@@ -2299,7 +2299,7 @@
 		/* Remove the /proc/scsi directory entry */
 		sprintf(name,"%d",shpnt->host_no);
 		remove_proc_entry(name, tpnt->proc_dir);
-		put_device(&shpnt->host_driverfs_dev);
+		device_unregister(&shpnt->host_driverfs_dev);
 		if (tpnt->release)
 			(*tpnt->release) (shpnt);
 		else {
--- linux-2.5.43/drivers/scsi/sg.c	Tue Oct 15 20:27:57 2002
+++ linux-2.5.43-unreg/drivers/scsi/sg.c	Wed Oct 16 12:50:25 2002
@@ -1611,7 +1611,7 @@
 		sdp->de = NULL;
 		device_remove_file(&sdp->sg_driverfs_dev, &dev_attr_type);
 		device_remove_file(&sdp->sg_driverfs_dev, &dev_attr_kdev);
-		put_device(&sdp->sg_driverfs_dev);
+		device_unregister(&sdp->sg_driverfs_dev);
 		if (NULL == sdp->headfp)
 			vfree((char *) sdp);
 	}

NCR adaptor doesn't see devices (was: 2.5.43 aic7xxx segfault)

[davidsen]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2621 bytes --]

On Wed, 16 Oct 2002, Patrick Mansfield wrote:

> On Wed, Oct 16, 2002 at 12:41:14PM -0700, Adam Radford wrote:
> > I think sd_synchronize_cache() is getting called after SHT->release()
> > function,
> > which couldn't possibly be right.  This causes adaptec, 3ware, etc, to
> > segfault
> > on rmmod.
> > 
> > See below for adaptec segfault output:
        [ let's not ]
> Are you sure it is not a BUG? This looks just like what Badari reported
> yesterday:
        [ more BUG output snipped ]
> I posted a patch to change the put_device() calls to device_unregister(),
> st.c got fixed in 2.5.43, these are still not fixed in 2.5.43:

I got the same type of thing in 2.5.43, 43-mm2. Applied the patch below 
and the BUG went away. Unfortunately the NCR still doesn't see the 
attached devices, normally a CD and tape drive. I pulled the tape drive to 
see if that helps, it didn't. All works just fine with 2.4.recent. dmesg 
output attached to preserve format.
 
> --- linux-2.5.43/drivers/scsi/scsi.c	Tue Oct 15 20:28:22 2002
> +++ linux-2.5.43-unreg/drivers/scsi/scsi.c	Wed Oct 16 12:50:08 2002
> @@ -2248,7 +2248,7 @@
>  			if (shpnt->hostt->slave_detach)
>  				(*shpnt->hostt->slave_detach) (SDpnt);
>  			devfs_unregister (SDpnt->de);
> -			put_device(&SDpnt->sdev_driverfs_dev);
> +			device_unregister(&SDpnt->sdev_driverfs_dev);
>  		}
>  	}
>  
> @@ -2299,7 +2299,7 @@
>  		/* Remove the /proc/scsi directory entry */
>  		sprintf(name,"%d",shpnt->host_no);
>  		remove_proc_entry(name, tpnt->proc_dir);
> -		put_device(&shpnt->host_driverfs_dev);
> +		device_unregister(&shpnt->host_driverfs_dev);
>  		if (tpnt->release)
>  			(*tpnt->release) (shpnt);
>  		else {
> --- linux-2.5.43/drivers/scsi/sg.c	Tue Oct 15 20:27:57 2002
> +++ linux-2.5.43-unreg/drivers/scsi/sg.c	Wed Oct 16 12:50:25 2002
> @@ -1611,7 +1611,7 @@
>  		sdp->de = NULL;
>  		device_remove_file(&sdp->sg_driverfs_dev, &dev_attr_type);
>  		device_remove_file(&sdp->sg_driverfs_dev, &dev_attr_kdev);
> -		put_device(&sdp->sg_driverfs_dev);
> +		device_unregister(&sdp->sg_driverfs_dev);
>  		if (NULL == sdp->headfp)
>  			vfree((char *) sdp);
>  	}
> -
> 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/
> 
> 
> 

-- 
bill davidsen, CTO TMR Associates, Inc <davidsen@tmr.com>
  Having the feature freeze for Linux 2.5 on Hallow'een is appropriate,
since using 2.5 kernels includes a lot of things jumping out of dark
corners to scare you.

[-- Attachment #2: Type: TEXT/PLAIN, Size: 14277 bytes --]

Linux version 2.5.43-mm2 (root@bilbo.tmr.com) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-112)) #3 SMP Sat Oct 19 08:39:46 EDT 2002
Video mode to be used for restore is ffff
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
 BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 0000000010000000 (usable)
 BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
256MB LOWMEM available.
found SMP MP-table at 000f5b30
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f1000 reserved twice.
hm, page 000f2000 reserved twice.
On node 0 totalpages: 65536
  DMA zone: 4096 pages, LIFO batch:1
  Normal zone: 61440 pages, LIFO batch:15
  HighMem zone: 0 pages, LIFO batch:1
Intel MultiProcessor Specification v1.1
    Virtual Wire compatibility mode.
OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Processor #0 6:6 APIC version 17
Processor #1 6:6 APIC version 17
I/O APIC #2 Version 17 at 0xFEC00000.
Enabling APIC mode:  Flat.  Using 1 I/O APICs
Processors: 2
Building zonelist for node : 0
Kernel command line: auto BOOT_IMAGE=2.5.43-mm2 ro root=305 BOOT_FILE=/boot/vmlinuz-2.5.43-mm2 hdc=ide-scsi
ide_setup: hdc=ide-scsi
Initializing CPU#0
Detected 498.058 MHz processor.
Console: colour VGA+ 80x25
Calibrating delay loop... 985.08 BogoMIPS
Memory: 255104k/262144k available (1832k kernel code, 6276k reserved, 1294k data, 132k init, 0k highmem)
Security Scaffold v1.0.0 initialized
Dentry cache hash table entries: 32768 (order: 6, 262144 bytes)
Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
CPU: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After vendor init, caps: 0183fbff 00000000 00000000 00000000
Intel machine check architecture supported.
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
Enabling fast FPU save and restore... done.
Checking 'hlt' instruction... OK.
POSIX conformance testing by UNIFIX
CPU: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After vendor init, caps: 0183fbff 00000000 00000000 00000000
Intel machine check reporting enabled on CPU#0.
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU0: Intel Celeron (Mendocino) stepping 05
per-CPU timeslice cutoff: 365.46 usecs.
task migration cache decay timeout: 1 msecs.
enabled ExtINT on CPU#0
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Booting processor 1/1 eip 2000
Initializing CPU#1
masked ExtINT on CPU#1
ESR value before enabling vector: 00000000
ESR value after enabling vector: 00000000
Calibrating delay loop... 993.28 BogoMIPS
CPU: Before vendor init, caps: 0183fbff 00000000 00000000, vendor = 0
CPU: L1 I cache: 16K, L1 D cache: 16K
CPU: L2 cache: 128K
CPU: After vendor init, caps: 0183fbff 00000000 00000000 00000000
Intel machine check reporting enabled on CPU#1.
CPU:     After generic, caps: 0183fbff 00000000 00000000 00000000
CPU:             Common caps: 0183fbff 00000000 00000000 00000000
CPU1: Intel Celeron (Mendocino) stepping 05
Total of 2 processors activated (1978.36 BogoMIPS).
ENABLING IO-APIC IRQs
Setting 2 in the phys_id_present_map
...changing IO-APIC physical APIC ID to 2 ... ok.
init IO_APIC IRQs
 IO-APIC (apicid-pin) 2-0, 2-9, 2-10, 2-11, 2-17, 2-20, 2-21, 2-22, 2-23 not connected.
..TIMER: vector=0x31 pin1=2 pin2=0
number of MP IRQ sources: 16.
number of IO-APIC #2 registers: 24.
testing the IO APIC.......................

IO APIC #2......
.... register #00: 02000000
.......    : physical APIC id: 02
.... register #01: 00170011
.......     : max redirection entries: 0017
.......     : PRQ implemented: 0
.......     : IO APIC version: 0011
.... register #02: 00000000
.......     : arbitration: 00
.... IRQ redirection table:
 NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:   
 00 000 00  1    0    0   0   0    0    0    00
 01 001 01  0    0    0   0   0    1    1    39
 02 001 01  0    0    0   0   0    1    1    31
 03 001 01  0    0    0   0   0    1    1    41
 04 001 01  0    0    0   0   0    1    1    49
 05 001 01  0    0    0   0   0    1    1    51
 06 001 01  0    0    0   0   0    1    1    59
 07 001 01  0    0    0   0   0    1    1    61
 08 001 01  0    0    0   0   0    1    1    69
 09 000 00  1    0    0   0   0    0    0    00
 0a 000 00  1    0    0   0   0    0    0    00
 0b 000 00  1    0    0   0   0    0    0    00
 0c 001 01  0    0    0   0   0    1    1    71
 0d 001 01  0    0    0   0   0    1    1    79
 0e 001 01  0    0    0   0   0    1    1    81
 0f 001 01  0    0    0   0   0    1    1    89
 10 001 01  1    1    0   1   0    1    1    91
 11 000 00  1    0    0   0   0    0    0    00
 12 001 01  1    1    0   1   0    1    1    99
 13 001 01  1    1    0   1   0    1    1    A1
 14 000 00  1    0    0   0   0    0    0    00
 15 000 00  1    0    0   0   0    0    0    00
 16 000 00  1    0    0   0   0    0    0    00
 17 000 00  1    0    0   0   0    0    0    00
IRQ to pin mappings:
IRQ0 -> 0:2
IRQ1 -> 0:1
IRQ3 -> 0:3
IRQ4 -> 0:4
IRQ5 -> 0:5
IRQ6 -> 0:6
IRQ7 -> 0:7
IRQ8 -> 0:8
IRQ9 -> 0:19
IRQ10 -> 0:16
IRQ11 -> 0:18
IRQ12 -> 0:12
IRQ13 -> 0:13
IRQ14 -> 0:14
IRQ15 -> 0:15
.................................... done.
Using local APIC timer interrupts.
calibrating APIC timer ...
..... CPU clock speed is 497.0945 MHz.
..... host bus clock speed is 82.0990 MHz.
checking TSC synchronization across 2 CPUs: passed.
Starting migration thread for cpu 0
Bringing up 1
CPU 1 IS NOW UP!
Starting migration thread for cpu 1
CPUS done 4294967295
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
mtrr: v2.0 (20020519)
PCI: PCI BIOS revision 2.10 entry at 0xfb420, last bus=1
PCI: Using configuration type 1
adding '' to cpu class interfaces
adding '' to cpu class interfaces
drivers/usb/core/usb.c: registered new driver hub
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Using IRQ router PIIX [8086/7110] at 00:07.0
slab: reap timer started for cpu 0
slab: reap timer started for cpu 1
Starting kswapd
BIO: pool of 256 setup, 14Kb (56 bytes/bio)
biovec pool[0]:   1 bvecs: 256 entries (12 bytes)
biovec pool[1]:   4 bvecs: 256 entries (48 bytes)
biovec pool[2]:  16 bvecs: 256 entries (192 bytes)
biovec pool[3]:  64 bvecs: 256 entries (768 bytes)
biovec pool[4]: 128 bvecs: 256 entries (1536 bytes)
biovec pool[5]: 256 bvecs: 256 entries (3072 bytes)
aio_setup: sizeof(struct page) = 40
Journalled Block Device driver loaded
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
Capability LSM initialized
Limiting direct PCI/PCI transfers.
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing enabled
ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
Generic RTC Driver v1.06
Linux agpgart interface v0.99 (c) Jeff Hartmann
agpgart: Maximum main memory to use for agp memory: 204M
agpgart: Detected Intel 440BX chipset
agpgart: AGP aperture is 64M @ 0xe0000000
block request queues:
 128 requests per read queue
 128 requests per write queue
 8 requests per batch
 enter congestion at 31
 exit congestion at 33
Floppy drive(s): fd0 is 1.44M
FDC 0 is a post-1991 82077
loop: loaded (max 8 devices)
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 00:07.1
PIIX4: chipset revision 1
PIIX4: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:pio
hda: WDC AC26400R, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: SONY CD-RW CRX140E, ATAPI CD/DVD-ROM drive
hdd: IOMEGA ZIP 100 ATAPI, ATAPI FLOPPY drive
ide1 at 0x170-0x177,0x376 on irq 15
HPT366: onboard version of chipset, pin1=1 pin2=2
HPT366: IDE controller at PCI slot 00:13.0
PCI: Enabling device 00:13.0 (0005 -> 0007)
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0xe000-0xe007, BIOS settings: hde:DMA, hdf:pio
    ide3: BM-DMA at 0xec00-0xec07, BIOS settings: hdg:pio, hdh:pio
hde: WDC WD205BA, ATA DISK drive
ide2 at 0xd800-0xd807,0xdc02 on irq 11
hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_no_data_intr: error=0x04 { DriveStatusError }
hda: host protected area => 1
hda: 12594960 sectors (6449 MB) w/512KiB Cache, CHS=784/255/63, UDMA(33)
 hda: hda1 hda2 hda3 hda4 < hda5 >
hde: host protected area => 1
hde: 40088160 sectors (20525 MB) w/2048KiB Cache, CHS=39770/16/63, UDMA(66)
 hde: hde1
SCSI subsystem driver Revision: 1.00
sym53c8xx: at PCI bus 0, device 9, function 0
sym53c8xx: not initializing, device not supported
request_module[scsi_hostadapter]: not ready
Linux Kernel Card Services 3.1.22
  options:  [pci] [cardbus]
Intel PCIC probe: 
  Vadem VG-468 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 2 sockets
    host opts [0]: none
    host opts [1]: none
    ISA irqs (scanned) = 3,4,5,7 polling interval = 1000 ms
Databook TCIC-2 PCMCIA probe: not found.
drivers/usb/host/uhci-hcd.c: USB Universal Host Controller Interface driver v2.0
drivers/usb/core/hcd-pci.c: uhci-hcd @ 00:07.2, Intel Corp. 82371AB/EB/MB PIIX4 USB
drivers/usb/core/hcd-pci.c: irq 9, io base 0000d000
drivers/usb/core/hcd.c: new USB bus registered, assigned bus number 1
drivers/usb/core/hub.c: USB hub found at 0
drivers/usb/core/hub.c: 2 ports detected
Initializing USB Mass Storage driver...
drivers/usb/core/usb.c: registered new driver usb-storage
USB Mass Storage support registered.
register interface 'mouse' with class 'input
mice: PS/2 mouse device common for all mice
logibm.c: Didn't find Logitech busmouse at 0x23c
input: PC Speaker
input: PS/2 Generic Mouse on isa0060/serio1
serio: i8042 AUX port at 0x60,0x64 irq 12
input: AT Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1
es1371: version v0.30 time 17:32:29 Oct 18 2002
NET4: Linux TCP/IP 1.0 for NET4.0
IP: routing cache hash table of 2048 buckets, 16Kbytes
TCP: Hash tables configured (established 16384 bind 16384)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 132k freed
Adding 409648k swap on /dev/hda2.  Priority:-1 extents:1
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,5), internal journal
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,1), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting.  Commit interval 5 seconds
EXT3 FS 2.4-0.9.16, 02 Dec 2001 on ide0(3,3), internal journal
EXT3-fs: mounted filesystem with ordered data mode.
scsi0 : SCSI host adapter emulation for IDE ATAPI devices
  Vendor: SONY      Model: CD-RW  CRX140E    Rev: 1.0n
  Type:   CD-ROM                             ANSI SCSI revision: 02
  Vendor: IOMEGA    Model: ZIP 100           Rev: 14.A
  Type:   Direct-Access                      ANSI SCSI revision: 00
Attached scsi removable disk sda at scsi0, channel 0, id 1, lun 0
SCSI device sda: drive cache: write back
ncr53c8xx: at PCI bus 0, device 9, function 0
ncr53c8xx: 53c825 detected 
ncr53c825-0: rev 0x2 on pci bus 0 device 9 function 0 irq 9
ncr53c825-0: ID 7, Fast-10, Parity Checking
scsi1 : ncr53c8xx-3.4.3b-20010512
ncr53c825-0-<2,*>: target did not report SYNC.
  Vendor: PHILIPS   Model: CDD2600           Rev: 1.07
  Type:   CD-ROM                             ANSI SCSI revision: 02
SCSI device sda: drive cache: write back
sda : READ CAPACITY failed.
sda : status=1, message=00, host=0, driver=00 
sda : sense not available. 
sda: Write Protect is off
sda: Mode Sense: 45 00 00 08
ncr53c825-0: releasing host resources
ncr53c825-0: resetting chip
ncr53c825-0: host resources successfully released
scsi : 1 host left.
parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,EPP]
parport0: irq 7 detected
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
parport0: cpp_daisy: aa5500ff(38)
parport0: assign_addrs: aa5500ff(38)
ncr53c8xx: at PCI bus 0, device 9, function 0
ncr53c8xx: 53c825 detected 
ncr53c825-0: rev 0x2 on pci bus 0 device 9 function 0 irq 9
ncr53c825-0: ID 7, Fast-10, Parity Checking
scsi1 : ncr53c8xx-3.4.3b-20010512
ncr53c825-0-<2,*>: target did not report SYNC.
  Vendor: PHILIPS   Model: CDD2600           Rev: 1.07
  Type:   CD-ROM                             ANSI SCSI revision: 02
ncr53c825-0: releasing host resources
ncr53c825-0: resetting chip
ncr53c825-0: host resources successfully released
scsi : 1 host left.
isapnp: Scanning for PnP cards...
isapnp: Card 'NE2000 PLUG & PLAY ETHERNET CARD'
isapnp: 1 Plug & Play card detected total
ne.c:v1.10 9/23/94 Donald Becker (becker@scyld.com)
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0x300: 00 00 e8 46 6d a1
eth0: NE2000 found at 0x300, using IRQ 3.
eth0: interrupt from stopped card
ne.c: ISAPnP reports Generic PNP at i/o 0x220, irq 5.
NE*000 ethercard probe at 0x220: 00 00 e8 46 6d a1
eth1: NE2000 found at 0x220, using IRQ 5.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x290-0x297 0x378-0x37f 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: excluding 0xa20-0xa2f

Re: NCR adaptor doesn't see devices (was: 2.5.43 aic7xxx segfault)

[Mr. James W. Laferriere]

	Hello Davidsen ,  I hope the Sym-2 driver is what you are using ?
	From the dmesg output I suspect that is not the case .  If there
	is only the one Symbios/LSI driver I hope it is the Sym-2
	version .  Hth ,  JimL

On Sat, 19 Oct 2002, davidsen wrote:
> On Wed, 16 Oct 2002, Patrick Mansfield wrote:
> > On Wed, Oct 16, 2002 at 12:41:14PM -0700, Adam Radford wrote:
> > > I think sd_synchronize_cache() is getting called after SHT->release()
> > > function,
> > > which couldn't possibly be right.  This causes adaptec, 3ware, etc, to
> > > segfault
> > > on rmmod.
> > > See below for adaptec segfault output:
>         [ let's not ]
> > Are you sure it is not a BUG? This looks just like what Badari reported
> > yesterday:
>         [ more BUG output snipped ]
> > I posted a patch to change the put_device() calls to device_unregister(),
> > st.c got fixed in 2.5.43, these are still not fixed in 2.5.43:
>
> I got the same type of thing in 2.5.43, 43-mm2. Applied the patch below
> and the BUG went away. Unfortunately the NCR still doesn't see the
> attached devices, normally a CD and tape drive. I pulled the tape drive to
> see if that helps, it didn't. All works just fine with 2.4.recent. dmesg
> output attached to preserve format.
--
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

Re: NCR adaptor doesn't see devices (was: 2.5.43 aic7xxx segfault)

[Bill Davidsen]

On Sat, 19 Oct 2002, Mr. James W. Laferriere wrote:

> 
> 	Hello Davidsen ,  I hope the Sym-2 driver is what you are using ?
> 	From the dmesg output I suspect that is not the case .  If there
> 	is only the one Symbios/LSI driver I hope it is the Sym-2
> 	version .  Hth ,  JimL

No, the sym-anything seems to be for the newer chopsets, and not the old
ncr825. I believe I tried 2.5.38 or so with that driver and it couldn't
find a device it liked. I'll try building that module again, but it didn't
work and I thought it might be causing a problem trying.

Also note that the driver inserts and fails twice (see dmesg) which is not
intuitive to me.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

Re: NCR adaptor doesn't see devices (was: 2.5.43 aic7xxx segfault)

[Mr. James W. Laferriere]

	Hello Bill ,

On Sun, 20 Oct 2002, Bill Davidsen wrote:
> No, the sym-anything seems to be for the newer chopsets, and not the old
> ncr825. I believe I tried 2.5.38 or so with that driver and it couldn't
> find a device it liked. I'll try building that module again, but it didn't
> work and I thought it might be causing a problem trying.
	Iirc ,  Gerard said that the Sym-2 is for all chipsets again .
	see: linux/drivers/scsi/sym53c8xx_2/Documentation.txt
	The ncr53c8xx was the original driver that he produced .  Then
	came the sym53c8xx version which was NOT for the older chips
	supported by the ncr53c8xx.c .

> Also note that the driver inserts and fails twice (see dmesg) which is not
> intuitive to me.
	Yes , I noted them below using a grep of your document .  It
	appears that the SYM53c8xx driver gets loaded   THEN the
	ncr53c8xx attempts to load & of course conflicts with the
	SYM53c8xx .  These two drivers can not co-exist ,  Without very
	special care as to how they get loaded or some such .
	I still highly recommend the sym2 driver rather than either of
	the two being loaded .  But if it won't recognise the drives ...
		Hth ,  JimL

--
       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

dmesg-2.5.43-mm2p1:227:sym53c8xx: at PCI bus 0, device 9, function 0
dmesg-2.5.43-mm2p1:228:sym53c8xx: not initializing, device not supported
...
dmesg-2.5.43-mm2p1:279:ncr53c8xx: at PCI bus 0, device 9, function 0
dmesg-2.5.43-mm2p1:280:ncr53c8xx: 53c825 detected
dmesg-2.5.43-mm2p1:281:ncr53c825-0: rev 0x2 on pci bus 0 device 9 function 0 irq 9
dmesg-2.5.43-mm2p1:282:ncr53c825-0: ID 7, Fast-10, Parity Checking
dmesg-2.5.43-mm2p1:283:scsi1 : ncr53c8xx-3.4.3b-20010512
dmesg-2.5.43-mm2p1:284:ncr53c825-0-<2,*>: target did not report SYNC.
...
dmesg-2.5.43-mm2p1:293:ncr53c825-0: releasing host resources
dmesg-2.5.43-mm2p1:294:ncr53c825-0: resetting chip
dmesg-2.5.43-mm2p1:295:ncr53c825-0: host resources successfully released
...
dmesg-2.5.43-mm2p1:303:ncr53c8xx: at PCI bus 0, device 9, function 0
dmesg-2.5.43-mm2p1:304:ncr53c8xx: 53c825 detected
dmesg-2.5.43-mm2p1:305:ncr53c825-0: rev 0x2 on pci bus 0 device 9 function 0 irq 9
dmesg-2.5.43-mm2p1:306:ncr53c825-0: ID 7, Fast-10, Parity Checking
dmesg-2.5.43-mm2p1:307:scsi1 : ncr53c8xx-3.4.3b-20010512
dmesg-2.5.43-mm2p1:308:ncr53c825-0-<2,*>: target did not report SYNC.
...
dmesg-2.5.43-mm2p1:311:ncr53c825-0: releasing host resources
dmesg-2.5.43-mm2p1:312:ncr53c825-0: resetting chip
dmesg-2.5.43-mm2p1:313:ncr53c825-0: host resources successfully released

Re: NCR adaptor doesn't see devices (was: 2.5.43 aic7xxx segfault)

[Bill Davidsen]

On Sun, 20 Oct 2002, Mr. James W. Laferriere wrote:

> On Sun, 20 Oct 2002, Bill Davidsen wrote:
> > No, the sym-anything seems to be for the newer chopsets, and not the old
> > ncr825. I believe I tried 2.5.38 or so with that driver and it couldn't
> > find a device it liked. I'll try building that module again, but it didn't
> > work and I thought it might be causing a problem trying.
> 	Iirc ,  Gerard said that the Sym-2 is for all chipsets again .
> 	see: linux/drivers/scsi/sym53c8xx_2/Documentation.txt
> 	The ncr53c8xx was the original driver that he produced .  Then
> 	came the sym53c8xx version which was NOT for the older chips
> 	supported by the ncr53c8xx.c .

First, you are right, using the new sym driver the card works. But:
 1. it doesn't build (2.5.43) as a module, up through -mm3
 2. the ncr module works in 2.4, and should work or be remnoved.
    Typically we keep old modules, like the something7,8xx (yes, comma
    in the module name).
 3. Building in makes it load before the ide-scsi module, and changes all
    the device name and assignments. I have enough problems going between
    2.4 and 2.5, I'm afraid of ising devfs on top of that. If it works.
 
> > Also note that the driver inserts and fails twice (see dmesg) which is not
> > intuitive to me.
> 	Yes , I noted them below using a grep of your document .  It
> 	appears that the SYM53c8xx driver gets loaded   THEN the
> 	ncr53c8xx attempts to load & of course conflicts with the
> 	SYM53c8xx .  These two drivers can not co-exist ,  Without very
> 	special care as to how they get loaded or some such .
> 	I still highly recommend the sym2 driver rather than either of
> 	the two being loaded .  But if it won't recognise the drives ...
> 		Hth ,  JimL

Most good catch, I saw the ncr52c8xx and missed the module name, don't
know how that got turned on.

So I can run as long as I'm very ccareful what scripts do, and the ncr
module could be fix (probably trivial) or the sym-2 could be made to work
as a module. I can provide the config and anything else if that proves
hard to replicate, I'm in the habbit of building almost everything as a
module, so I hit rather more of these problems than I would like.

Again thanks for the catch, I'm working, the system uses all devices, and
the swap of /dev/sc0<=>/dev/scd1 assignment is acceptable for a
development machine. I'll probably change the scripts to use cdrom1..N and
just make the symlinks in rc.local.

I couldn't get netfilter to build as modules the last time I tried, I have
to look at that Wednesday, when I'm back in the office.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.