From: "Stanislav Meduna" <stano@meduna.org>
To: "Dan Siemon" <dan@coverfire.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: USB stability - possibly printer related
Date: Fri, 19 Oct 2001 21:16:46 +0200 [thread overview]
Message-ID: <AHEMIKPKMHEEJBKHLIGHEEFGCAAA.stano@meduna.org> (raw)
In-Reply-To: <1003518067.16964.22.camel@cr156960-a>
Hi,
> I have not had time to risk killing my system again but
> it appears to be either related to postscript printing
> or the lm_sensors modules. Do you by chance use lm_sensors?
No, I don't.
> I am pretty sure I can make it happen again but I don't have
> the time to reinstall my system right now...
I can experiment, provided that only the mounted partitions
can be hosed this way. But if this is some memory corruption,
maybe anything could go wrong...
> > - I got a corruption of the files that were surely _not_
> > opened for writing.
>
> Here too. Many system libs were corrupted. When fsck tried
> to repair the file system it spewed all kinds of errors
> about libs.
Kernel gurus: it seems this is a common symptom. Could someone
give some explanation/speculation, what mechanismus can lead
to this kind of corruption (not necessarily related to USB)?
Regards
--
Stano
next prev parent reply other threads:[~2001-10-19 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-14 15:44 USB stability - possibly printer related Stanislav Meduna
2001-10-14 17:17 ` Kevin Krieser
2001-10-15 7:02 ` Stanislav Meduna
2001-10-15 12:41 ` Kevin Krieser
2001-10-15 21:52 ` Alan Cox
2001-10-16 10:11 ` Stanislav Meduna
2001-10-19 19:01 ` Dan Siemon
2001-10-19 19:16 ` Stanislav Meduna [this message]
2001-10-19 20:15 ` Pete Toscano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AHEMIKPKMHEEJBKHLIGHEEFGCAAA.stano@meduna.org \
--to=stano@meduna.org \
--cc=dan@coverfire.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox