public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Heimbigner <icxcnika@mar.tar.cc>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Peter Osterlund <petero2@telia.com>
Subject: Re: BUG: Null pointer dereference (2.6.21-rc7)
Date: Mon, 23 Apr 2007 16:39:45 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704231633210.25153@server.thyself> (raw)
In-Reply-To: <Pine.LNX.4.64.0704231356480.25153@server.thyself>

On Mon, 23 Apr 2007, William Heimbigner wrote:
> On Mon, 23 Apr 2007, Andrew Morton wrote:
>>  It certainly is.  Are you able to identify an earlier kernel in which this
>>  didn't happen?  2.6.20?  An earlier 2.6.21-rcX?
>
> I'll try .18 and .20 and see where that gets me - this is my first time 
> trying to set up packet writing.

Ok, on 2.6.18, I still get the warning about a recursive lock, but no dump 
regarding a null pointer dereference. The command still fails, however, 
with pkt_get_last_written_failed. On 2.6.20, I get an error similar to the
one I orignally posted (first the recursive lock warning, seconds later,
null pointer dereference).

Not sure about the recursive lock, but something between .18 and .20 
happened such that the packet writing driver didn't fail gracefully.

On a side (offtopic) note, I noticed that ACPI support changed for the 
better in very recent kernels - on both .18 and .20, there were severe 
and early errors unless I specified acpi=off

I'll see if I can figure out exactly where from 2.6.18 to .20 things went 
wrong,
William Heimbigner
icxcnika@mar.tar.cc

  reply	other threads:[~2007-04-23 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-22 23:13 BUG: Null pointer dereference (2.6.21-rc7) William Heimbigner
2007-04-23  8:00 ` Andrew Morton
2007-04-23 13:58   ` William Heimbigner
2007-04-23 16:39     ` William Heimbigner [this message]
2007-04-24  4:09       ` BUG: Null pointer dereference in fs/open.c William Heimbigner
     [not found]         ` <20070423215810.5a24ed9a.akpm@linux-foundation.org>
2007-04-24  5:10           ` William Heimbigner
2007-04-24  5:17             ` Andrew Morton
2007-04-24  5:44               ` William Heimbigner
2007-04-24  5:56                 ` Andrew Morton
2007-04-25  7:48                 ` Andrew Morton
2007-04-25 22:53                   ` William Heimbigner
2007-04-25 23:05                     ` Andrew Morton
2007-04-26  0:48                       ` William Heimbigner
2007-04-26  6:39                         ` Jens Axboe
2007-04-26  6:33                       ` Jens Axboe
2007-04-24 20:46           ` Peter Osterlund

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=Pine.LNX.4.64.0704231633210.25153@server.thyself \
    --to=icxcnika@mar.tar.cc \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.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