Re: loop-AES trouble

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 25, 2002 at 09:28:10PM +0300, Jari Ruusu wrote:
> Richard Zidlicky wrote:
> > I am getting repeatable deadlocks using 2.4.18, loop-AES-v1.6e
> > and ciphers-v1.0e.tar.bz2.
> [snip]
> > Next I have copied 240 MB random files to the fresh filesystem
> > and bdflush as well as kupdated entered 'D' state, a few other
> > processes that were active at that time entered the 'T' state
> > All files have been apparently correctly copied over, can be
> > accessed and everything else works quite well except that every
> > (f)sync hangs - a few hours later the system is still usable..
> > 
> > I am running automount and knfsd which did nothing at that time.
> > 
> > Any idea?
> 
> Did you change kernel .config between compiling your running kernel and
> compiling loop.o + loop_serpent.o modules? Compiling a module and rest of
> kernel with different .config is almost guaranteed to cause trouble.

Both are freshly recompiled.

Tried without kernel automounter and without knfsd, same result.

Realised one more thing, I run with IDE multcount=16 and 'hdparm -u1', 
did you ever test with similar options?


Richard

### /etc/sysconfig/harddisks ##
# These options are used to tune the hard drives -
# read the hdparm man page for more information

# Set this to 1 to enable DMA. This might cause some 
# data corruption on certain chipset / hard drive
# combinations. This is used with the "-d" option

# USE_DMA=1

# Multiple sector I/O. a feature of most modern IDE hard drives,
# permitting the transfer of multiple sectors per I/O interrupt,
# rather than the usual one sector per interrupt.  When this feature
# is enabled, it typically reduces operating system overhead for disk
# I/O by 30-50%.  On many systems, it also provides increased data
# throughput of anywhere from 5% to 50%.  Some drives, however (most
# notably the WD Caviar series), seem to run slower with multiple mode
# enabled. Under rare circumstances, such failures can result in
# massive filesystem corruption. USE WITH CAUTION AND BACKUP.
# This is the sector count for multiple sector I/O - the "-m" option

MULTIPLE_IO=16

# (E)IDE 32-bit I/O support (to interface card)
#
# EIDE_32BIT=3

# Enable drive read-lookahead
#
# LOOKAHEAD=1

# Add extra parameters here if wanted
# On reasonably new hardware, you may want to try -X66, -X67 or -X68
# Other flags you might want to experiment with are -u1, -a and -m
# See the hdparm manpage (man hdparm) for details and more options.
#
EXTRA_PARAMS=-u1

-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux