nouveau, linux3.8-rc5: BUG: unable to handle kernel paging request at fffffffffffffff8
On Sat, 26 Jan 2013 21:40:47 +1000 Ben Skeggs wrote: > On Sat, 2013-01-26 at 11:53 +0100, Antonio Ospite wrote: > > Hi, > > > > I am experiencing a bug with nouveau with linux-3.8-rc5, my video > > adapter is the one integrated on the MSI M3N78-VM motherboard (hence > > x86_64): > > > > 02:00.0 VGA compatible controller: NVIDIA Corporation C77 [GeForce 8200] > > (rev a2) (prog-if 00 [VGA controller]) > > Subsystem: ASUSTeK Computer Inc. Device 82f2 > > Flags: bus master, fast devsel, latency 0, IRQ 21 > > Memory at fd00 (32-bit, non-prefetchable) [size=16M] > > Memory at f000 (64-bit, prefetchable) [size=128M] > > Memory at fa00 (64-bit, prefetchable) [size=32M] > > I/O ports at ec00 [size=128] > > Expansion ROM at febe [disabled] [size=128K] > > Capabilities: > > Kernel driver in use: nouveau > > > > The problem happens every time I use some 3D feature, for instance the > > trace below is from after I started "blender": > > > > > > [ 6163.299538] BUG: unable to handle kernel paging request at > > fff8 > > [ 6163.299600] IP: [] nouveau_mm_head+0x30/0x127 [nouveau] > > It's a known issue, and the fix will be in my next -fixes merge request. > > Ben. Hi Ben, the problem is still there in 3.8-rc7. Regards, Antonio > > [ 6163.299714] PGD 160e067 PUD 160f067 PMD 0 > > [ 6163.299739] Oops: [#1] SMP > > [ 6163.299757] Modules linked in: hidp ebtable_nat ebtables > > cpufreq_powersave cpufreq_conservative cpufreq_stats cpufreq_userspace > > ipt_MASQUERADE xt_CHECKSUM bridge stp llc ppdev lp bnep rfcomm tun sit > > tunnel4 binfmt_misc uinput ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad > > ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6table_raw > > ip6table_mangle ip6t_REJECT xt_LOG nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_rt > > ip6table_filter ip6_tables xt_tcpudp ipt_REJECT ipt_ULOG xt_limit > > xt_multiport xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4 > > nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw > > ip_tables x_tables loop fuse snd_hda_codec_hdmi snd_hda_codec_via lm63 > > adm1021 snd_hda_intel snd_hda_codec snd_usb_audio snd_usbmidi_lib snd_hwdep > > lm90 snd_pcm_oss snd_mixer_oss f75375s snd_seq_midi snd_pcm > > snd_seq_midi_event snd_rawmidi snd_seq snd_page_alloc snd_seq_device > > adt7475 hwmon_vid snd_timer btusb snd nouveau bluetooth ttm drm_kms_help! > er! > > drm mx > > m_wmi powernow_k8 i2c_algo_bit edac_mce_amd edac_core parport_pc shpchp > > kvm_amd soundcore rfkill crc16 kvm evdev pcspkr parport ehci_pci k8temp > > video asus_atk0110 wmi processor thermal_sys i2c_nforce2 i2c_core button > > ext3 mbcache jbd sg sr_mod cdrom usb_storage hid_generic usbhid hid sd_mod > > crc_t10dif dm_mod ahci libahci libata ohci_hcd ehci_hcd forcedeth scsi_mod > > usbcore usb_common floppy > > [ 6163.300023] CPU 0 > > [ 6163.300023] Pid: 3460, comm: Xorg Not tainted 3.8.0-rc5-ao2 #6 System > > manufacturer System Product Name/M3N78-VM > > [ 6163.300023] RIP: 0010:[] [] > > nouveau_mm_head+0x30/0x127 [nouveau] > > [ 6163.300023] RSP: 0018:8801167eb9c8 EFLAGS: 00010216 > > [ 6163.300023] RAX: RBX: fff0 RCX: > > 006c > > [ 6163.300023] RDX: 006c RSI: 0001 RDI: > > 8801167e6108 > > [ 6163.300023] RBP: 8800bb334d78 R08: R09: > > 8800bb334d78 > > [ 6163.300023] R10: 0360 R11: 8800bb334cc0 R12: > > 006c > > [ 6163.300023] R13: 8801167e6001 R14: 8801167e6020 R15: > > 8801167eba90 > > [ 6163.300023] FS: 7f23f04c2880() GS:88011fc0() > > knlGS: > > [ 6163.300023] CS: 0010 DS: ES: CR0: 80050033 > > [ 6163.300023] CR2: fff8 CR3: 0001194d6000 CR4: > > 07f0 > > [ 6163.300023] DR0: DR1: DR2: > > > > [ 6163.300023] DR3: DR6: 0ff0 DR7: > > 0400 > > [ 6163.300023] Process Xorg (pid: 3460, threadinfo 8801167ea000, task > > 88011770a7c0) > > [ 6163.300023] Stack: > > [ 6163.300023] 80d0 167e6020 0002 > > 0360 > > [ 6163.300023] 0002 0010 8801167e6000 > > 8801167e6020 > > [ 6163.300023] 8801167eb
Re: nouveau, linux3.8-rc5: BUG: unable to handle kernel paging request at fffffffffffffff8
On Sat, 26 Jan 2013 21:40:47 +1000 Ben Skeggs bske...@redhat.com wrote: On Sat, 2013-01-26 at 11:53 +0100, Antonio Ospite wrote: Hi, I am experiencing a bug with nouveau with linux-3.8-rc5, my video adapter is the one integrated on the MSI M3N78-VM motherboard (hence x86_64): 02:00.0 VGA compatible controller: NVIDIA Corporation C77 [GeForce 8200] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device 82f2 Flags: bus master, fast devsel, latency 0, IRQ 21 Memory at fd00 (32-bit, non-prefetchable) [size=16M] Memory at f000 (64-bit, prefetchable) [size=128M] Memory at fa00 (64-bit, prefetchable) [size=32M] I/O ports at ec00 [size=128] Expansion ROM at febe [disabled] [size=128K] Capabilities: access denied Kernel driver in use: nouveau The problem happens every time I use some 3D feature, for instance the trace below is from after I started blender: [ 6163.299538] BUG: unable to handle kernel paging request at fff8 [ 6163.299600] IP: [a02cff32] nouveau_mm_head+0x30/0x127 [nouveau] It's a known issue, and the fix will be in my next -fixes merge request. Ben. Hi Ben, the problem is still there in 3.8-rc7. Regards, Antonio [ 6163.299714] PGD 160e067 PUD 160f067 PMD 0 [ 6163.299739] Oops: [#1] SMP [ 6163.299757] Modules linked in: hidp ebtable_nat ebtables cpufreq_powersave cpufreq_conservative cpufreq_stats cpufreq_userspace ipt_MASQUERADE xt_CHECKSUM bridge stp llc ppdev lp bnep rfcomm tun sit tunnel4 binfmt_misc uinput ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip6table_raw ip6table_mangle ip6t_REJECT xt_LOG nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_rt ip6table_filter ip6_tables xt_tcpudp ipt_REJECT ipt_ULOG xt_limit xt_multiport xt_conntrack iptable_filter iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw ip_tables x_tables loop fuse snd_hda_codec_hdmi snd_hda_codec_via lm63 adm1021 snd_hda_intel snd_hda_codec snd_usb_audio snd_usbmidi_lib snd_hwdep lm90 snd_pcm_oss snd_mixer_oss f75375s snd_seq_midi snd_pcm snd_seq_midi_event snd_rawmidi snd_seq snd_page_alloc snd_seq_device adt7475 hwmon_vid snd_timer btusb snd nouveau bluetooth ttm drm_kms_hel p! er! drm mx m_wmi powernow_k8 i2c_algo_bit edac_mce_amd edac_core parport_pc shpchp kvm_amd soundcore rfkill crc16 kvm evdev pcspkr parport ehci_pci k8temp video asus_atk0110 wmi processor thermal_sys i2c_nforce2 i2c_core button ext3 mbcache jbd sg sr_mod cdrom usb_storage hid_generic usbhid hid sd_mod crc_t10dif dm_mod ahci libahci libata ohci_hcd ehci_hcd forcedeth scsi_mod usbcore usb_common floppy [ 6163.300023] CPU 0 [ 6163.300023] Pid: 3460, comm: Xorg Not tainted 3.8.0-rc5-ao2 #6 System manufacturer System Product Name/M3N78-VM [ 6163.300023] RIP: 0010:[a02cff32] [a02cff32] nouveau_mm_head+0x30/0x127 [nouveau] [ 6163.300023] RSP: 0018:8801167eb9c8 EFLAGS: 00010216 [ 6163.300023] RAX: RBX: fff0 RCX: 006c [ 6163.300023] RDX: 006c RSI: 0001 RDI: 8801167e6108 [ 6163.300023] RBP: 8800bb334d78 R08: R09: 8800bb334d78 [ 6163.300023] R10: 0360 R11: 8800bb334cc0 R12: 006c [ 6163.300023] R13: 8801167e6001 R14: 8801167e6020 R15: 8801167eba90 [ 6163.300023] FS: 7f23f04c2880() GS:88011fc0() knlGS: [ 6163.300023] CS: 0010 DS: ES: CR0: 80050033 [ 6163.300023] CR2: fff8 CR3: 0001194d6000 CR4: 07f0 [ 6163.300023] DR0: DR1: DR2: [ 6163.300023] DR3: DR6: 0ff0 DR7: 0400 [ 6163.300023] Process Xorg (pid: 3460, threadinfo 8801167ea000, task 88011770a7c0) [ 6163.300023] Stack: [ 6163.300023] 80d0 167e6020 0002 0360 [ 6163.300023] 0002 0010 8801167e6000 8801167e6020 [ 6163.300023] 8801167eba90 a02e19be 8801167ebb00 0360e000 [ 6163.300023] Call Trace: [ 6163.300023] [a02e19be] ? nv50_fb_vram_new+0xc5/0x1f2 [nouveau] [ 6163.300023] [a0324e3a] ? nouveau_vram_manager_new+0x62/0xa4 [nouveau] [ 6163.300023] [a029fc6a] ? ttm_bo_mem_space+0x113/0x301 [ttm] [ 6163.300023] [81383c00] ? _raw_write_lock_irqsave+0x19/0x2a [ 6163.300023] [8110b000] ? create_object+0x1e9/0x299 [ 6163.300023] [a029feef] ? ttm_bo_move_buffer+0x97/0xdd [ttm] [ 6163.300023] [a029ffd4] ? ttm_bo_validate+0x9f/0xdd [ttm
nouveau, linux3.8-rc5: BUG: unable to handle kernel paging request at fffffffffffffff8
163.300023] [] ? sys_ioctl+0x4d/0x7c [ 6163.300023] [] ? system_call_fastpath+0x16/0x1b [ 6163.300023] Code: 44 89 c0 41 56 f7 d0 41 55 41 88 f5 41 54 41 89 d4 55 4c 89 cd 53 48 83 ec 18 48 8b 5f 10 89 44 24 0c 48 83 eb 10 e9 da 00 00 00 <48> 8b 43 08 44 8b 53 34 44 8b 7b 38 48 39 f8 45 89 d3 47 8d 0c [ 6163.300023] RIP [] nouveau_mm_head+0x30/0x127 [nouveau] [ 6163.300023] RSP [ 6163.300023] CR2: fff8 [ 6163.300023] ---[ end trace b0239eaa41f9b476 ]--- [ 6165.326199] nouveau E[ PDISP][:02:00.0] chid 1 mthd 0x0080 data 0x 0x000b5080 I had a similar issue in 3.7-rc cycle, here is a link to the discussion https://lkml.org/lkml/2012/10/29/696 where David explained the cause, I am not sure if this is the same scenario tho. Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
nouveau, linux3.8-rc5: BUG: unable to handle kernel paging request at fffffffffffffff8
] ? drm_gem_flink_ioctl+0xc1/0xde [drm] [ 6163.300023] [a026e603] ? drm_ioctl+0x28c/0x36a [drm] [ 6163.300023] [a0327e36] ? nouveau_gem_new+0xf7/0xf7 [nouveau] [ 6163.300023] [8111949e] ? vfs_ioctl+0x1e/0x31 [ 6163.300023] [81119cd6] ? do_vfs_ioctl+0x3ee/0x430 [ 6163.300023] [8110cf1c] ? vfs_read+0xac/0xf5 [ 6163.300023] [81119d65] ? sys_ioctl+0x4d/0x7c [ 6163.300023] [81388f29] ? system_call_fastpath+0x16/0x1b [ 6163.300023] Code: 44 89 c0 41 56 f7 d0 41 55 41 88 f5 41 54 41 89 d4 55 4c 89 cd 53 48 83 ec 18 48 8b 5f 10 89 44 24 0c 48 83 eb 10 e9 da 00 00 00 48 8b 43 08 44 8b 53 34 44 8b 7b 38 48 39 f8 45 89 d3 47 8d 0c [ 6163.300023] RIP [a02cff32] nouveau_mm_head+0x30/0x127 [nouveau] [ 6163.300023] RSP 8801167eb9c8 [ 6163.300023] CR2: fff8 [ 6163.300023] ---[ end trace b0239eaa41f9b476 ]--- [ 6165.326199] nouveau E[ PDISP][:02:00.0] chid 1 mthd 0x0080 data 0x 0x000b5080 I had a similar issue in 3.7-rc cycle, here is a link to the discussion https://lkml.org/lkml/2012/10/29/696 where David explained the cause, I am not sure if this is the same scenario tho. Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
On Mon, 5 Nov 2012 08:40:38 + Dave Airlie wrote: > On Mon, Nov 5, 2012 at 8:29 AM, Antonio Ospite > wrote: > > On Mon, 29 Oct 2012 23:16:24 +0100 > > Antonio Ospite wrote: > > > >> Hi, > >> > >> I am experiencing a bug with nouveau with linux-3.7-rc3 (and since rc1), > >> my video adapter is the one integrated on the MSI M3N78-VM motherboard > >> (hence x86_64): > >> > > [...] > >> [ 1943.858601] BUG: unable to handle kernel paging request at > >> fff8 > >> [ 1943.858669] IP: [] nouveau_mm_head+0x30/0x127 > >> [nouveau] > >> [ 1943.858779] PGD 160d067 PUD 160e067 PMD 0 > >> [ 1943.858803] Oops: [#1] SMP > > [..] > >> [ 1943.860018] Call Trace: > >> [ 1943.860019] [] ? kmem_cache_alloc_trace+0xbf/0xcf > >> [ 1943.860019] [] ? should_resched+0x5/0x23 > >> [ 1943.860019] [] ? nv50_fb_vram_new+0xc5/0x1f2 > >> [nouveau] > > > > Ben, I cannot reproduce the crash with 3.7-rc4, I spotted commits > > a7dbf00 and 5cad16a which seem to be related to the problem I was > > having; would you mind elaborating a bit about what you think was > > causing the crash on my side? Maybe the chipset used on this motherboard > > doesn't support some feature? And how did you figured out from the logs? > > > > 5cad16acd25b16681a060d28d10eeacf98d07701 is the actual fix > > The chipset hasn't got Z compression support, and the oops once decoded > pointed > out the new code was trying to allocate Z tags from a NULL memory block. The > old > code use to allocate an empty memory block instead of NULL, and it got > lost in the > rewrite, Ben just fixed it to allow empty memory blocks again. > > Dave. > Thanks a lot for the explanation. Regards, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
On Mon, 29 Oct 2012 23:16:24 +0100 Antonio Ospite wrote: > Hi, > > I am experiencing a bug with nouveau with linux-3.7-rc3 (and since rc1), > my video adapter is the one integrated on the MSI M3N78-VM motherboard > (hence x86_64): > [...] > [ 1943.858601] BUG: unable to handle kernel paging request at fff8 > [ 1943.858669] IP: [] nouveau_mm_head+0x30/0x127 [nouveau] > [ 1943.858779] PGD 160d067 PUD 160e067 PMD 0 > [ 1943.858803] Oops: [#1] SMP [..] > [ 1943.860018] Call Trace: > [ 1943.860019] [] ? kmem_cache_alloc_trace+0xbf/0xcf > [ 1943.860019] [] ? should_resched+0x5/0x23 > [ 1943.860019] [] ? nv50_fb_vram_new+0xc5/0x1f2 [nouveau] Ben, I cannot reproduce the crash with 3.7-rc4, I spotted commits a7dbf00 and 5cad16a which seem to be related to the problem I was having; would you mind elaborating a bit about what you think was causing the crash on my side? Maybe the chipset used on this motherboard doesn't support some feature? And how did you figured out from the logs? Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Re: nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
On Mon, 29 Oct 2012 23:16:24 +0100 Antonio Ospite osp...@studenti.unina.it wrote: Hi, I am experiencing a bug with nouveau with linux-3.7-rc3 (and since rc1), my video adapter is the one integrated on the MSI M3N78-VM motherboard (hence x86_64): [...] [ 1943.858601] BUG: unable to handle kernel paging request at fff8 [ 1943.858669] IP: [a031a67a] nouveau_mm_head+0x30/0x127 [nouveau] [ 1943.858779] PGD 160d067 PUD 160e067 PMD 0 [ 1943.858803] Oops: [#1] SMP [..] [ 1943.860018] Call Trace: [ 1943.860019] [810fa13d] ? kmem_cache_alloc_trace+0xbf/0xcf [ 1943.860019] [81060f13] ? should_resched+0x5/0x23 [ 1943.860019] [a032a10a] ? nv50_fb_vram_new+0xc5/0x1f2 [nouveau] Ben, I cannot reproduce the crash with 3.7-rc4, I spotted commits a7dbf00 and 5cad16a which seem to be related to the problem I was having; would you mind elaborating a bit about what you think was causing the crash on my side? Maybe the chipset used on this motherboard doesn't support some feature? And how did you figured out from the logs? Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
On Mon, 5 Nov 2012 08:40:38 + Dave Airlie airl...@gmail.com wrote: On Mon, Nov 5, 2012 at 8:29 AM, Antonio Ospite osp...@studenti.unina.it wrote: On Mon, 29 Oct 2012 23:16:24 +0100 Antonio Ospite osp...@studenti.unina.it wrote: Hi, I am experiencing a bug with nouveau with linux-3.7-rc3 (and since rc1), my video adapter is the one integrated on the MSI M3N78-VM motherboard (hence x86_64): [...] [ 1943.858601] BUG: unable to handle kernel paging request at fff8 [ 1943.858669] IP: [a031a67a] nouveau_mm_head+0x30/0x127 [nouveau] [ 1943.858779] PGD 160d067 PUD 160e067 PMD 0 [ 1943.858803] Oops: [#1] SMP [..] [ 1943.860018] Call Trace: [ 1943.860019] [810fa13d] ? kmem_cache_alloc_trace+0xbf/0xcf [ 1943.860019] [81060f13] ? should_resched+0x5/0x23 [ 1943.860019] [a032a10a] ? nv50_fb_vram_new+0xc5/0x1f2 [nouveau] Ben, I cannot reproduce the crash with 3.7-rc4, I spotted commits a7dbf00 and 5cad16a which seem to be related to the problem I was having; would you mind elaborating a bit about what you think was causing the crash on my side? Maybe the chipset used on this motherboard doesn't support some feature? And how did you figured out from the logs? 5cad16acd25b16681a060d28d10eeacf98d07701 is the actual fix The chipset hasn't got Z compression support, and the oops once decoded pointed out the new code was trying to allocate Z tags from a NULL memory block. The old code use to allocate an empty memory block instead of NULL, and it got lost in the rewrite, Ben just fixed it to allow empty memory blocks again. Dave. Thanks a lot for the explanation. Regards, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
On Tue, 30 Oct 2012 15:17:21 +1000 Ben Skeggs wrote: > On Mon, 2012-10-29 at 23:16 +0100, Antonio Ospite wrote: [...] > > The problem presents itself as soon as I use a gnome-shell session from > > gdm3, if I use the fall-back mode (gnome-panel) it does not happen > > immediately, until maybe some processes do something stressful (firefox > > triggered it twice). > If you boot into fallback mode and run glxgears (or whatever, some 3d > app) does this happen too? It does: as soon as I run glxgears the driver crashes. > > Here is the kernel trace, please let me know if the disassembled > > nouveau.o ?or any other information? is necessary: > Are you able to post me your entire kernel log from before this happens? I am pasting it below, I noticed in particular the line: nouveau [ DRM] allocated 1024x768 fb: 0x5, bo 88011a025800 I am setting video=1024x768 in the kernel command line because without any resolution set nouveau and my monitor do not get along, but then in Xorg I am using a bigger resolution, this setup works fine in 3.5 tho so maybe it's not that. Full kernel log from boot to crash: imklog 5.8.11, log source = /proc/kmsg started. [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.7.0-rc3-ao2 (ao2 at jcn) (gcc version 4.7.2 (Debian 4.7.2-4) ) #1 SMP Mon Oct 29 13:14:36 CET 2012 [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc3-ao2 root=UUID=614c68fd-bd5f-4627-9f62-1f0cada81683 ro quiet video=1024x768 [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009dbff] usable [0.00] BIOS-e820: [mem 0x0009dc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000e3000-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xcff8] usable [0.00] BIOS-e820: [mem 0xcff9-0xcff9dfff] ACPI data [0.00] BIOS-e820: [mem 0xcff9e000-0xcffd] ACPI NVS [0.00] BIOS-e820: [mem 0xcffe-0xcffedfff] reserved [0.00] BIOS-e820: [mem 0xcfff-0xcfff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfeef] reserved [0.00] BIOS-e820: [mem 0xfff0-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00011fff] usable [0.00] NX (Execute Disable) protection: active [0.00] DMI present. [0.00] DMI: System manufacturer System Product Name/M3N78-VM, BIOS 1801 09/10/2010 [0.00] e820: update [mem 0x-0x] usable ==> reserved [0.00] e820: remove [mem 0x000a-0x000f] usable [0.00] No AGP bridge found [0.00] e820: last_pfn = 0x12 max_arch_pfn = 0x4 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-E uncachable [0.00] F-F write-protect [0.00] MTRR variable ranges enabled: [0.00] 0 base 00 mask FF8000 write-back [0.00] 1 base 008000 mask FFC000 write-back [0.00] 2 base 00C000 mask FFF000 write-back [0.00] 3 disabled [0.00] 4 disabled [0.00] 5 disabled [0.00] 6 disabled [0.00] 7 disabled [0.00] TOM2: 00012000 aka 4608M [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] e820: update [mem 0xd000-0x] usable ==> reserved [0.00] e820: last_pfn = 0xcff90 max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [880ff780] [0.00] initial memory mapped: [mem 0x-0x1fff] [0.00] Base memory trampoline at [88097000] 97000 size 24576 [0.00] init_memory_mapping: [mem 0x-0xcff8] [0.00] [mem 0x-0xcfdf] page 2M [0.00] [mem 0xcfe0-0xcff8] page 4k [0.00] kernel direct mapping tables up to 0xcff8 @ [mem 0x1fffa000-0x1fff] [0.00] init_memory_mapping: [mem 0x1-0x11fff] [0.00] [mem 0x1-0x11fff] page 2M [0.00] kernel direct mapping tables up to 0x11fff @ [mem 0xcff8e000-0xcff8] [0.00] RAMDISK: [mem 0x368de000-0x37466fff] [0.00] ACPI: RSDP 000fb630 00024 (v02 ACPIAM) [0.00] ACPI: XSDT cff90100 0006C (v01 091010 XSDT1648 20100910 MSFT 0097) [0.00] ACPI: FACP cff90290 000F4 (v03 091010 FACP1648 20100910 MSFT 0097) [0.00] ACPI: DSDT cff90460 0AF17 (v01 A1041 A1041000 INTL 20060113) [0.00]
nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
[ 1943.860019] [] ? _cond_resched+0x6/0x1b [ 1943.860019] [] ? nouveau_gem_ioctl_new+0x9f/0x107 [nouveau] [ 1943.860019] [] ? drm_gem_flink_ioctl+0xc1/0xde [drm] [ 1943.860019] [] ? drm_ioctl+0x28c/0x36a [drm] [ 1943.860019] [] ? handle_pte_fault+0x6ff/0x770 [ 1943.860019] [] ? nouveau_gem_new+0xf7/0xf7 [nouveau] [ 1943.860019] [] ? __do_page_fault+0x2d8/0x376 [ 1943.860019] [] ? vfs_ioctl+0x1e/0x31 [ 1943.860019] [] ? do_vfs_ioctl+0x3ee/0x430 [ 1943.860019] [] ? vfs_read+0xac/0xf5 [ 1943.860019] [] ? sys_ioctl+0x4d/0x7c [ 1943.860019] [] ? system_call_fastpath+0x16/0x1b [ 1943.860019] Code: 44 89 c0 41 56 f7 d0 41 55 41 88 f5 41 54 41 89 d4 55 4c 89 cd 53 48 83 ec 18 48 8b 5f 10 89 44 24 0c 48 83 eb 10 e9 da 00 00 00 <48> 8b 43 08 44 8b 53 34 44 8b 7b 38 48 39 f8 45 89 d3 47 8d 0c [ 1943.860019] RIP [] nouveau_mm_head+0x30/0x127 [nouveau] [ 1943.860019] RSP [ 1943.860019] CR2: fff8 [ 1943.860019] ---[ end trace cbc160afe55cb77d ]--- [ 1945.878352] nouveau E[ DRM] EvoCh 1 Mthd 0x0080 Data 0x (0x000b 0x05) [ 1945.880013] [sched_delayed] sched: RT throttling activated Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
nouveau, linux3.7-rc3: BUG: unable to handle kernel paging request at fffffffffffffff8
] [a036a021] ? nouveau_bo_new+0x23f/0x264 [nouveau] [ 1943.860019] [a0369c55] ? nouveau_ttm_tt_unpopulate+0xa3/0xa3 [nouveau] [ 1943.860019] [a036b77a] ? nouveau_gem_new+0x53/0xf7 [nouveau] [ 1943.860019] [81060f13] ? should_resched+0x5/0x23 [ 1943.860019] [8137031a] ? _cond_resched+0x6/0x1b [ 1943.860019] [a036b8bd] ? nouveau_gem_ioctl_new+0x9f/0x107 [nouveau] [ 1943.860019] [a022507b] ? drm_gem_flink_ioctl+0xc1/0xde [drm] [ 1943.860019] [a0223603] ? drm_ioctl+0x28c/0x36a [drm] [ 1943.860019] [810dfe6e] ? handle_pte_fault+0x6ff/0x770 [ 1943.860019] [a036b81e] ? nouveau_gem_new+0xf7/0xf7 [nouveau] [ 1943.860019] [81373f12] ? __do_page_fault+0x2d8/0x376 [ 1943.860019] [8110eb82] ? vfs_ioctl+0x1e/0x31 [ 1943.860019] [8110f3ba] ? do_vfs_ioctl+0x3ee/0x430 [ 1943.860019] [8110289c] ? vfs_read+0xac/0xf5 [ 1943.860019] [8110f449] ? sys_ioctl+0x4d/0x7c [ 1943.860019] [81376129] ? system_call_fastpath+0x16/0x1b [ 1943.860019] Code: 44 89 c0 41 56 f7 d0 41 55 41 88 f5 41 54 41 89 d4 55 4c 89 cd 53 48 83 ec 18 48 8b 5f 10 89 44 24 0c 48 83 eb 10 e9 da 00 00 00 48 8b 43 08 44 8b 53 34 44 8b 7b 38 48 39 f8 45 89 d3 47 8d 0c [ 1943.860019] RIP [a031a67a] nouveau_mm_head+0x30/0x127 [nouveau] [ 1943.860019] RSP 8801179519a8 [ 1943.860019] CR2: fff8 [ 1943.860019] ---[ end trace cbc160afe55cb77d ]--- [ 1945.878352] nouveau E[ DRM] EvoCh 1 Mthd 0x0080 Data 0x (0x000b 0x05) [ 1945.880013] [sched_delayed] sched: RT throttling activated Thanks, Antonio -- Antonio Ospite http://ao2.it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
