mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ray Lee <ray-lk@madrabbit.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: excessive IDE log spamming
Date: Fri, 08 Jul 2005 14:45:13 -0700	[thread overview]
Message-ID: <1120859114.10563.35.camel@orca.madrabbit.org> (raw)

ray:/var/log$ grep ' 08:' messages
Jul  8 08:00:00 orca kernel: [7033724.854000] hdc: ATAPI reset complete
Jul  8 08:00:00 orca kernel: [7033724.854000] hdc: status error: status=0x20 { DeviceFault }
Jul  8 08:00:00 orca kernel: [7033724.854000] ide: failed opcode was: unknown
Jul  8 08:00:00 orca kernel: [7033724.904000] hdc: ATAPI reset complete
Jul  8 08:00:00 orca kernel: [7033724.904000] hdc: status error: status=0x20 { DeviceFault }
Jul  8 08:00:00 orca kernel: [7033724.904000] ide: failed opcode was: unknown
Jul  8 08:00:00 orca kernel: [7033724.904000] hdc: status error: status=0x20 { DeviceFault }
Jul  8 08:00:00 orca kernel: [7033724.904000] ide: failed opcode was: unknown
Jul  8 08:00:00 orca kernel: [7033724.954000] hdc: ATAPI reset complete
Jul  8 08:00:00 orca kernel: [7033724.954000] hdc: status error: status=0x20 { DeviceFault }
Jul  8 08:00:00 orca kernel: [7033724.954000] ide: failed opcode was: unknown
Jul  8 08:00:00 orca kernel: [7033725.004000] hdc: ATAPI reset complete
Jul  8 08:00:00 orca kernel: [7033725.004000] hdc: status error: status=0x20 { DeviceFault }
Jul  8 08:00:00 orca kernel: [7033725.004000] ide: failed opcode was: unknown
Jul  8 08:00:02 orca kernel: [7033727.006000] hdc: status error: status=0x20 { DeviceFault }

/var/log/{messages,syslog,kern.log} are each growing at about 4
megabytes an hour. That's nearly a third of a gig per day. I may be a
bit dense, but honest, I got the hint the first meg.

/dev/hdc points to my Plextor CD/RW drive. I'm not sure when this
started; it took some time before I noticed my hard drive filling up
(they're pretty big these days). I'll be rebooting here soon, which I
imagine will fix the problem.

Using Ubuntu's 2.6.12 kernel, so there's the outside chance that odd
vendor patches are doing unhappy things.

Ray


                 reply	other threads:[~2005-07-08 21:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1120859114.10563.35.camel@orca.madrabbit.org \
    --to=ray-lk@madrabbit.org \
    --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

all inboxes | Powered by JetHome®