Ok, after playing with it a little more I found out that the message I'm
getting about the block sizes isn't related to the lockups. I can lock
the system up by tar'ing up the /proc directory (why are you tar'ing the
/proc directory!!! I know!!! But that's not the point). I had no
problem with RH 7.2's supplied 7.2 kernel (2.4.7-10). However, this is
2.4.17 (with the linux-abi patch).
I have been able to make succesful backups as long as I ignore the /proc
directory but something must be wrong. Doing an "ls -la *" doesn't lock
the machine though. Only when tar'ing it (I suppose because of a read).
It doesn't lock up consistently in the same place when reading from the
proc directory however, but always in the proc. I made about 15 test
runs and they all died in proc and --exclude proc doesn't cause it to
lock somewhere else.
I guess the question is (and I've had it for a while) is how do I get
the system to log more info for me? I'm a little new a debugging the
kernel, but I did compile most of the debugging into a test kernel.
However, the system hard locks with no oops or anything in the logs.
The system must be shutdown by holding the power button in for 4
seconds. I know this must not be a huge problem because no ones
mentioned it, so I'd like to do some more investigating on my part.
Thanks for your help.
> Hello Glover , I get the same messages & do not get system
> lock ups . Might try sending a little bit more info about
> what is going on around any of the lock ups . If you can
> reliably lock up the system by accessing the tape drive .
> Then send some info to the list about the system & the tape
> drive and how it is attached to the system . Hth , JimL
> ps: All disk & tape drives are scsi .
>
>
> On Tue, 19 Feb 2002, Glover George wrote:
>
> > I've been experiencing mysterious lockups since upgrading to kernel
> > 2.4.17. Looking in the /var/log/messages I hadn't seen anything
> > suspicious until now. I guess the machine hasn't had time to write
> > this to disk except every now and then. The message
> >
> > Feb 19 11:29:55 butler kernel: st0: Block limits 1 - 16777215 bytes.
> >
> > I notice this after rebooting after the crash. So I tried manually
> > doing a tar to the tape drive and was able to successfully lock the
> > machine up. Can someone help me understand this and if it
> is simply a
> > limit problem, why would the machine lock up?
> >
-
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/
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:24 EST