From mboxrd@z Thu Jan 1 00:00:00 1970 From: Len Brown Subject: Re: Problem 2.6.21 Date: Sat, 28 Apr 2007 01:34:08 -0400 Message-ID: <200704280134.08636.lenb@kernel.org> References: <40771.172.20.1.1.1177699187.squirrel@srv01.nuovanetmore.it> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from hera.kernel.org ([140.211.167.34]:36495 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754688AbXD1Fft (ORCPT ); Sat, 28 Apr 2007 01:35:49 -0400 In-Reply-To: <40771.172.20.1.1.1177699187.squirrel@srv01.nuovanetmore.it> Content-Disposition: inline Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Riccardo Ricci , linux-acpi@vger.kernel.org Cc: linux-kernel@vger.kernel.org On Friday 27 April 2007 14:39, Riccardo Ricci wrote: > > Hi to everyone, > i've compiled kernel 2.6.21 on my debian PIII 650 / 256MB / Dell Latitude > J650GT. With 2.6.20.8 all works very good, with 2.6.21 don't boot... While > booting it stops after ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 9 > 10 11 12 14 15). Does 2.6.20.8 boot with acpi=off, does 2.6.21? Any chance you can get the serial console log of the failure when booted with "debug"? Also, the 2.6.20.8 dmesg is missing the beginning, try dmesg -s64000 -- though it will probably not be very interesting until 2.6.21 output is available to compare to it. thanks, -Len