nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing. (http://www.nvnews.net/vbulletin/showthread.php?t=95114)

gilboa 07-18-07 01:27 PM

Xen 3.1/100.14.11 patch crashing.
 
1 Attachment(s)
Hello Jaxxon,

I'm trying to get your 96.25 patch working on Fedora 7 (Xen 3.1) + 100.14.11.
While I could get the patch applied (I removed the _RT part to make it Fedoa/kmod digestible) with some minor modification, I'm getting OOPS during driver init.
Do you have any idea what's wrong? (You seem to be a much better VMM-guru then me ;))

Thanks,
- Gilboa

gilboa 07-18-07 01:30 PM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
1 Attachment(s)
Sigh.
Reversed patch. Trying again.

zander 07-18-07 03:40 PM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
You shouldn't need to patch 100.14.11 to build it against Xen kernels, though you will need to override the sanity check (Xen is still unsupported); you can do so by setting the IGNORE_XEN_PRESENCE environment variable to 1.

gilboa 07-18-07 06:38 PM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
Quote:

Originally Posted by zander
You shouldn't need to patch 100.14.11 to build it against Xen kernels, though you will need to override the sanity check (Xen is still unsupported); you can do so by setting the IGNORE_XEN_PRESENCE environment variable to 1.

Zander,

Thanks. It's good to know.
I'll drop all the dma_attr/pfn_xxx/PAT changes and see how it goes.

Never the less, the drivers doesn't compile cleanly under Xen 3.1 (Fedora 7)
The biggest culprits are missing HYPERVISOR_memory_op prototype (that's buried deep-deep-deep under include/asm-XXX/mach-xen and missing asm/maddr.h (the same).

- Gilboa

zander 07-18-07 07:17 PM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
I suspected as much. The existing code should build/work with RHEL5, however, barring kernel-devel package bugs.

gilboa 07-19-07 08:34 AM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
Quote:

Originally Posted by zander
I suspected as much. The existing code should build/work with RHEL5, however, barring kernel-devel package bugs.

Re-did the patch - just fixed the nv-linux.h include line and the Makefile.
I know that's Xen is not officially supported, but anyone @nVidia feels like looking into it.
I'll attach a bug report once the offending machine goes up again.

Code:

NVRM: failed to register with the ACPI subsystem!
Unable to handle kernel paging request at ffff881884e2dd30 RIP:
 [<ffffffff88607b88>] :nvidia:nv_vm_malloc_pages+0x1bb/0x4d5
PGD 17d7067 PUD 0
Oops: 0000 [1] SMP
last sysfs file: /devices/pci0000:00/0000:00:0e.0/0000:0a:00.0/enable
CPU 1
Modules linked in: netbk blktap blkbk ipt_REJECT bridge nfsd exportfs lockd nfs_acl autofs4 hidp rfcomm l2cap sunrpc ipv6 ipt_LOG ipt_MASQUERADE xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nfnetlink iptable_filter ip_tables x_tables dm_multipath raid1 parport_pc lp parport loop snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device hci_usb nvidia(P) snd_pcm_oss bluetooth snd_mixer_oss serio_raw snd_pcm k8_edac edac_mc e1000 cfi_cmdset_0002 cfi_util mtdpart jedec_probe snd_timer forcedeth snd cfi_probe gen_probe ck804xrom mtdcore chipreg k8temp shpchp hwmon map_funcs sr_mod cdrom i2c_nforce2 soundcore snd_page_alloc i2c_core ata_generic sg floppy dm_snapshot dm_zero dm_mirror dm_mod pata_amd sata_nv libata mptspi mptscsih mptbase scsi_transport_spi sd_mod scsi_mod raid456 xor raid0 ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
Pid: 5149, comm: X Tainted: P      2.6.20-2925.11.fc7xen #1
RIP: e030:[<ffffffff88607b88>]  [<ffffffff88607b88>] :nvidia:nv_vm_malloc_pages+0x1bb/0x4d5
RSP: e02b:ffff8800d69b5b60  EFLAGS: 00010286
RAX: 0000001882e9dd30 RBX: ffff8800d517c3d0 RCX: 00000700d51aa000
RDX: ffff881884e2dd30 RSI: 00000000ffffffff RDI: ffff8800d51aa000
RBP: ffff8800e9f6d340 R08: 0000000000000000 R09: 00000000000cb1e5
R10: 0000000000000001 R11: ffff8800f1ecc000 R12: ffff8800d51aa000
R13: 0000000000000000 R14: ffff810000000000 R15: 00000000000002d0
FS:  00002aaaaaae8a40(0000) GS:ffffffff80579080(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000d5c9e000 CR4: 0000000000000660
Process X (pid: 5149, threadinfo ffff8800d69b4000, task ffff8800e909b040)
Stack:  00000000000000d0 0000000000000008 0000000000000001 ffffffff88a4b660
 0000000000000002 0000000000000000 ffff8800e9f6d340 ffffffff886047e2
 ffff8800e94c2400 ffff8800d5187068 ffffffff8020ba24 ffff880001f8f300
Call Trace:
 [<ffffffff886047e2>] :nvidia:nv_alloc_pages+0x34e/0x46f
 [<ffffffff8020ba24>] __might_sleep+0x26/0xd0
 [<ffffffff882be957>] :nvidia:_nv003572rm+0x48/0x51
 [<ffffffff88545e06>] :nvidia:_nv005147rm+0x35/0x176
 [<ffffffff884706bc>] :nvidia:_nv009020rm+0xa7/0x15a
 [<ffffffff8846e44e>] :nvidia:_nv009007rm+0x59b/0x5bb
 [<ffffffff8844f076>] :nvidia:_nv005745rm+0xb6/0x17a
 [<ffffffff88450658>] :nvidia:_nv008773rm+0x74/0x15c
 [<ffffffff884c6470>] :nvidia:_nv007592rm+0x7a/0x215
 [<ffffffff884c611f>] :nvidia:_nv007302rm+0x61/0x80
 [<ffffffff88295fda>] :nvidia:_nv007481rm+0xd/0x12
 [<ffffffff882c16b4>] :nvidia:_nv002690rm+0x106/0x1b3
 [<ffffffff882c2200>] :nvidia:_nv002696rm+0x338/0x4d3
 [<ffffffff882c7247>] :nvidia:rm_init_adapter+0x85/0xdb
 [<ffffffff88606661>] :nvidia:nv_kern_open+0x426/0x629
 [<ffffffff8024758a>] chrdev_open+0x149/0x198
 [<ffffffff80247441>] chrdev_open+0x0/0x198
 [<ffffffff8021e2f3>] __dentry_open+0xd9/0x1aa
 [<ffffffff80227752>] do_filp_open+0x2a/0x38
 [<ffffffff80251e79>] sys_chown+0x45/0x56
 [<ffffffff80215be9>] get_unused_fd+0xf9/0x107
 [<ffffffff80219696>] do_sys_open+0x44/0xc1
 [<ffffffff8025b300>] tracesys+0xb2/0xb7


Code: 8b 02 f6 c4 40 74 04 48 8b 52 10 8b 42 08 89 43 18 4c 89 63
RIP  [<ffffffff88607b88>] :nvidia:nv_vm_malloc_pages+0x1bb/0x4d5
 RSP <ffff8800d69b5b60>
CR2: ffff881884e2dd30
 <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
in_atomic():0, irqs_disabled():1

Call Trace:
 [<ffffffff802958db>] down_read+0x15/0x23
 [<ffffffff8029e836>] acct_collect+0x42/0x18e
 [<ffffffff80215467>] do_exit+0x200/0x809
 [<ffffffff80262c8c>] do_page_fault+0x129c/0x134b
 [<ffffffff8020ba24>] __might_sleep+0x26/0xd0
 [<ffffffff8020ad84>] get_page_from_freelist+0x315/0x3b0
 [<ffffffff802b088f>] __rmqueue+0x50/0xf9
 [<ffffffff80260447>] error_exit+0x0/0x6e
 [<ffffffff88607b88>] :nvidia:nv_vm_malloc_pages+0x1bb/0x4d5
 [<ffffffff886047e2>] :nvidia:nv_alloc_pages+0x34e/0x46f
 [<ffffffff8020ba24>] __might_sleep+0x26/0xd0
 [<ffffffff882be957>] :nvidia:_nv003572rm+0x48/0x51
 [<ffffffff88545e06>] :nvidia:_nv005147rm+0x35/0x176
 [<ffffffff884706bc>] :nvidia:_nv009020rm+0xa7/0x15a
 [<ffffffff8846e44e>] :nvidia:_nv009007rm+0x59b/0x5bb
 [<ffffffff8844f076>] :nvidia:_nv005745rm+0xb6/0x17a
 [<ffffffff88450658>] :nvidia:_nv008773rm+0x74/0x15c
 [<ffffffff884c6470>] :nvidia:_nv007592rm+0x7a/0x215
 [<ffffffff884c611f>] :nvidia:_nv007302rm+0x61/0x80
 [<ffffffff88295fda>] :nvidia:_nv007481rm+0xd/0x12
 [<ffffffff882c16b4>] :nvidia:_nv002690rm+0x106/0x1b3
 [<ffffffff882c2200>] :nvidia:_nv002696rm+0x338/0x4d3
 [<ffffffff882c7247>] :nvidia:rm_init_adapter+0x85/0xdb
 [<ffffffff88606661>] :nvidia:nv_kern_open+0x426/0x629
 [<ffffffff8024758a>] chrdev_open+0x149/0x198
 [<ffffffff80247441>] chrdev_open+0x0/0x198
 [<ffffffff8021e2f3>] __dentry_open+0xd9/0x1aa
 [<ffffffff80227752>] do_filp_open+0x2a/0x38
 [<ffffffff80251e79>] sys_chown+0x45/0x56
 [<ffffffff80215be9>] get_unused_fd+0xf9/0x107
 [<ffffffff80219696>] do_sys_open+0x44/0xc1
 [<ffffffff8025b300>] tracesys+0xb2/0xb7


gilboa 07-19-07 08:39 AM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
1 Attachment(s)
Bug report.

BTW, I know it's been asked a million times, but does nVidia have any solid plans to officially support Xen in the semi-near future?

Thanks,
Gilboa

gilboa 07-19-07 08:41 AM

Re: Calling Mr. JaXXoN - Xen 3.1/100.14.11 patch crashing.
 
1 Attachment(s)
... And patch.


All times are GMT -5. The time now is 06:14 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.