Re: Filesystem Corruption revisited

El mié, 29-12-2004 a las 02:31 +1100, Joseph Jezak escribió:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Flaffer wrote:
> | I believe there is a kernel issue (at least with my kernel). Less then
> | 24 hours after fixing the /dev/hda8 filesystem which was fubar, I now
> | have BOTH hda8 and hda9 go read-only (the first symptom I see).
> |
> | Here is some information from the logs. I am seeing a ton of the
> | following error:
> |
> | Dec 28 06:03:57 anime kernel: evbug.c: Event. Dev: adb2:2.02/input,
> | Type: 1, Code: 57, Value: 1
> | Dec 28 06:03:57 anime kernel: evbug.c: Event. Dev: adb2:2.02/input,
> | Type: 0, Code: 0, Value: 0
> |
> | This looks like something with the adb driver (keyboard/mouse are
> | using it). Not sure why it would affect filesystems.
> |
> 
> Yes, this is the input event debugging system, turn it off in your
> kernel config, it's useless and just clutters things up.
only wanted to point that it can be also a security problem

> und.
> |
> | Unless I can get some direction here, I am thinking of trying to
> | install YellowDog4 and see if it is more stable. Of course, if it does
> | not fail, then I know it was Gentoo. If it does, then it must be
> | hardware related.
> |
> | Any help would be be appreciated,
> |
> | Ben Ricker
> |
> 
> It may be worth trying again without the event debugging to see if any
> other errors catch your eye.  Is your kernel compiled with PREEMPT on?
> Which kernel are you using?  Can you post your config somewhere where we
> can see it?  I'd lean on the side of hardware problem, but I'm not positive.
> 

Why don't you try with the latest kernel? It seems that 2.6.10 comes
with tons of fixes...

See you, Fernando


--
[email protected] mailing list