mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: david@lang.hm
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: system locks up when CD burn fails
Date: Thu, 13 May 2010 00:22:49 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.01.1005130021140.8603@asgard.lang.hm> (raw)
In-Reply-To: <20100513070531.GA8491@liondog.tnic>

On Thu, 13 May 2010, Borislav Petkov wrote:

> From: david@lang.hm
> Date: Wed, May 12, 2010 at 03:35:06PM -0700
>
>> I have a couple hundred boxes running kernels from 2.6.12 through
>> 2.6.33.3 that each burn a backup to a IDE CD-ROM once a week. Every
>> couple of months one of the boxes (_not_ the same one each time)
>> runs into some sort of error when burning the CD and the entire box
>> locks up (unable to toggle numlock even). I have not been able to
>> find any correlation between failures and anything on the system.
>>
>> when the system locks up it doesn't log anything, and the screen
>> just freezes in the middle of the cdrecord status (X of Y MB
>> written) with no error message.
>>
>> I'm actually not worried that much about the burn failing, The
>> problem is that the burn failing will take out the entire system. Is
>> there anything that I should be doing to make the systems more
>> robust in the face of such failures?
>
> Are you using the ide drivers or libata? If it is the first, try
> switching to libata to see whether this fixes your freezes.

most of the boxes are using the ide drivers. Unfortunantly the problem is 
very intermittent (every few thousand disks burned I get a problem)

I'm upgrading them all to 2.6.33.3 with the libata drivers within the next 
few days, so we'll see what happens over the next couple of months.

David Lang

      reply	other threads:[~2010-05-13  7:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 22:35 david
2010-05-13  7:05 ` Borislav Petkov
2010-05-13  7:22   ` david [this message]

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=alpine.DEB.2.01.1005130021140.8603@asgard.lang.hm \
    --to=david@lang.hm \
    --cc=bp@alien8.de \
    --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®