-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Linux Kernel Problem/Bug Report
[1.] One line summary of the problem:
Kernel locks up access to a specific SCSI device with FSB at 100Mhz
[2.] Full description of the problem/report:
When the motherboard FSB is set to 100Mhz any access to the files on
the IBM DSAS-3540 drive causes the system to immediately lock up.
Does not matter if done via comman line before XFree is started or if
accessed in any number of possible ways after XFree is started.
Accessing the files on the Segate drive poses no difficulty. If the
motherboard FSB is set to 95Mhz, 83Mhz, 75Mhz, or 66 Mhz access to
the same drive is fine and normal. In all cases all that has been
changed is the DIP switch setting that sets the FSB speed. Please
note that under Windows NT 4.0 SP6a using the standard Buslogic NT
driver there are no issues with access, lock up or performance in the
exact same configuration (I have removable SCSI trays for this PC.)
using the 100Mhz or any other FSB frequency setting.
[3.] Keywords (i.e., modules, networking, kernel):
Kernel Buslogic SCSI 100Mhz FSB [4.] (Kernel.org)2.2.18, (SuSE)2.2.16
[5.] Output of Oops.. message (if applicable) with symbolic
information resolved (see Documentation/oops-tracing.txt)
No known "Oops" message.
[6.] A small shell script or example program which triggers the
problem (if possible):
Problem is caused by such things as "ls /SwapTemp" via the comman
line or trying to access /SwapTemp via KFM, but again all that seems
to be the trigger is a accessing the /SwapTemp directory or
subdirectory in some manner.
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here):
./ver_linux
- -- Versions installed: (if some fields are empty or looks
- -- unusual then possibly you have very old versions)
Linux uyhaporjthgagkfgiu 2.2.18 #2 SMP Sat Feb 24 17:26:18 EST 2001
i586 unknownKernel modules 2.3.9
Gnu C 2.95.2
Binutils 2.9.5.0.24
Linux C Library x 1 root root 4060896 Sep 5 07:57
/lib/libc.so.6
Dynamic linker ldd (GNU libc) 2.1.3
Procps 2.0.6
Mount 2.10f
Net-tools 1.54
Kbd 0.99
Sh-utils 2.0
Modules Loaded ppp_deflate bsd_comp ppp slhc nls_cp437
I am using SuSE Linux 6.4 with updates as of 31 December 2000
applied. After having the problem with the latest SuSE 6.4 Kernel
2.2.16 and SuSE 7.0 Kernel 2.2.16 (k_deflt SuSE kernels) I downloaded
the 2.2.18 kernel from kernel.org and compiled the kernel for a test
against the "latest" kernel. The kernel.org version of the 2.2.18
Kernel produced the same results as have experienced thus far of this
problem.
[7.2.] Processor information (from /proc/cpuinfo):
In the SuSE system it is empty. This problem came to light after I
have upgraded from an AMD K6 233 process that runs at 66Mhz FSB, to
an AMD K6-2 500 that runs at 100Mhz FSB.
[7.3.] Module information(from /proc/modules):
In the SuSE system it is empty.
[7.4.] SCSI information (from /proc/scsi/scsi)
In the SuSE system it is empty.
I am using a Buslogic BT-930 with firmware 1.41i and have used this
PCI controller for better than 18 months and on this motherbaord for
past 5 months. The /SwapTemp (/dev/sdb1) device is a IBM Model DSAS
3540 P/N 66G9693 MLC E15153 and is the entire drive via the/SwapTemp
directory and is SCSI ID 4. SCSI ID 1 on the same BT-930 is a Segate
ST39216N, and SCSI ID 4 is a Plextor CD-ROM PX-8XCS. Other devices
do get plugged into the SCSI but either on the other SCSI tray I have
or via the external connector, but for the purposes of this bug
report these "other" devices have not been used or connected for the
purposes of isolating this bug. It should be known that the
connection of thes eother devices has not been tested enough to know
if they would be affected by the system motherboard FBS frequency.
[7.5.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
The motherboard being used is a DFI K6BV3+/66 with an Award Modular
BIOS V4.51PG, PnP Extensions 1.0a BIOS related info displayed on
bottom line during system startup:
04/12/2000-VP3-596B-DD-2A5LED4GC-00
[X.] Other notes, patches, fixes, workarounds:
I believe I mentioned what may be listed here already. To summarize,
using a 95Mhz, 83Mhz, 75Mhz, or 66Mhz FSB setting for the motherboard
avoids the lock up problem when assess the one specific device. The
only Kernel parameter being passed is that to set physical memory to
192MB. Windows NT 4.0/SP6a has no problem accessing the same IBM
SCSI ID 4 drive. Again the only change being made between
encountering the problem or not is the changing of the three DIP
switches that determine the FSB speed the motherboard will use.
The system fstab is:
/dev/sda5 swap swap defaults
0 0
/dev/sda6 swap swap defaults
0 0
/dev/sda1 / ext2 defaults
1 1
/dev/sda3 /data ext2 defaults
1 2
/dev/sdb1 /SwapTemp vfat user
0 0
/dev/scd0 /cdrom auto
ro,noauto,user,exec 0 0
/dev/fd0 /floppy auto noauto,user
0 0
none /proc proc defaults
0 0
# End of YaST-generated fstab lines
Regards,
John L. Males
Willowdale, Ontario
Canada
24 February 2001 21:09
mailto:[EMAIL PROTECTED]
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.8 for non-commercial use
<http://www.pgp.com>
iQA/AwUBOphpXeAqzTDdanI2EQKYugCg6LMRUDH6yN1kXMOyJPTJ4edVAMcAoM/Z
c9umRI4J6eBdgx5TgBh96xyv
=wOAq
-----END PGP SIGNATURE-----
"Boooomer ... Boom Boom, how are you Boom Boom" Boomer 1985 - February/2000
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
