linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Starikovskiy <aystarik@gmail.com>
To: webmaster@dragonslave.de
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
	linux-acpi@vger.kernel.org
Subject: Re: linux-next Regression: Unable to locate IOAPIC
Date: Fri, 13 Jun 2008 02:58:44 +0400	[thread overview]
Message-ID: <4851AA24.7060906@gmail.com> (raw)
In-Reply-To: <200806102229.10512.dex@dragonslave.de>

Hi Daniel,

Could you please provide full dmesg and acpidump outputs?

Thanks,
Alex.

Daniel Exner wrote:
> Andrew Morton wrote:
>   
>> On Fri, 6 Jun 2008 19:30:28 +0200 Daniel Exner <dex@dragonslave.de> wrote:
>>     
>>> Andrew Morton wrote:
>>>       
>>>> (cc linux-acpi)
>>>>
>>>> On Thu, 5 Jun 2008 11:00:12 +0200 Daniel Exner <dex@dragonslave.de> 
>>>>         
> wrote:
>   
>>>>> Hi!
>>>>>
>>>>> (Added myself to CC, because I'm not subscribed)
>>>>>
>>>>> with linux-next snapshot 20080604 my Laptop morphes into sitting duck
>>>>> and I think this is due to this:
>>>>>           
>>>> I assume 2.6.26-rc5 is OK?
>>>>         
>>> Indeed.. just tried it with (nearly) the same config: no unable to locate
>>> IOAPIC
>>>
>>> Will try todays next snapshot above -rc5 now.
>>>       
>> OK, thanks.
>>
>> It would be great if you could test 2.6.26-rc5 plus
>> http://userweb.kernel.org/~akpm/git-acpi.patch.  That'll allow us to
>> confirm that the regression is due to changes in the acpi tree.
>>     
> Sorry for the delay.. real-life you know ;)
>
> I guess you'd expect me to confirm the behavior on rc5 with this patch aplied, 
> but .. well this Kernel works!
>
> So I think the regression is NOT in the acpi tree. Perhaps pci subsystem?
> If I find time I'll try bisecting it..
>
> Greetings
> Daniel Exner
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>   


  parent reply	other threads:[~2008-06-12 22:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-05  9:00 linux-next Regression: Unable to locate IOAPIC Daniel Exner
2008-06-06 10:17 ` Andrew Morton
2008-06-06 17:30   ` Daniel Exner
2008-06-06 18:50     ` Andrew Morton
2008-06-10 20:29       ` Daniel Exner
2008-06-11  5:47         ` Andrew Morton
2008-06-12 22:16           ` Yinghai Lu
2008-06-12 22:58         ` Alexey Starikovskiy [this message]
2008-06-13 11:07           ` Daniel Exner
2008-06-13 15:42             ` Maciej W. Rozycki
2008-06-14  7:07             ` Alexey Starikovskiy
2008-06-14  8:26               ` Yinghai Lu
2008-06-14  8:31                 ` Ingo Molnar
2008-06-15 19:14                 ` Daniel Exner
2008-06-15 19:20                   ` Yinghai Lu
2008-06-18 19:57                     ` Daniel Exner
2008-06-18 20:41                       ` Yinghai Lu
2008-06-18 21:14                         ` Daniel Exner

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=4851AA24.7060906@gmail.com \
    --to=aystarik@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=webmaster@dragonslave.de \
    /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).