mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc2 crashes
Date: Tue, 27 Jul 2004 10:32:56 -0700	[thread overview]
Message-ID: <20040727103256.2691d6f9.rddunlap@osdl.org> (raw)
In-Reply-To: <200407271343.43583.gene.heskett@verizon.net>

On Tue, 27 Jul 2004 13:43:43 -0400 Gene Heskett wrote:

| On Tuesday 27 July 2004 12:51, Randy.Dunlap wrote:
| >On Tue, 27 Jul 2004 13:02:41 -0400 Gene Heskett wrote:
| >| On Tuesday 27 July 2004 10:29,
| >| viro@parcelfarce.linux.theplanet.co.uk
| >|
| >| wrote:
| >| >On Tue, Jul 27, 2004 at 12:33:04PM -0400, Gene Heskett wrote:
| >| >> Greetings everybody;
| >| >>
| >| >> 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.
| >| >>
| >| >> All have had an initial Opps located in prune_dcache, and were
| >| >> logged as follows:
| >| >> Jul 27 07:58:58 coyote kernel: Unable to handle kernel NULL
| >| >> pointer dereference at virtual address 00000000
| >| >
| >| >... which means that dentry_unused list got corrupted, which
| >| > doesn't really help.  Could you try to narrow it down to
| >| > 2.6.8-rc1-bk<day>?
| >|
| >| I don't have bitkeeper installed.  I get my patches from
| >| kernel.org, either from the main Linus tree, or Andrews akpm tree.
| >| Is there someplace where I can dl a patchkit that leads up to rc1
| >| by the "daily" snapshot?  Or should I just get the 'broken out'
| >| patch after I verify that it also occurs with rc1 of course.  That
| >| I haven't done, mainly because rc2 has a lot of usb bugfixes and
| >| my mouse hasn't died all by itself on rc2 like it was for at least
| >| 2 dozen patches before rc2.  IIRC it did a time or 2 on rc1.
| >
| >In case you need daily bk snapshots, they are here:
| >  http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/
| 
| Thanks Randy, got all 6 of them.
| 
| >| It takes a < 1 day for this to occur usually, but seems to occur
| >| after a long session of doing something else that fails. (or maybe
| >| causes the fail, of a make install in konstruct/meta/kde)  Thats
| >| running now, someplace in kdegraphics-3.2.92 from the looks of it.
| 
| I take it that I should apply these to a 2.6.7 tarballs tree in this 
| order:
| 1. 2.6.8-rc1
>>>> 2.6.8-rc2 <<<<<

| 2. each of these 'rc2-bk' patches by the day and then run each for a 
| couple days, or should I start in the middle, say the 3rd one and 
| work forward or backwards from there depending on the results?

I'd suggest beginning with -bk3 and doing a binary search.

| Your (and Viro's) call.  I'd imagine you would want to run this to 
| earth as quick as we can.
| 
| Are these patches cumulative?  I presume they are as they grow by the 
| day.

Sorry, I should have mentioned that.  Yes, they are cumulative.

--
~Randy

  reply	other threads:[~2004-07-27 17: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 [this message]
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
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=20040727103256.2691d6f9.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=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®