SEO

hmmm... my athlon64 hung last night. hard lockup, had to powerfail it.
of course the screensaver was in powersave mode (kde) so I dunno what
the desktop looked like.

syslog has nothing, and messages has:

Oct 25 01:48:27 athlin1 -- MARK --
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@Oct 25 07:37:00 athlin1 syslogd 1.4.1: restart.
Oct 25 07:37:01 athlin1 kernel: klogd 1.4.1, log source = /proc/kmsg
started.

all that was running was a kde desktop with a console session doing a
copy to a usb hard drive (IDE drive in removable case) via a smb mount...

the box is about 6 months old and this is probably the first time it's
ever done that.

I'm more annoyed than anything.. is there anything else I can check (dumps?)

I'm not used to troubleshooting failures on Linux boxes... it could be
hardware, but I dunno, and this box hasn't had a history of that and
other than the USB drive it's unchanged in months.

Ray

news wrote:

> hmmm... my athlon64 hung last night. hard lockup, had to powerfail it.
> of course the screensaver was in powersave mode (kde) so I dunno what
> the desktop looked like.
>
> syslog has nothing, and messages has:
>
> Oct 25 01:48:27 athlin1 -- MARK --
>
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
>
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
> ^@^@^@^@Oct 25 07:37:00 athlin1 syslogd 1.4.1: restart.
> Oct 25 07:37:01 athlin1 kernel: klogd 1.4.1, log source = /proc/kmsg
> started.
>
> all that was running was a kde desktop with a console session doing a
> copy to a usb hard drive (IDE drive in removable case) via a smb mount...
>
> the box is about 6 months old and this is probably the first time it's
> ever done that.
>
> I'm more annoyed than anything.. is there anything else I can check
> (dumps?)
>
> I'm not used to troubleshooting failures on Linux boxes... it could be
> hardware, but I dunno, and this box hasn't had a history of that and
> other than the USB drive it's unchanged in months.
>
> Ray

Because of the infrequency of the event, it once only, I would suspect some
sort of power spike throwing the PSU off stride for a millisecond.

Might be worth updating to KDE 3.4.3 from kde.org if it happens again (been
running the non-official Slack packages since it was released, not had a
problem.)

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.


Which kernel? recent 2.6 series have usbmon, USB debug stuff you
may turn on to get an idea what's happening.

Running USB IDE drives is iffy with some USB<=>IDE bridges (chip in
the USB enclosure).

More info?

Grant.

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.
>
>
>
> Which kernel? recent 2.6 series have usbmon, USB debug stuff you
> may turn on to get an idea what's happening.
>
> Running USB IDE drives is iffy with some USB<=>IDE bridges (chip in
> the USB enclosure).
>
> More info?
>
> Grant.
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.

Steve'o wrote:

> Might be worth updating to KDE 3.4.3 from kde.org if it happens again (been
> running the non-official Slack packages since it was released, not had a
> problem.)
>

eventually... I just rebuilt this dang box like a month ago.

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.

Grant wrote:
> 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.
latest BIOS and stuff... and that's the only hiccup since I built that
box in January, so I'm not bothering for now... but I like the idea of
USB debug stuff if it happens again.

Like I said, unable to replicate, so I'm putting down as phase of the
moon for now...