From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755887AbXGUQzz (ORCPT ); Sat, 21 Jul 2007 12:55:55 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751393AbXGUQzr (ORCPT ); Sat, 21 Jul 2007 12:55:47 -0400 Received: from wa-out-1112.google.com ([209.85.146.177]:50973 "EHLO wa-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750745AbXGUQzq (ORCPT ); Sat, 21 Jul 2007 12:55:46 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=r03vFw+bGUlBrPVWS4evmrIYcmpHeDzjCkWVAjZRM3UEl9FKcyiS1Luk9zsksqYZORq+4KzYWPNZV1vzqHA3UxXuWmZSn/VJqSriZwwmXPNWTBzmNh7HolHRKAoKhi2C+hPclZiEId+o7rpxCVqMouBrijiRqbLNyLDC+acM+Zo= Message-ID: <6bffcb0e0707210955r4822e44cnca400bd166ee429d@mail.gmail.com> Date: Sat, 21 Jul 2007 18:55:41 +0200 From: "Michal Piotrowski" To: "Andi Kleen" Subject: Re: [broken-out-2007-07-20-00-22] kernel bug at kernel/params:570 Cc: "Satyam Sharma" , "Greg KH" , "Andrew Morton" , rdunlap@xenotime.net, LKML In-Reply-To: <6bffcb0e0707210952x97db031o7b93deff81bcdae4@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6bffcb0e0707200932p2b905e21g7970172ca7eb4da7@mail.gmail.com> <6bffcb0e0707210900h505f04aaq98e0f4b17139d94b@mail.gmail.com> <200707211841.39339.ak@suse.de> <6bffcb0e0707210952x97db031o7b93deff81bcdae4@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 21/07/07, Michal Piotrowski wrote: > On 21/07/07, Andi Kleen wrote: > > On Saturday 21 July 2007 18:00:52 Michal Piotrowski wrote: > > > Hi Andi, > > > > > > On 21/07/07, Satyam Sharma wrote: > > > > On 7/21/07, Michal Piotrowski 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 ftp :) Regards, Michal -- LOG http://www.stardust.webpages.pl/log/