linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@it.uu.se>
To: Alexander Shaduri <ashaduri@gmail.com>
Cc: Al Viro <viro@ZenIV.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: BUG: unable to handle kernel paging request at virtual address
Date: Sat, 5 Jan 2008 15:34:25 +0100	[thread overview]
Message-ID: <18303.38257.850625.70108@harpo.it.uu.se> (raw)
In-Reply-To: <20080105173601.75370546@linux.localdomain>

Alexander Shaduri writes:
 > On Sat, 5 Jan 2008 09:10:12 +0000
 > Al Viro <viro@ZenIV.linux.org.uk> wrote:
 > 
 > > and we have q->page == 0x48464443.  Seeing how we assign that sucker, that
 > > smells like we've got a page on quicklist with {0x43, 0x44, 0x46, 0x48}
 > > in its first 4 bytes.  Instead of having address of the next page stored
 > > in there...
 > > 
 > > Do other oopsen of the same kind give the same value?
 > 
 > I've got another oops here with a different value. This time a bttv message
 > preceded it. Note that the oops happened shortly *after* I stopped capturing
 > (watching the tv through mplayer).
 > 
 > Output of dmesg:
 > 
 > bttv0: OCERR @ 375e2014,bits: HSYNC OFLOW FDSR OCERR*
 > (two pages of the same message here)
 > 
 > bttv0: OCERR @ 375e2014,bits: HSYNC OFLOW FDSR OCERR*
 > bttv0: OCERR @ 375e2014,bits: HSYNC OFLOW FBUS FDSR OCERR*
 > BUG: unable to handle kernel paging request at virtual address 23232323
 >  printing eip:
 > c011d6f8
 > *pde = 00000000
 > Oops: 0000 [#1]
 > PREEMPT SMP
 > Modules linked in: ppp_generic slhc iptable_filter ip_tables ip6table_filter ip6_tables x_tables ipv6 cpufreq_conservative cpufreq_ondemand cpufreq_userspace cpufreq_powersave powernow_k8 freq_table snd_pcm_oss snd_mixer_oss snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_event snd_seq_midi_emul snd_seq capability commoncap fuse nls_koi8_r nls_cp866 loop dm_mod binfmt_misc uhci_hcd it87 hwmon_vid eeprom nvidia(P) tuner tvaudio snd_emu10k1 bttv snd_rawmidi snd_ac97_codec video_buf firmware_class ir_common ac97_bus snd_pcm snd_seq_device compat_ioctl32 i2c_algo_bit snd_timer snd_page_alloc emu10k1_gp snd_util_mem btcx_risc tveeprom videodev gameport ohci1394 ieee1394 ide_cd snd_hwdep snd v4l2_common v4l1_compat agpgart soundcore i2c_nforce2 thermal button rtc_cmos rtc_core rtc_lib forcedeth k8temp i2c_core hwmon cdrom sg ohci_hcd ehci_hcd usbcore edd fan processor pata_amd
 > CPU:    0
 > EIP:    0060:[<c011d6f8>]    Tainted: P        VLI

This kernel is tainted by the nvidia module...

  reply	other threads:[~2008-01-05 14:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-04 17:38 BUG: unable to handle kernel paging request at virtual address Alexander Shaduri
2008-01-05  9:10 ` Al Viro
2008-01-05 13:36   ` Alexander Shaduri
2008-01-05 14:34     ` Mikael Pettersson [this message]
2008-01-05 14:46       ` Alexander Shaduri
2008-01-05 20:16         ` Al Viro
2008-01-05 20:30           ` Alexander Shaduri
2008-01-05 21:20             ` Alexey Dobriyan
2008-01-05 21:30               ` Alexander Shaduri
2008-01-22 13:40               ` Alexander Shaduri
  -- strict thread matches above, loose matches on Subject: below --
2006-08-01  8:09 Chuck Ebbert
2006-07-31 14:48 Stephen Lynch
2006-07-31 15:07 ` Ingo Oeser
2006-07-31 17:48   ` Stephen Lynch

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=18303.38257.850625.70108@harpo.it.uu.se \
    --to=mikpe@it.uu.se \
    --cc=ashaduri@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).