public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Mayo <mayo@clara.co.uk>
To: linux-media@vger.kernel.org
Cc: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] general protection fault: 0000 [1] SMP with 2.6.27 and	2.6.28
Date: Mon, 02 Feb 2009 19:18:01 +0000	[thread overview]
Message-ID: <498746E9.8010000@clara.co.uk> (raw)
In-Reply-To: <1233536229.3091.58.camel@palomino.walls.org>

Andy Walls wrote:
> On Sun, 2009-02-01 at 23:38 +0100, Oliver Endriss wrote:
>> Andy Walls wrote:
>>> On Sat, 2009-01-31 at 15:01 +0000, Chris Mayo wrote:
> 
>>> So tuner_addr is non-NULL and is not a valid pointer either.
>>>
>>> It looks like linux/drivers/media/dvb/ttpci/budget.c:frontend_init() is
>>> setting the pointer up properly.  So something else is trashing the
>>> struct dvb_frontend structure pointed to by the variable fe.  Finding
>>> what's doing that will be difficult.
>>>
>>> Without a device nor steps to reliably reproduce, that's about all I can
>>> help with.
>>>
>>> Regards,
>>> Andy
>> Afaik this bug was fixed in changeset
>> http://linuxtv.org/hg/v4l-dvb/rev/f4d7d0b84940
>>
>> CU
>> Oliver
> 
> Thanks.  I didn't realize the initialization to NULL was a recent fix.
> I was looking at very recent v4l-dvb source code with that change in
> place (which is why I thought tracking down the problem would be hard).
> 
> I agree that that change likely fixes the problem, if Chris doesn't have
> it in place.
> 
> Regards,
> Andy
> 

I didn't have the patch (and hadn't seen it so seems a good advert for
merging the lists). Have applied it to 2.6.28 and OK so far. Thanks for
pointing it out and the investigation.

Chris

      reply	other threads:[~2009-02-02 19:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-27 16:41 [linux-dvb] general protection fault: 0000 [1] SMP with 2.6.27 and 2.6.28 Chris Mayo
2009-01-31 15:01 ` Chris Mayo
2009-02-01 21:39   ` Andy Walls
2009-02-01 22:38     ` Oliver Endriss
2009-02-02  0:57       ` Andy Walls
2009-02-02 19:18         ` Chris Mayo [this message]

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=498746E9.8010000@clara.co.uk \
    --to=mayo@clara.co.uk \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-media@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