From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related?
Date: Mon, 04 Jan 2010 23:50:39 +0000 [thread overview]
Message-ID: <201001041650.39862.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <d72eeaf61001041440s58b51b9j58e62af378b55224@mail.gmail.com>
On Monday 04 January 2010 03:40:46 pm Émeric Maschino wrote:
> Indeed, it seems that something is going wrong with AGP GART. Here are
> the relevant lines of the dmesg output:
>
> [ 12.652322] Linux agpgart interface v0.103
> [ 12.715735] Unable to handle kernel NULL pointer dereference
> (address 0000000000000003)
> [ 12.715784] modprobe[895]: Oops 8804682956800 [1]
> [ 12.715819] Modules linked in: hp_agp(+) agpgart snd_fm801
> snd_ac97_codec ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm
> snd_page_alloc snd_tea575x_tuner videodev v4l1_compat
> v4l2_compat_ioctl32 i2c_core snd_opl3_lib snd_hwdep snd_mpu401_uart
> snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer
> snd_seq_device snd fm801_gp soundcore gameport evdev ext4 mbcache jbd2
> crc16 sd_mod crc_t10dif usbhid hid ide_cd_mod cdrom ide_pci_generic
> ata_generic libata tg3 mptspi mptscsih e100 ohci_hcd cmd64x libphy
> mptbase scsi_transport_spi scsi_mod mii ide_core ehci_hcd usbcore
> nls_base [last unloaded: scsi_wait_scan]
> [ 12.716925]
> [ 12.716926] Pid: 895, CPU 0, comm: modprobe
> [ 12.716988] psr : 00001010085a6010 ifs : 8000000000000712 ip :
> [<a000000202b10200>] Not tainted (2.6.32-trunk-mckinley)
> [ 12.717044] ip is at zx1_gart_probe+0xd0/0xcc0 [hp_agp]
This definitely looks like a kernel problem. I tried to reproduce it,
but regrettably, the current upstream kernel croaks before I get that
far with this:
Unable to handle kernel paging request at virtual address a00000010400ab00
swapper[0]: Oops 8804682956800 [1]
Modules linked in:
Pid: 0, CPU 0, comm: swapper
psr : 00001010084a6018 ifs : 8000000000000288 ip : [<a000000100ed8d60>] Not tainted (2.6.33-rc2-00302-gc5974b8)
ip is at proc_net_ns_init+0x100/0x160
Guess I'll have to sort through that problem first.
Bjorn
next prev parent reply other threads:[~2010-01-04 23:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 22:40 [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-04 23:50 ` Bjorn Helgaas [this message]
2010-01-07 23:02 ` Émeric Maschino
2010-01-07 23:57 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-08 20:06 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-08 23:55 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-09 11:46 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-11 17:54 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-11 18:23 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Luck, Tony
2010-01-11 18:35 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-11 21:18 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-11 21:40 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-13 7:15 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-13 17:13 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be kernel-related? Bjorn Helgaas
2010-01-14 0:10 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this Dave Airlie
2010-01-14 8:50 ` [drm:drm_mmap_locked] *ERROR* Could not find map: Could this be Émeric Maschino
2010-01-14 8:54 ` Émeric Maschino
2010-01-18 15:44 ` Émeric Maschino
2010-01-22 22:19 ` Émeric Maschino
2010-02-02 21:05 ` Émeric Maschino
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=201001041650.39862.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=linux-ia64@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