On Wed, 26 Oct 2005 04:00:19 GMT, ray <rollingviolation@domain.invalid.com> wrote:

>Grant wrote:
>> On Tue, 25 Oct 2005 16:05:09 GMT, news <rollingviolation@domain.invalid.com> wrote:
>>
>>
>>>syslog has nothing, and messages has:
>>>
>>>Oct 25 01:48:27 athlin1 -- MARK --
>>>^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>>>^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^ @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>>>^@^@^@^@Oct 25 07:37:00 athlin1 syslogd 1.4.1: restart.
>>
....
>2.4.31.
>Stock kernel with ACPI enabled.
>Athlon 64 3000+ (socket 754), MSI Neo something MB (KT800 chipset.)
>512MB DDR400
>Nothing overclocked.
>external USB 2.0 Case with Maxtor 250GB IDE drive (8MB/7200RPM) inside.
>unable to replicate -> I filled it right up today and nothing...
>so I dunno what else to say... just wondering what other hints may be
>left behind.

Stuff happens ) Maybe you bumped the cable?

See http://linux.exosec.net/kernel/2.4-h...-hf6/CHANGELOG
try 2.4.31-hf6? There are some x86-64 fixes mentioned in there might
ring a bell.

Turn on SCSI verbose errors and USB debug might shed some light, but
the odd lockup is difficult. One lockup more so I've had trouble
with (no-name) DDR-400 memory, maybe a compile test loop, perhaps:

cd linux-2.4.31; cp vmlinux ..
while true; do make clean; make bzImage -j4; cmp vmlinux ../vmlinux >> ../result; done

Checked for BIOS update?

Grant.