public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linus Torvalds <torvalds@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.15-rc3
Date: 29 Nov 2005 23:11:49 -0700	[thread overview]
Message-ID: <p73iruahdga.fsf@verdi.suse.de> (raw)
In-Reply-To: <200511292247.09243.rjw@sisk.pl>

"Rafael J. Wysocki" <rjw@sisk.pl> writes:

> On Tuesday, 29 of November 2005 05:11, Linus Torvalds wrote:
> > 
> > I just pushed 2.6.15-rc3 out there, and here are both the shortlog and 
> > diffstats appended.
> 
> Hangs solid on boot on dual-core Athlon64.  No details yet, but I'm working
> on them.  I wonder if anyone else is seeing this.

I also see a hang in EHCI on my single A64 VIA box, but curiously
it goes away with pci=noacpi (but that might just cover it - i 
had a buggy USB storage device in the front usb ports and 
I think with noacpi it just doesn't route them correctly) 
Didn't investigate closer so far.

-Andi

      parent reply	other threads:[~2005-11-30  1:43 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-29  4:11 Linux 2.6.15-rc3 Linus Torvalds
2005-11-29  7:20 ` Michael Krufky
2005-11-29  7:43   ` Nick Piggin
2005-11-29  8:25     ` Michael Krufky
2005-11-29 15:47     ` Linus Torvalds
2005-11-29 16:10   ` Linus Torvalds
2005-11-29 16:25     ` Michael Krufky
2005-11-29 16:38       ` Linus Torvalds
2005-11-29 16:49         ` Stephen Frost
2005-11-29 17:04           ` Michael Krufky
2005-11-30  0:18           ` David S. Miller
2005-11-29 17:25         ` Chris Shoemaker
2005-11-29 17:44           ` Stephen Frost
2005-11-29 18:37           ` Linux 2.6.15-rc3 - gcc-4.0.2 compile error Byron Stanoszek
2005-11-29 18:42             ` Arjan van de Ven
2005-11-30  5:53           ` Linux 2.6.15-rc3 Michael Krufky
2005-11-29  9:29 ` Linux 2.6.15-rc3 - VIDEO_BT848_DVB config Eyal Lebedinsky
2005-11-29 13:07   ` Michael Krufky
2005-11-29 21:36 ` Linux 2.6.15-rc3 Helge Hafting
2005-11-29 21:47   ` Linus Torvalds
2005-11-30  8:59     ` Helge Hafting
2005-12-01  8:16       ` Jeff Garzik
2005-12-01  9:32         ` Helge Hafting
2005-12-01  9:37           ` Jeff Garzik
2005-12-04  0:43         ` Linux 2.6.15-rc3 problem found - scsi order changed Helge Hafting
2005-12-04  1:14           ` Linus Torvalds
2005-12-04  9:34             ` Zwane Mwaikambo
2005-12-04 15:28               ` Adrian Bunk
2005-12-04 23:50               ` Helge Hafting
2005-11-29 21:47 ` Linux 2.6.15-rc3 Rafael J. Wysocki
2005-11-29 22:42   ` Rafael J. Wysocki
2005-11-29 22:53     ` Stephen Hemminger
2005-11-29 23:37       ` Greg KH
2005-11-30  0:17         ` Stephen Hemminger
2005-11-30  0:25           ` Andrew Morton
2005-11-30  0:42             ` Stephen Hemminger
2005-11-30  1:57               ` Linus Torvalds
2005-11-30  2:09                 ` Paul Mackerras
2005-11-30  2:46                 ` Stephen Hemminger
2005-11-30  3:16                   ` Linus Torvalds
2005-11-30  4:14                     ` Greg KH
2005-11-30  1:09         ` Stephen Hemminger
2005-11-30  6:11   ` Andi Kleen [this message]

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=p73iruahdga.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@osdl.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