Re: Consistent complete lock up with 2.6.8.1-mm2 and vuescan, no serial console output

[Jaco Kroon]

Norbert Preining said:
> Hi Andrew, hi Ed, hi list!
> Anyway it would be nice to hear at least a comment from one of you on
> how to proceed with this. Since it is 100% repeatable here, it would be
> nice if it can be fixed. It suprises me that the whole kernel just
> completely freezes, while only disk io and cpu is used, there is no
> usage of usb stuff (besides the usb serial console, but also wihtout

I've got a similar problem on an old pentium 90 machine.  When compiling
glibc it'll run for about a day and then die with absolutely nothing in
the logs.  I've got a serial cable and another machine, so if someone can
point me at documentation on how to set it up I'd be willing to collect
whatever information I can over the weekend.

Jaco

>
> On Don, 12 Aug 2004, preining wrote:
>> The problem persisted with 2.6.8-rc4-mm1, always (repeatable 100%) after
>> around 30 scans the computer freezes completely. Not even sysrq works.
>>
>> But at least what I could check was that it is not a memory problem,
>> there is still enough swap free (close to 1G).
>>
>> So what can I do, any ideas?
>>
>> On Mon, 09 Aug 2004, preining wrote:
>> > I have a bit of a problem here: I am scanning with vuescan (latest
>> > version) on linux-2.6.8-rc3-mm1 a lot of images from raw files, i.e.
>> > only data io from the hard disk, no usb etc interferes, and always
>> after
>> > 20/30 something images the computer freezes completely. Not even Sysrq
>> > works. Only reset button. Of course, the syslog shows up nothing.
>> >
>> > Is there anything you two can think of what could be the reason?
>> >
>> > (and no, I have no chance to use serial console, but I doubt it would
>> be
>> > useful)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/