All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Vlasenko <vda.linux@googlemail.com>
To: Krzysztof Halasa <khc@pm.waw.pl>,
	Thomas Richter <thor@mail.math.tu-berlin.de>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org, Dmytro_Puhach@cz.ibm.com
Subject: Re: MSI K9N Neo: crash under heavy IDE read
Date: Thu, 14 Sep 2006 11:38:14 +0200	[thread overview]
Message-ID: <200609141138.14885.vda.linux@googlemail.com> (raw)
In-Reply-To: <m3irjr1r57.fsf@defiant.localdomain>

Thanks for everyone answered.

The problem is resolved - one DDR2 module is bad now.

One month ago it survived overnight memtest run,
but now it is definitely bad. memtest detects problems
in a few seconds.

On Wednesday 13 September 2006 21:51, Krzysztof Halasa wrote:
> > Copying movies from SATA drive to PATA drive oopses
> > after few gigabytes transferred. Creating iso image
> > with mkisofs (done entirely on PATA drive, no SATA attached)
> > does the same.
> 
> I don't know about K9N Neo, but I have MSI K9N Ultra-2F (the same
> MCP55) and have no such issues. But:
> - I'm not using drivers/ide anymore (I was using 2.6.17.11 with
>   Alan's libata-PATA patch and now I have ca. 2.6.18-rc6 merged
>   with Jeff's pata-drivers git branch)
> - I have only PATA CD-ROM (and SATA disk, Seagate ST3250823AS).
> - just 1 GB of RAM.
> 
> Copied CD/DVD-ROM discs to HDD few times, no problems.

On Thursday 14 September 2006 10:33, Thomas Richter wrote:
> Not really, but allow me to make another comment: MSI seems to have
> massive problems with the K9N based boards. A good percentage of them
> just "freaks out" from time to time and shuts the system down with no
> aparent reason.

I found info about such mobos and preliminary analysis said
to indicate that one of mobo capacitors had wrong specs.
MSI said to start replacing affected mobos.

My mobo serial number doesn't seem to fall into range of
affected ones, but entire affair doesn't sound encouraging at all.

Not to mention that BIOS is somewhat more buggy that I expected, too.
--
vda

      reply	other threads:[~2006-09-14  9:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12  8:46 MSI K9N Neo: crash under heavy IDE read Denis Vlasenko
2006-09-12 16:18 ` Denis Vlasenko
2006-09-13  7:41   ` MSI K9N Neo: corruption on streaming PATA/SATA i/o - testers needed Denis Vlasenko
2006-09-14  8:33   ` MSI K9N Neo: crash under heavy IDE read Thomas Richter
2006-09-13 19:51 ` Krzysztof Halasa
2006-09-14  9:38   ` Denis Vlasenko [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=200609141138.14885.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=Dmytro_Puhach@cz.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thor@mail.math.tu-berlin.de \
    /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.