All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Alexander Sabourenkov <screwdriver@lxnt.info>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Promise SATA300 TX4: errors, oops in ext3 code
Date: Tue, 02 Oct 2007 11:08:46 +0200	[thread overview]
Message-ID: <47020A9E.6090602@anagramm.de> (raw)
In-Reply-To: <4701CAA9.6070902@lxnt.info>

Alexander Sabourenkov schrieb:
 >> Have you checked your memory already (memtest86)?
 > [...]
 >> Again... sounds like bad memory to me.
 > Nightly memtest86  run : 11 hours, 23 passes, 0 errors.

Okay, I have no idea about any bugs there.
You have several options: Find a 100% working vanilla kernel for your
problem (minimal configuration, skip i.e. the sound stuff, ...).
And then git bisect with a known bad kernel.

Same thing in hardware: move components (Controllers + HDD) to/from a working
machine and verify...

Regards,

Clemens Koller
__________________________________
R&D Imaging Devices
Anagramm GmbH
Rupert-Mayer-Straße 45/1
Linhof Werksgelände
D-81379 München
Tel.089-741518-50
Fax 089-741518-19
http://www.anagramm-technology.com

  reply	other threads:[~2007-10-02  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-01  7:04 Promise SATA300 TX4: errors, oops in ext3 code Alexander Sabourenkov
2007-10-01  9:09 ` Clemens Koller
2007-10-01 10:26   ` Alexander Sabourenkov
2007-10-02  4:35   ` Alexander Sabourenkov
2007-10-02  9:08     ` Clemens Koller [this message]
2007-10-02  9:49       ` Alexander Sabourenkov
2007-10-02  9:25 ` Clemens Koller

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=47020A9E.6090602@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=screwdriver@lxnt.info \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.