jcezanna56
Bonjour,
j'ai quelques soucis pour utiliser virtualbox 1.4.0 sous F7.
[jrc@nadiav12 ~]$ uname -a
Linux nadiav12 2.6.20-2925.11.fc7xen #1 SMP Mon Jun 11 16:21:08 EDT 2007 i686 i686 i386 GNU/Linux
Après la compilation de vboxdrv qui ne semble pas poser de problème en direct, lors de l'insertion du module, j'ai les messages suivants dans le /var/log/messages :
Jul 23 14:11:05 nadiav12 kernel: vboxdrv: Trying to deactivate NMI watchdog permanently...
Jul 23 14:11:05 nadiav12 kernel: BUG: unable to handle kernel paging request at virtual address f57fc030
Jul 23 14:11:05 nadiav12 kernel: printing eip:
Jul 23 14:11:05 nadiav12 kernel: ee00603b
Jul 23 14:11:05 nadiav12 kernel: 2375a000 -> *pde = 00000001:19228001
Jul 23 14:11:05 nadiav12 kernel: 24828000 -> *pme = 00000000:7c15d067
Jul 23 14:11:05 nadiav12 kernel: 0015d000 -> *pte = 00000000:00000000
Jul 23 14:11:05 nadiav12 kernel: Oops: 0000 [#1]
Jul 23 14:11:05 nadiav12 kernel: SMP
Jul 23 14:11:05 nadiav12 kernel: last sysfs file: /devices/pci0000:00/0000:00:00.0/irq
Jul 23 14:11:05 nadiav12 kernel: Modules linked in: vboxdrv netbk blktap blkbk ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 xt_state nf_conntrack nfnetlink ipt_REJECT xt_tcpudp iptable_filter ip_tables x_tables bridge autofs4 hidp rfcomm l2cap bluetooth sunrpc dm_mirror dm_multipath dm_mod video sbs i2c_ec dock button battery asus_acpi backlight ac ipv6 parport_pc lp parport loop snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer serio_raw snd soundcore e1000 iTCO_wdt iTCO_vendor_support snd_page_alloc i2c_i801 i2c_core sr_mod cdrom pcspkr sg usb_storage ata_piix ata_generic libata sd_mod scsi_mod raid456 xor raid0 ext3 jbd mbcache ehci_hcd ohci_hcd uhci_hcd
Jul 23 14:11:05 nadiav12 kernel: CPU: 0Jul 23 14:11:05 nadiav12 kernel: EIP: 0061:[<ee00603b>] Not tainted VLI
Jul 23 14:11:05 nadiav12 kernel: EFLAGS: 00210286 (2.6.20-2925.11.fc7xen #1)
Jul 23 14:11:05 nadiav12 kernel: EIP is at VBoxSupDrvInit+0x3b/0x286 [vboxdrv]
Jul 23 14:11:05 nadiav12 kernel: eax: f57fc000 ebx: e5d819ec ecx: c1018a60 edx: f5416000
Jul 23 14:11:05 nadiav12 kernel: esi: e5d81800 edi: e5d81a1c ebp: e302aea4 esp: e302ae64
Jul 23 14:11:05 nadiav12 kernel: ds: 007b es: 007b ss: 0069
Jul 23 14:11:05 nadiav12 kernel: Process modprobe (pid: 5789, ti=e302a000 task=e3028a90 task.ti=e302a000)
Jul 23 14:11:05 nadiav12 kernel: Stack: ee5da815 e5d819ec c12c31c0 e5d819ec e302ae9c c11f4357 c103a634 c11f4367
Jul 23 14:11:05 nadiav12 kernel: e302ae90 c102f86a 00000000 e5d819ec 00000001 e5d819ec e5d81800 e5d81a1c
Jul 23 14:11:05 nadiav12 kernel: e302afb0 c103d23c ee5ddd48 c1273127 ee5ddd0c 00000000 00079bb8 00000618
Jul 23 14:11:05 nadiav12 kernel: Call Trace:
Jul 23 14:11:05 nadiav12 kernel: [<c1005d3a>] show_trace_log_lvl+0x1a/0x2f
Jul 23 14:11:05 nadiav12 kernel: [<c1005dea>] show_stack_log_lvl+0x9b/0xa3
Jul 23 14:11:05 nadiav12 kernel: [<c1005f86>] show_registers+0x194/0x26a
Jul 23 14:11:05 nadiav12 kernel: [<c100618d>] die+0x131/0x246
Jul 23 14:11:05 nadiav12 kernel: [<c11f79d5>] do_page_fault+0xaf7/0xc7b
Jul 23 14:11:05 nadiav12 kernel: [<c11f5cf5>] error_code+0x35/0x3c
Jul 23 14:11:05 nadiav12 kernel: [<c103d23c>] sys_init_module+0x173e/0x1899
Jul 23 14:11:05 nadiav12 kernel: [<c1005540>] syscall_call+0x7/0xb
Jul 23 14:11:05 nadiav12 kernel: =======================
Jul 23 14:11:05 nadiav12 kernel: Code: 75 09 c7 04 24 55 a7 5d ee eb 52 c7 05 60 4b 38 c1 ff ff ff ff c7 04 24 15 a8 5d ee e8 41 98 01 d3 a1 bc 0e 2c c1 2d 00 20 00 00 <8b> 50 30 f6 c2 f0 74 3b c1 ea 10 80 fa 03 76 33 8b 90 40 03 00
Jul 23 14:11:05 nadiav12 kernel: EIP: [<ee00603b>] VBoxSupDrvInit+0x3b/0x286 [vboxdrv] SS:ESP 0069:e302ae64
Jul 23 14:11:05 nadiav12 kernel: <3>BUG: sleeping function called from invalid context at kernel/rwsem.c:20
Jul 23 14:11:05 nadiav12 kernel: in_atomic():0, irqs_disabled():1
Jul 23 14:11:05 nadiav12 kernel: no locks held by modprobe/5789.
Jul 23 14:11:05 nadiav12 kernel: [<c1005d3a>] show_trace_log_lvl+0x1a/0x2f
Jul 23 14:11:05 nadiav12 kernel: [<c10062e3>] show_trace+0x12/0x14
Jul 23 14:11:05 nadiav12 kernel: [<c100635e>] dump_stack+0x16/0x18
Jul 23 14:11:05 nadiav12 kernel: [<c1019038>] __might_sleep+0xc5/0xcc
Jul 23 14:11:05 nadiav12 kernel: [<c10327c5>] down_read+0x18/0x51
Jul 23 14:11:05 nadiav12 kernel: [<c103e97e>] acct_collect+0x3b/0x145
Jul 23 14:11:05 nadiav12 kernel: [<c102186a>] do_exit+0x1c1/0x721
Jul 23 14:11:05 nadiav12 kernel: [<c100627c>] die+0x220/0x246
Jul 23 14:11:05 nadiav12 kernel: [<c11f79d5>] do_page_fault+0xaf7/0xc7b
Jul 23 14:11:05 nadiav12 kernel: [<c11f5cf5>] error_code+0x35/0x3c
Jul 23 14:11:05 nadiav12 kernel: [<c103d23c>] sys_init_module+0x173e/0x1899
Jul 23 14:11:05 nadiav12 kernel: [<c1005540>] syscall_call+0x7/0xb
Jul 23 14:11:05 nadiav12 kernel: =======================
avec un message 'segmentation fault' sur le terminal.
En outre, le module est chargé et une commande rmmod vboxdrv retourne une erreur indiquant que le module est utilisé (!!!)
Merci pour toute aide que vous voudrez bien m'apporter car je commence à perdre mon latin sur cette affaire.
