LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Jeff Garzik <jeff@garzik.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: current git crashes on bootup with pci_iounmap()
Date: Sat, 24 Feb 2007 20:40:15 +0100	[thread overview]
Message-ID: <1172346015.3766.1.camel@min.off.vrfy.org> (raw)
In-Reply-To: <45DC2E52.4030506@gmail.com>

On Wed, 2007-02-21 at 20:34 +0900, Tejun Heo wrote:
> Kay Sievers wrote:
> > On 2/13/07, Kay Sievers <kay.sievers@vrfy.org> wrote:
> >> On Tue, 2007-02-13 at 17:04 +0100, Marcel Holtmann wrote:
> >> > > kernel BUG at lib/iomap.c:254!
> >> > > invalid opcode: 0000 [#1]
> >> > > ...
> >> > >
> >> > > The screen picture is here:
> >> > >   http://vrfy.org/pci_iounmap.jpg
> >> > >
> >> > > It's a Thinkpad T43p.
> >> > >
> >> > > 2.6.20 was working fine.
> >> > >
> >> > > Commenting out:
> >> > >   IO_COND(addr, /* nothing */, iounmap(addr));
> >> > > in:
> >> > >   lib/iomap.c:254
> >> > > makes at least booting up possible.
> >> >
> >> > I saw a similar one on my X41. Disabling the AHCI driver made the
> >> > machine booting again.
> >>
> >> Hey Marcel,
> >> yeah, that works fine here too.
> > 
> > Tejun, Jeff, any ideas what's going wrong with the iomap change and
> > the AHCI driver?
> 
> The following commit should have fixed the problem, at least the oops.
> Care to give the current git head a shot?

Yes, it boots fine now with the AHCI driver compiled in.

Thanks,
Kay


      reply	other threads:[~2007-02-24 19:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 15:31 Kay Sievers
2007-02-13 16:04 ` Marcel Holtmann
2007-02-13 16:52   ` Kay Sievers
2007-02-14 20:57     ` Kay Sievers
2007-02-21 11:34       ` Tejun Heo
2007-02-24 19:40         ` Kay Sievers [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=1172346015.3766.1.camel@min.off.vrfy.org \
    --to=kay.sievers@vrfy.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --subject='Re: current git crashes on bootup with pci_iounmap()' \
    /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

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).