Adapter Configuration:
SCSI Adapter: Adaptec AHA-294X Ultra2 SCSI host adapter
Ultra-2 LVD/SE Wide Controller
PCI MMAPed I/O Base: 0xe6000000
Adapter SEEPROM Config: SEEPROM found and used.
Adaptec SCSI BIOS: Enabled
IRQ: 5
SCBs: Active 0, Max Active 1,
Allocated 15, HW 32, Page 255
Interrupts: 4924
BIOS Control Word: 0x1886
Adapter Control Word: 0x1c5d
Extended Translation: Enabled
Disconnect Enable Flags: 0xffff
Ultra Enable Flags: 0x0000
Tag Queue Enable Flags: 0x0000
Ordered Queue Tag Flags: 0x0000
Default Tag Queue Depth: 8
Tagged Queue By Device array for aic7xxx host instance 0:
{255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
Actual queue depth per device for aic7xxx host instance 0:
{1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
Statistics:
(scsi0:0:0:0)
Device using Narrow/Sync transfers at 20.0 MByte/sec, offset 15
Transinfo settings: current(12/15/0/0), goal(10/127/0/0), user(10/127/1/0)
Total transfers 4898 (2706 reads and 2192 writes)
===
This is under Kernel 2.2.13 with devfs.
Now, the problem is that aprox every 4 to 5 seconds, there are 4 writes
(according to /proc/scsi/aic7xxx/0). This is a problem because the
repetitve clicking noise is, well, in my room. Imagine sleeping next to a
metrinome -- I sleep next to these machines (being they're in my room and
all).
My first responce was to use a combination of nannie (a program which
monitors files for any changes) and lsof (listing open files). I tracked
down a daemon that would write to a file every 5 seconds. As I had the
source, I modified it to write the log, then exit. Then I set it as a cron
job. Problem solved...... or not. The regular writing continued. The 4
random writes every 4 to 5 seconds were really getting to me.
Here is the debug log of the SCSI driver:
Nov 5 21:20:25 zephyr kernel: scsi logging level set to 0x12082080
Nov 5 21:20:34 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:34 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:34 zephyr kernel: use_sg is 0
Nov 5 21:20:34 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:34 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:34 zephyr kernel: use_sg is 0
Nov 5 21:20:34 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:34 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:34 zephyr kernel: use_sg is 0
Nov 5 21:20:34 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:34 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:34 zephyr kernel: use_sg is 0
Nov 5 21:20:34 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:34 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:34 zephyr kernel: use_sg is 0
Nov 5 21:20:34 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:34 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:34 zephyr kernel: use_sg is 0
Nov 5 21:20:39 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:39 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:39 zephyr kernel: use_sg is 0
Nov 5 21:20:39 zephyr kernel: sda : rw_intr(0, 0 [0 0])
Nov 5 21:20:39 zephyr kernel: sda : 2 sectors remain.
Nov 5 21:20:39 zephyr kernel: use_sg is 0
Nov 5 21:20:43 zephyr kernel: scsi logging level set to 0x10082080
Now, I'm not a master of the scsi.c internals (far from it), and I don't
really spend much time poking at the kernel (I'm not that good), but a large
amount of zeroes like that makes me wonder what is wrong. Is it a driver
problem? Should I downgrade back to 2.2.9? Any feedback is appreciated.
(CC:ing will get my attention better as I skim the digest ver and could miss
replies there)
-- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me spread!- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/