From: Gene Heskett <gene.heskett@verizon.net>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc2 crashes
Date: Wed, 28 Jul 2004 08:52:04 -0400 [thread overview]
Message-ID: <200407280852.04763.gene.heskett@verizon.net> (raw)
In-Reply-To: <10D3E6305A14470B62191D9B@sig-9-145-17-80.uk.ibm.com>
On Wednesday 28 July 2004 07:38, Andy Whitcroft wrote:
>> I just had another crash/lockup, running 2.6.8-rc2-bk3
>> At the instant, I was looking thru the menu's of the new
>> kde3.3-beta2, in the window decoration, themes etc menu,
>> where it got 14% loaded in a 60 megabyte file and it went
>> away.
>
>Confused. Previously (below) you were running 2.6.8-rc2 so the
> problem was in that version but not in -rc1 if I read you
> correctly. So I would expect you to be testing 2.6.8-rc1-bkN
> snapshots to see where your breakage was introduced.
I was having mobo problems back about rc1 times, so I'm not able to
positively say that rc1 did/did not do it. I tried to make that
clear in a later message but must not have been. Motherboard, cpu,
memory and psu are all fresh now.
As this mobo contains the nforce2 chipset, now running the reverse
engineered driver, how far back can I go without running into
problems with it?
>> I have now had 4 crashes while running 2.6.8-rc2, the last one
>> requiring a full powerdown before the intel-8x0 could
>> re-establish control over the sound.
>
>[...]
>
>> I'd revert to rc1, but I'd have to figure out a way to use this
>> .config
>
>As viro put it:
>>It goes like that:
>>2.6.7
>>2.6.7 + 7-bk<n>
>>2.6.7 + 8-rc1
>>2.6.7 + 8-rc1 + 8-rc1-bk<n>
>>2.6.7 + 8-rc2
>>2.6.7 + 8-rc2 + 8-rc2-bk<n>
>
>-apw
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.23% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attorneys please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
next prev parent reply other threads:[~2004-07-28 12:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-27 16:33 Gene Heskett
2004-07-27 13:37 ` Denis Vlasenko
2004-07-27 14:29 ` viro
2004-07-27 17:02 ` Gene Heskett
2004-07-27 16:51 ` Randy.Dunlap
2004-07-27 17:43 ` Gene Heskett
2004-07-27 17:32 ` Randy.Dunlap
2004-07-27 18:02 ` Gene Heskett
2004-07-27 17:50 ` Randy.Dunlap
2004-07-27 18:36 ` Gene Heskett
2004-07-27 18:42 ` Gene Heskett
2004-07-27 19:23 ` viro
2004-07-27 22:17 ` Gene Heskett
2004-07-27 21:40 ` Matt Mackall
2004-07-27 22:21 ` Gene Heskett
2004-07-27 17:15 ` Gene Heskett
2004-07-27 19:26 ` viro
2004-07-27 22:24 ` Gene Heskett
2004-07-27 22:25 ` Gene Heskett
2004-07-28 11:20 ` Gene Heskett
2004-07-28 11:38 ` Andy Whitcroft
2004-07-28 12:52 ` Gene Heskett [this message]
2004-07-27 17:31 ` Gene Heskett
2004-07-28 23:26 ` Gene Heskett
2004-07-29 12:53 ` Gene Heskett
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=200407280852.04763.gene.heskett@verizon.net \
--to=gene.heskett@verizon.net \
--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
all inboxes | Powered by JetHome®