[parisc-linux] disk I/O error

[parisc-linux] disk I/O error

[Matthias Klose]

ok, seems that the root fs is damaged after some locks and following
resets. For the reinstallation, which kernel should be used on a A500? 
I Tried 2.4.17-64-smp, 2.4.16-64-smp, 2.4.17-64 and
2.4.16-64. However, the machine locks up after three, maybe four days.
 
init-2.05a# ls -l /lib/libext2fs.so.2.4  
ls: /lib/libext2fs.so.2.4: Input/output error 
 
attempt to access beyond end of device 
08:06: rw=0, want=6803996040, limit=1999856 
attempt to access beyond end of device 
08:06: rw=0, want=7745165772, limit=1999856 
attempt to access beyond end of device 
/p/pari/libpari1-dev_2.1.3-1_hppa.deb 
Size: 1540332 

Re: [parisc-linux] disk I/O error

[Grant Grundler]

Matthias Klose wrote:
> ok, seems that the root fs is damaged after some locks and following
> resets. For the reinstallation, which kernel should be used on a A500? 
> I Tried 2.4.17-64-smp, 2.4.16-64-smp, 2.4.17-64 and
> 2.4.16-64. However, the machine locks up after three, maybe four days.

You can try ftp://ftp.parisc-linux.org/kernels/a500/2.4.17-pa23.tgz

this seems to be fairly stable on my a500. And it has ext3
builtin so you can use it on your root filesystem.

I can say that 2.4.18-pa0 is *not* stable with CONFIG_SMP on A500.
It only runs a few hours before locking up.
We suspect issues with do_gettimeofday() (iirc).

grant

Re: [parisc-linux] disk I/O error

[Ralf Hildebrandt]

Am 01.03.2002 um 01:24:58 +0100 schrieb Matthias Klose folgendes:

> ok, seems that the root fs is damaged after some locks and following
> resets. For the reinstallation, which kernel should be used on a A500? 
> I Tried 2.4.17-64-smp, 2.4.16-64-smp, 2.4.17-64 and
> 2.4.16-64. However, the machine locks up after three, maybe four days.
>  
> init-2.05a# ls -l /lib/libext2fs.so.2.4  
> ls: /lib/libext2fs.so.2.4: Input/output error 
>  
> attempt to access beyond end of device 
> 08:06: rw=0, want=6803996040, limit=1999856 
> attempt to access beyond end of device 
> 08:06: rw=0, want=7745165772, limit=1999856 
> attempt to access beyond end of device 
> /p/pari/libpari1-dev_2.1.3-1_hppa.deb 
> Size: 1540332 

This sounds like broken hardware! At least whenever this pops up on
the ext3 list, then it's mostly due to bad hardware, bizarre UDMA
settings or the hardware being used out of spec.

In this case, going to ext3 might not help, since ext3 is ext2, except
for the journal.

-- 
Ralf Hildebrandt (Im Auftrag des Referat V A)   Ralf.Hildebrandt@charite.de
Charite Campus Virchow-Klinikum                 Tel.  +49 (0)30-450 570-155
Referat V A - Kommunikationsnetze -             Fax.  +49 (0)30-450 570-916
Why you can't find your system administrators:
S/He is down to the 7-11 down the street, to buy extra strong coffee and caffeine tabs.