public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "ismail dönmez" <ismail.donmez@gmail.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NForce4 ide problems?
Date: Thu, 21 Apr 2005 21:14:40 +0300	[thread overview]
Message-ID: <2a4f155d05042111141e340cc1@mail.gmail.com> (raw)
In-Reply-To: <2a4f155d05042022575553c2aa@mail.gmail.com>

Oh well, this was due to bad cabling after all. A 80-conductor cable
fixed the issue.Thanks for heads up. Appreciated.

Regards,
ismail



On 4/21/05, ismail dönmez <ismail.donmez@gmail.com> wrote:
> Hi,
> 
> On 4/20/05, Jesper Juhl <juhl-lkml@dif.dk> wrote:
> > You might want to post that Oops message if you want someone to try and 
> > fix it.
> > 
> 
> Ok see it below.
> 
> > Also, from your dmesg output I see that you are loading the NVIDIA module
> >  NVRM: loading NVIDIA Linux x86_64 NVIDIA Kernel Module  1.0-7174  Tue
> Mar
> > 22 06:45:40 PST 2005
> > You may want to try /not/ loading that module and then reproduce the 
> > kernel panic and then post that Oops or panic message instead.
> > 
> Ok this message was taken without loading nvidia module.
> 
> I get this just after hdparm command on /dev/hda :
> 
> <snip>
> CPU 0: Machine Check Exception: 4 Bank 4: b200000000070f0f
> TSC 1cb2201501c
> Kernel panic - not syncing : Machine check
> 
> </snip>
> 
> Any help is appreciated.
> 
> Regards,
> ismail
> 
> 
> -- 
> Time is what you make of it
> 

-- 
Time is what you make of it

      reply	other threads:[~2005-04-21 18:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 15:12 NForce4 ide problems? ismail dönmez
2005-04-20 18:36 ` ismail dönmez
2005-04-20 19:45 ` Jesper Juhl
2005-04-21  5:57   ` ismail dönmez
2005-04-21 18:14     ` ismail dönmez [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=2a4f155d05042111141e340cc1@mail.gmail.com \
    --to=ismail.donmez@gmail.com \
    --cc=juhl-lkml@dif.dk \
    --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