public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Krufky <mkrufky@m1k.net>
To: 7eggert@gmx.de
Cc: klasyk99@poczta.onet.pl, linux-kernel@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@brturbo.com.br>
Subject: Re: my kernel sometimes did a crash, but no panic
Date: Tue, 09 Aug 2005 15:05:43 -0400	[thread overview]
Message-ID: <42F8FE87.5010809@m1k.net> (raw)
In-Reply-To: <E1E2Z5U-0004ji-Nt@be1.lrz>

Bodo Eggert wrote:

>Klasyk <klasyk99@poczta.onet.pl> wrote:
>  
>
>>my kernel sometimes did a crash, but no panic
>>Keyboard hunged up :(
>>Network were working and I can log in. Without the keybord - it
>>generally worked.
>>
>>In logs:
>>for example:
>>
>>Aug  6 15:30:02 o kernel: Unable to handle kernel NULL pointer
>>dereference at virtual address 00
>>000000
>>Aug  6 15:30:02 o kernel:  printing eip:
>>Aug  6 15:30:02 o kernel: c026b0d9
>>Aug  6 15:30:02 o kernel: *pde = 3588d001
>>Aug  6 15:30:02 o kernel: Oops: 0000 [#1]
>>Aug  6 15:30:02 o kernel: Modules linked in: ip_nat_irc
>>    
>>
>[...]
>  
>
>>4 ieee1394 loop via-agp bt878 tuner tvaudio bttv video-buf
>>    
>>
>                                              ^^^^
>It's probably the same problem I had.
>
>There is a recent patch enabling the no_overlay=1 parameter and some PCI
>quirks to autotune this option. Please try that and, if your board isn't
>autodetected, the lspci -vvv output and the exact name of your MB chipset.
>
>I temporarily uploaded the patch to
>http://7eggert.dyndns.org/l/scratch/v4l_bttv_no_overlay_linus.patch
>  
>
I don't know if this is the same problem... Let's hope that it IS the 
same problem, because the fix that Bodo speaks of has already been 
included in 2.6.13-rc6:

http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;h=00dd1e433967872f3997a45d5adf35056fdf2f56;f=drivers/media/video/bttv-driver.c

Please test again using Kernel 2.6.13-rc6 and let us know if the problem 
persists.

-- 
Michael Krufky



  reply	other threads:[~2005-08-09 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4zEQ3-7Le-21@gated-at.bofh.it>
2005-08-09 18:44 ` my kernel sometimes did a crash, but no panic Bodo Eggert
2005-08-09 19:05   ` Michael Krufky [this message]
2005-08-09 20:14 klasyk99
  -- strict thread matches above, loose matches on Subject: below --
2005-08-09 16:04 Klasyk
2005-08-09 19:18 ` Mauro Carvalho Chehab
     [not found]   ` <1123618340.2484.9.camel@KKK>
2005-08-09 20:26     ` Mauro Carvalho Chehab
2005-08-09 20:21 ` Adrian Bunk

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=42F8FE87.5010809@m1k.net \
    --to=mkrufky@m1k.net \
    --cc=7eggert@gmx.de \
    --cc=klasyk99@poczta.onet.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab@brturbo.com.br \
    /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