public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ford <david+cert@blue-labs.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux v2.5.62
Date: Wed, 19 Feb 2003 05:53:43 -0500	[thread overview]
Message-ID: <3E536237.8010502@blue-labs.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0302171515110.1150-100000@penguin.transmeta.com>

2.5.60+ is rather unstable for me on an Athlon CPU w/ gcc 3.2.2.  If I'm 
careful and do very little in X, it seems to stay up for a few days.  If 
I do any sort of fast graphics or sound, etc, it'll die very quickly.  
'tis an instant death with no OOPS, nothing at all on screen, nothing on 
serial console.

Just an FYI, I'm trying to narrow it down.

David

Linus Torvalds wrote:

>Hmm.. Mostly lots of small updates, although the merge with Andrew
>included the RCU dcache patches from IBM that he has carried along for a
>while (ie fairly fundamnetal, but also very well tested).
>
>ARM, PPC, PPC64, alpha, kbuild.
>
>Oh, and as a sign that 2.6.x really _is_ approaching, people have started 
>sending me spelling fixes. Kernel coders are apparently all atrocious 
>spellers, and for some reason the spelling police always comes out of the 
>woodwork when stable releases get closer.
>  
>


  parent reply	other threads:[~2003-02-19 10:43 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-17 23:18 Linux v2.5.62 Linus Torvalds
2003-02-18  0:03 ` Linux v2.5.62 --- spontaneous reboots Chris Wedgwood
2003-02-18  0:44   ` Jeff Garzik
2003-02-18  0:46     ` Chris Wedgwood
2003-02-18  1:42   ` Linus Torvalds
2003-02-18  1:53     ` Chris Wedgwood
2003-02-18  2:02       ` Linus Torvalds
2003-02-18  2:16         ` Chris Wedgwood
2003-02-18  2:33           ` Linus Torvalds
2003-02-18  3:21         ` Martin J. Bligh
2003-02-19 11:02         ` David Ford
2003-02-18 21:44     ` Chris Wedgwood
2003-02-18 21:59       ` Chris Wedgwood
2003-02-18 22:13         ` Linus Torvalds
2003-02-18 22:34           ` Linus Torvalds
2003-02-18 23:01           ` Chris Wedgwood
2003-02-19 23:35             ` doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots) Linus Torvalds
2003-02-20  2:22               ` Zwane Mwaikambo
2003-02-20  2:26                 ` William Lee Irwin III
2003-02-20  2:55                   ` Zwane Mwaikambo
2003-02-20  3:15                     ` William Lee Irwin III
2003-02-20  4:52                 ` Linus Torvalds
2003-02-20  5:07                   ` William Lee Irwin III
2003-02-20  6:05                   ` Zwane Mwaikambo
2003-02-20 11:46                   ` Ingo Molnar
2003-02-20 12:12                     ` William Lee Irwin III
2003-02-20 12:33                       ` Ingo Molnar
2003-02-20 14:03                         ` Zwane Mwaikambo
2003-02-20 14:00                     ` Zwane Mwaikambo
2003-02-20 15:43                     ` Linus Torvalds
2003-02-20 15:52                       ` Ingo Molnar
2003-02-20 16:11                       ` Martin J. Bligh
2003-02-20 16:54                         ` Linus Torvalds
2003-02-20 17:24                           ` Jeff Garzik
2003-02-20 21:21                           ` Alan Cox
2003-02-20 20:20                             ` Linus Torvalds
2003-02-20 20:23                             ` Martin J. Bligh
2003-02-20 20:42                               ` William Lee Irwin III
2003-02-20 20:51                                 ` Linus Torvalds
2003-02-21  7:39                           ` [PATCH] snd_pcm_oss_change_params is a stack offender Muli Ben-Yehuda
2003-02-21  7:58                             ` Andreas Dilger
2003-02-21  8:20                               ` Muli Ben-Yehuda
2003-02-27 18:50                           ` doublefault debugging (was Re: Linux v2.5.62 --- spontaneous reboots) Randy.Dunlap
2003-02-27 19:39                             ` Muli Ben-Yehuda
2003-02-27 19:47                               ` Randy.Dunlap
2003-03-02  6:12                             ` Keith Owens
2003-02-27 23:32                           ` Randy.Dunlap
2003-02-20 23:09                         ` Chris Wedgwood
2003-02-20 16:44                       ` Ingo Molnar
2003-02-20 20:13                       ` Chris Wedgwood
2003-02-18 12:13   ` Linux v2.5.62 --- spontaneous reboots Pavel Machek
2003-02-19 10:53 ` David Ford [this message]
2003-02-19  6:49   ` Linux v2.5.62 Thomas Molina
2003-02-19 11:04   ` Duncan Sands
2003-02-19 11:07     ` William Lee Irwin III
2003-02-19 11:58       ` Duncan Sands
2003-02-19 12:04         ` William Lee Irwin III
2003-02-19 11:17   ` Hirling Endre
2003-02-19 11:24     ` Duncan Sands
2003-02-19 11:52       ` Hirling Endre
2003-02-19 18:50   ` Zilvinas Valinskas
2003-02-19 21:46     ` Remco Post
2003-02-19 22:23       ` Remco Post
2003-02-20  1:13         ` Tom Rini
2003-02-20 19:42           ` Remco Post
2003-02-20 19:46             ` Tom Rini
2003-02-20 20:05               ` Remco Post
2003-02-20 13:31     ` Dave Jones
2003-02-20 13:57       ` Zilvinas Valinskas
2003-02-20 14:31         ` Dave Jones
2003-02-21  3:58     ` Alexander Hoogerhuis
2003-02-22  5:34       ` Alexander Hoogerhuis
  -- strict thread matches above, loose matches on Subject: below --
2003-02-15  1:11 Linux v2.5.61 Linus Torvalds
2003-02-17 19:35 ` John Cherry
2003-02-18  0:52   ` Linux v2.5.62 John Cherry

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=3E536237.8010502@blue-labs.org \
    --to=david+cert@blue-labs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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