public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: szonyi calin <caszonyi@yahoo.com>
Cc: Calin Szonyi <caszonyi@rdslink.ro>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.7-mm[3-4] doesn't boot (alsa or pnp related) (fixed - Acpi)
Date: 17 Jul 2004 02:39:15 -0400	[thread overview]
Message-ID: <1090046355.2792.12.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FFFA6@hdsmsx403.hd.intel.com>


On Mon, 2004-07-12 at 16:35, szonyi calin wrote:
> --- szonyi calin <caszonyi@yahoo.com> a écrit : > ---
> caszonyi@rdslink.ro a écrit : > Hi all
> > > I just tried today 2.6.7-mm3 and 2.6.7-mm4.
> > > They both stop booting at:
> > > Advanced Linux Sound Architecture Driver Version 1.0.5 (Sun
> > > May 30
> > > 10:49:40 2004 UTC)
> > > pnp: Device 01:01.00 activated
> > > pnp: Device 01:01.02 activated
> > > pnp: Device 01:01.03 activated
> > > 
> > 
> > The same happens on 2.6.7-mm5 ;-(
> 
> ... and with 2.6.7-mm6 and 2.6.8-rc1
> Booting with acpi=off fixes the problem. ;-)

Did a previous kernel work w/o acpi=off?
If yes, please send me the dmesg and /proc/interrupts
for both the working and failing kernels.

thanks,
-Len



       reply	other threads:[~2004-07-17  6:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <A6974D8E5F98D511BB910002A50A6647615FFFA6@hdsmsx403.hd.intel.com>
2004-07-17  6:39 ` Len Brown [this message]
2004-07-18 18:36   ` 2.6.7-mm[3-4] doesn't boot (alsa or pnp related) (fixed - Acpi) caszonyi
     [not found] <29AC424F54821A4FB5D7CBE081922E400124DA23@hdsmsx403.hd.intel.com>
2004-08-05 22:11 ` caszonyi
2004-07-01 20:32 2.6.7-mm[3-4] doesn't boot (alsa or pnp related) szonyi calin
2004-07-12 20:35 ` 2.6.7-mm[3-4] doesn't boot (alsa or pnp related) (fixed - Acpi) szonyi calin

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=1090046355.2792.12.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=caszonyi@rdslink.ro \
    --cc=caszonyi@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /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