Hey folks, Just like when I compile something in g++ and it claims to be a compiler error when in fact I've done something wrong, my kernel thinks it's done something wrong. I just compiled 2.6.5-rc2 w/reiserfs, SATA, SMP (Dual Opteron 240s), SuSe 9.0. I was running Folding at Home -- one on each processor -- and then ran glxgears. Then, I got this from my machine, anyone familiar with this? Thanks, -- Jason Vertrees ----------- [cut here ] --------- [please bite here ] --------- Kernel BUG at pageattr:106 invalid operand: 0000 [1] SMP CPU 0 Pid: 11041, comm: glxgears Tainted: P 2.6.5-rc2 RIP: 0010:[<ffffffff80120dbb>] <ffffffff80120dbb>{__change_page_attr+875} RSP: 0018:0000010012a4b468 EFLAGS: 00010282 RAX: 0000000000000098 RBX: 8000000000000163 RCX: 0000010000105098 RDX: 0000010000103000 RSI: 0000010000000000 RDI: 000001003feef080 RBP: ffffffff82648000 R08: 00000100010ac440 R09: 0000000000000001 R10: 00000000000000cb R11: 0000000000000000 R12: 0000010001004968 R13: 0000010000105098 R14: 0000000000000001 R15: 8e38e38e38e38e39 FS: 0000002a9669f4a0(0000) GS:ffffffff803e5900(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000002a962a3780 CR3: 0000000000101000 CR4: 00000000000006e0 Process glxgears (pid: 11041, stackpage=1001657dab0) Stack: 0000010001d66f80 00000100010ac440 0000000000000000 0000000000000000 8000000000000163 ffffffff80120eb4 0000000000000093 00000100010ac440 0000010002648000 0000010000000000 Call Trace:<ffffffff80120eb4>{change_page_attr+164} <ffffffff8021cb50>{agp_generic_destroy_page+96} <ffffffff8021d21f>{agp_free_memory+159} <ffffffffa039db86>{:nvidia:KernFreeAGPPages+70} <ffffffffa039be48>{:nvidia:nv_free_pages+280} <ffffffffa022199a>{:nvidia:_nv000948rm+118} <ffffffffa020dec6>{:nvidia:_nv005342rm+150} <ffffffffa020dce7>{:nvidia:_nv005346rm+187} <ffffffffa020d3b8>{:nvidia:_nv005355rm+298} <ffffffffa022675e>{:nvidia:_nv005319rm+1054} <ffffffff801555d1>{__alloc_pages+161} <ffffffff801558e1>{__get_free_pages+33} <ffffffff80153661>{mempool_alloc+161} <ffffffff80134b90>{autoremove_wake_function+0} <ffffffff80134b90>{autoremove_wake_function+0} <ffffffff8022af15>{as_add_arq_rb+133} <ffffffff8022b36b>{as_insert_request+1099} <ffffffff80222b97>{__elv_add_request+55} <ffffffff80226865>{__make_request+1285} <ffffffff80134b90>{autoremove_wake_function+0} <ffffffff802251d3>{generic_make_request+339} <ffffffff8022527d>{submit_bio+141} <ffffffff8018dda2>{mpage_bio_submit+34} <ffffffff8018e95e>{do_mpage_readpage+830} <ffffffff801555d1>{__alloc_pages+161} <ffffffff8016fed9>{__find_get_block+425} <ffffffff8017001f>{__getblk+31} <ffffffff80172046>{__bread+6} <ffffffffa004d0a1>{:reiserfs:search_by_key+145} <ffffffff8012f810>{__wake_up_common+64} <ffffffff8020be6b>{n_tty_receive_buf+4859} <ffffffff8020be6b>{n_tty_receive_buf+4859} <ffffffff80150ec7>{find_get_page+23} <ffffffff80151cb8>{filemap_nopage+344} <ffffffff8015daed>{do_no_page+1437} <ffffffff8015ec32>{handle_mm_fault+354} <ffffffffa0225f5f>{:nvidia:rm_ioctl+9} <ffffffffa039d059>{:nvidia:nv_kern_ioctl+793} <ffffffff80161af7>{do_munmap+1111} <ffffffff8017fa52>{sys_ioctl+930} <ffffffff80161e15>{sys_munmap+85} <ffffffff8010f7e4>{system_call+124} Code: 0f 0b da 1c 30 80 ff ff ff ff 6a 00 48 b8 ff ff ff 7f ff ff RIP <ffffffff80120dbb>{__change_page_attr+875} RSP <0000010012a4b468> -- Jason Vertrees BSCB Graduate Student @ UTMB, Galveston javertre@utmb.edu :: http://www.bscb.utmb.edu
On Wed, 24 Mar 2004 00:08:04 -0600
Jason Vertrees
<ffffffff80151cb8>{filemap_nopage+344} <ffffffff8015daed>{do_no_page+1437} <ffffffff8015ec32>{handle_mm_fault+354} <ffffffffa0225f5f>{:nvidia:rm_ioctl+9} <ffffffffa039d059>{:nvidia:nv_kern_ioctl+793}
The binary only nvidia driver caused the crash. Talk to Nvidia, there is nothing we can here do about it. -Andi
participants (2)
-
Andi Kleen
-
Jason Vertrees