public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Sipek <jeffpc@optonline.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Clemens Schwaighofer <cs@tequila.co.jp>,
	"Matt H." <lkml@lpbproductions.com>,
	Norberto Bensa <norberto+linux-kernel@bensa.ath.cx>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.7-bk way too fast
Date: Mon, 21 Jun 2004 05:52:51 -0400	[thread overview]
Message-ID: <200406210552.57420.jeffpc@optonline.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0406210031160.11274@ppc970.osdl.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 21 June 2004 03:37, Linus Torvalds wrote:
> Ok, either we have two bugs with _exactly_ the same behaviour, or
> something is just getting screwed up. That single change has definitely
> been fingered as being the problem by a few people. And removing the one
> line (if you have an x86-64 system you have to remove it in the x86-64
> version of the file too) should undo the patch that seems to have caused
> the problem in the first place.
>
> Anyway, my one-liner patch won't have applied at all if you had applied
> Andrew's patch, so the first thing to do is to double-check that it
> actually got applied. I'm still hoping. But assuming it did, can you
> enable APIC debugging in include/asm-i386/apic.h, and send the resulting
> honking huge dmesg to me and the other suspects in this on-going saga?
>
> Preferably both from a plain 2.6.7 kernel (well, "plain" except for the
> DEBUG enable) and from the broken kernel..

If you want the dmesgs, you can get them from 
http://shells.gnugeneration.com/~jeffpc/kernel/logs/.

The 'bad' one is before your patch, and the 'good' one is after your patch.

Jeff.

- -- 
We have joy, we have fun, we have Linux on a Sun...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA1q/3wFP0+seVj/4RAmX8AJ9w/O8ZPFL0LuH/fqoA8nYBbpMBsQCfWe1N
U8WsaVMhFsT2og5BxmS6fjk=
=E2nb
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-06-21  9:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  2:54 2.6.7-bk way too fast Jeff Garzik
2004-06-21  3:29 ` Ricky Beam
2004-06-21  7:20   ` Felipe Alfaro Solana
2004-06-21  8:23   ` Vojtech Pavlik
2004-07-02  7:53     ` David Woodhouse
2004-07-02 12:56       ` Vojtech Pavlik
2004-06-21  3:36 ` Jeff Garzik
2004-06-21  3:49   ` Matt H.
2004-06-21 11:53     ` Marcel Holtmann
2004-06-21  3:52   ` Zwane Mwaikambo
2004-06-21  3:55     ` Zwane Mwaikambo
2004-06-21  4:02   ` Andrew Morton
2004-06-21  5:00     ` Norberto Bensa
2004-06-21  5:39       ` Norberto Bensa
2004-06-21  6:16         ` Linus Torvalds
2004-06-21  7:05           ` Clemens Schwaighofer
2004-06-21  7:18             ` Matt H.
2004-06-21  7:16               ` Andrew Morton
2004-06-21  8:15                 ` Matt H.
2004-06-21  8:20                   ` Clemens Schwaighofer
2004-06-21  9:25                     ` Clemens Schwaighofer
2004-06-21 10:24                     ` Felipe Alfaro Solana
2004-06-21  7:37             ` Linus Torvalds
2004-06-21  9:52               ` Jeff Sipek [this message]
2004-06-21 16:41                 ` Jeff Sipek
2004-06-21  7:19           ` Jeff Sipek
2004-06-21  5:11     ` Jeff Garzik
2004-06-21  5:08 ` Aubin LaBrosse
2004-06-21  8:22 ` Vojtech Pavlik
2004-06-21 10:26   ` Felipe Alfaro Solana
2004-06-21 11:02     ` Vojtech Pavlik
2004-06-21  8:48 ` Andrew Morton
2004-06-21  9:17   ` Matt H.
2004-06-21  9:56   ` Jeff Sipek
2004-06-21 10:47   ` Felipe Alfaro Solana
2004-06-21 16:55     ` Norberto Bensa
  -- strict thread matches above, loose matches on Subject: below --
2004-06-21 13:20 Sau Dan Lee
2004-06-21 15:17 ` Vojtech Pavlik
2004-06-21 15:25   ` Sau Dan Lee

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=200406210552.57420.jeffpc@optonline.net \
    --to=jeffpc@optonline.net \
    --cc=akpm@osdl.org \
    --cc=cs@tequila.co.jp \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@lpbproductions.com \
    --cc=norberto+linux-kernel@bensa.ath.cx \
    --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