linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Mike Mattie <codermattie@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Sergei Shtylyov <sshtylyov@ru.mvista.com>,
	bzolnier@gmail.com, linux-ide@vger.kernel.org
Subject: Re: [BUG] 2.6.21-rc7 hpt366 driver broken
Date: Mon, 16 Apr 2007 16:36:13 +0200	[thread overview]
Message-ID: <20070416143613.GD10338@stusta.de> (raw)
In-Reply-To: <20070416043822.0ea2490e@reforged>

[ Cc's added, full bug report was in http://lkml.org/lkml/2007/4/16/18 ]

On Mon, Apr 16, 2007 at 04:38:22AM -0700, Mike Mattie wrote:
> On Sun, 15 Apr 2007 22:48:46 -0700
> Mike Mattie <codermattie@gmail.com> wrote:
> 
> > Hello,
> > 
> > I am testing the 2.6.21-rc7 kernel release. The IDE hpt366 driver is
> > crashing hanging the boot. I have basically the same config as
> > 2.6.20.7 which works fine (except for netconsole mentioned in a
> > previous mail).
> > 
> > here is the hand-copied info:
> > 
> > * "unable to handle paging request" , null deref
> > * EIP @ init_chipset_hpt366
> > 
> 
> > I am running a git-bisect to see if I can resolve it to a commit.
> 
> This was identified as the first broken commit:
> 
> commit 7b73ee05d0acb926923d43d78b61add776ea4bb1
> Author: Sergei Shtylyov <sshtylyov@ru.mvista.com>
> Date:   Wed Feb 7 18:18:16 2007 +0100
> 
>     hpt366: init code rewrite
> 
> Reverting is conflicted so it will be a bit longer before I pin-point any other build-breaks.

Thanks for your report.

Can you use a digital camera for taking a photograph of the crash?

cu
Adrian

--

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


           reply	other threads:[~2007-04-16 14:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20070416043822.0ea2490e@reforged>]

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=20070416143613.GD10338@stusta.de \
    --to=bunk@stusta.de \
    --cc=bzolnier@gmail.com \
    --cc=codermattie@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sshtylyov@ru.mvista.com \
    /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;
as well as URLs for NNTP newsgroup(s).