From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Andi Kleen" <ak@suse.de>
Cc: "Satyam Sharma" <satyam.sharma@gmail.com>,
"Greg KH" <gregkh@suse.de>,
"Andrew Morton" <akpm@linux-foundation.org>,
rdunlap@xenotime.net, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [broken-out-2007-07-20-00-22] kernel bug at kernel/params:570
Date: Sat, 21 Jul 2007 18:52:14 +0200 [thread overview]
Message-ID: <6bffcb0e0707210952x97db031o7b93deff81bcdae4@mail.gmail.com> (raw)
In-Reply-To: <200707211841.39339.ak@suse.de>
On 21/07/07, Andi Kleen <ak@suse.de> wrote:
> On Saturday 21 July 2007 18:00:52 Michal Piotrowski wrote:
> > Hi Andi,
> >
> > On 21/07/07, Satyam Sharma <satyam.sharma@gmail.com> wrote:
> > > On 7/21/07, Michal Piotrowski <michal.k.k.piotrowski@gmail.com> wrote:
> > > > Satyam Sharma pisze:
> > > > > [...]
> > > > > Gargh! My system obviously cannot boot without libata. Guess it's
> > > > > time to go through git log and see how to fix that build breakage
> > > > > myself ...
> > > > >
> > > > > Michal, how did you even manage to build / boot this kernel!
> > > >
> > > > I commented origin.patch and mm.patch in series file, reverted xfs patches,
> > > > fixed libata build, deselected unionfs.
> > > >
> > > > Here is a patch for libata
> > > >
> > > > --- linux-work3-clean/drivers/ata/libata-core.c 2007-07-20 16:53:26.000000000 +0200
> > > > +++ linux-work3/drivers/ata/libata-core.c 2007-07-20 17:26:30.000000000 +0200
> > > > @@ -2036,7 +2036,7 @@ int ata_dev_configure(struct ata_device
> > > > dev->max_sectors = min_t(unsigned int, ATA_MAX_SECTORS_128,
> > > > dev->max_sectors);
> > > >
> > > > - if (ata_device_blacklisted(dev) & ATA_HORKAGE_ALPM) {
> > > > + if (ata_dev_blacklisted(dev) & ATA_HORKAGE_ALPM) {
> > > > dev->horkage |= ATA_HORKAGE_ALPM;
> > > >
> > > > /* reset link pm_policy for this port to no pm */
> > >
> > >
> > > And to think I went through all those hoops just to avoid *this* ... :-(
> > > Anyway, please apply the attached patch and let's verify if we're both
> > > actually bit by the same bug. A screenshot of my case is available at:
> > >
> > > http://www.cse.iitk.ac.in/users/ssatyam/mtrr.show-bug.jpg
> >
> > Yep, the same bug here.
> >
> > My hunt file shows me this
> >
> > GOOD
> > x86_64-mm-i386-string-out-of-line.patch
> > BAD
> >
> > Andi?
>
>
> Does it still happen with the i386-string-out-of-line version from
> firstfloor.org:/pub/ak/x86_64/quilt/patches/ ?
404
>
> I fixed some issues there.
>
> -Andi
>
>
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
next prev parent reply other threads:[~2007-07-21 16:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 16:32 [broken-out-2007-07-20-00-22] kernel bug at kernel/params:570 Michal Piotrowski
2007-07-20 22:50 ` Greg KH
2007-07-20 22:59 ` Andrew Morton
2007-07-20 23:10 ` Greg KH
2007-07-20 23:37 ` Randy Dunlap
2007-07-20 23:43 ` Satyam Sharma
2007-07-21 0:03 ` Satyam Sharma
2007-07-21 0:28 ` Michal Piotrowski
2007-07-21 1:02 ` Greg KH
2007-07-21 1:37 ` Andrew Morton
2007-07-21 1:44 ` Greg KH
2007-07-21 3:21 ` Satyam Sharma
2007-07-21 3:57 ` Satyam Sharma
2007-07-21 6:00 ` Satyam Sharma
2007-07-21 6:39 ` [BUG] " Satyam Sharma
2007-07-21 8:11 ` Michal Piotrowski
2007-07-21 8:00 ` Michal Piotrowski
2007-07-21 8:36 ` Satyam Sharma
2007-07-21 8:41 ` Michal Piotrowski
2007-07-21 16:00 ` Michal Piotrowski
2007-07-21 16:41 ` Andi Kleen
2007-07-21 16:52 ` Michal Piotrowski [this message]
2007-07-21 16:55 ` Michal Piotrowski
2007-07-21 18:11 ` Michal Piotrowski
2007-07-21 18:24 ` Andi Kleen
2007-07-22 17:51 ` Satyam Sharma
2007-07-21 19:13 ` Andrew Morton
2007-07-21 19:31 ` Michal Piotrowski
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=6bffcb0e0707210952x97db031o7b93deff81bcdae4@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=satyam.sharma@gmail.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 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.