search for: set_init_arg

...<EOI> ? xen_hypercall_sched_op+0xa/0x20 ? xen_hypercall_sched_op+0xa/0x20 ? xen_safe_halt+0x10/0x20 ? default_idle+0x1e/0xd0 ? arch_cpu_idle+0xf/0x20 ? default_idle_call+0x2c/0x40 ? cpu_startup_entry+0x1ac/0x240 ? rest_init+0x77/0x80 ? start_kernel+0x4a7/0x4b4 ? set_init_arg+0x55/0x55 ? x86_64_start_reservations+0x24/0x26 ? xen_start_kernel+0x555/0x561 general protection fault: 0000 [#1] SMP Call Trace: <IRQ> ? napi_gro_complete+0x5e/0xa0 skb_release_all+0x24/0x30 kfree_skb+0x32/0x90 napi_gro_complete+0x5e/0xa0 napi_gro_flush+0x5f/0x80...

...fffffff810b24a5>] ? cpu_idle_loop+0x135/0x1e0 [<ffffffff810b256b>] ? cpu_startup_entry+0x1b/0x70 [<ffffffff810b25b0>] ? cpu_startup_entry+0x60/0x70 [<ffffffff81667c57>] ? rest_init+0x77/0x80 [<ffffffff81d774c9>] ? start_kernel+0x441/0x448 [<ffffffff81d76ea6>] ? set_init_arg+0x5d/0x5d [<ffffffff81d76603>] ? x86_64_start_reservations+0x2a/0x2c [<ffffffff81d7aae1>] ? xen_start_kernel+0x5ef/0x5f1 Code: 00 0f 87 06 07 00 00 44 8b b3 b8 00 00 00 44 03 b3 c0 00 00 00 45 29 e6 41 39 c6 44 0f 47 f0 45 85 f6 0f 84 8f 00 00 00 0f ae e8 <8b> 83 c0 00 00 00 83...

...t;] ? cpu_startup_entry+0x312/0x3e0 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff816445c7>] ? rest_init+0x77/0x80 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff81d77130>] ? start_kernel+0x4d0/0x4dd Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff81d76a50>] ? set_init_arg+0x55/0x55 Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff81d765ee>] ? x86_64_start_reservations+0x2a/0x2c Jul 03 11:31:23 antares.fsoft.nnet kernel: [<ffffffff81d7a7cc>] ? xen_start_kernel+0x5a9/0x5b5 Jul 03 11:31:23 antares.fsoft.nnet kernel: handlers: Jul 03 11:31:23 antares...

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

...cpu_startup_entry+0x312/0x3e0 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff816445c7>] ? rest_init+0x77/0x80 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d77130>] ? start_kernel+0x4d0/0x4dd Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d76a50>] ? set_init_arg+0x55/0x55 Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d765ee>] ? x86_64_start_reservations+0x2a/0x2c Jul 03 11:31:23 myDom0.mynetwork.net kernel: [<ffffffff81d7a7cc>] ? xen_start_kernel+0x5a9/0x5b5 Jul 03 11:31:23 myDom0.mynetwork.net kernel: handlers: Jul 03 11:31:23 m...

...fff81009e0c>] ? xen_safe_halt+0xc/0x20 [ 4.355824] [<ffffffff8101c949>] ? default_idle+0x19/0xb0 [ 4.355920] [<ffffffff810a7dc0>] ? cpu_startup_entry+0x340/0x400 [ 4.356026] [<ffffffff81902071>] ? start_kernel+0x492/0x49d [ 4.356155] [<ffffffff81901a04>] ? set_init_arg+0x4e/0x4e [ 4.356250] [<ffffffff81903f64>] ? xen_start_kernel+0x569/0x573 [ 4.356354] Code: 66 0f 1f 44 00 00 e8 03 fc ff ff 48 8b 43 58 48 2b 43 50 88 43 4e eb e6 90 90 90 90 90 90 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 <f3> 48 a5 89 d1 f3 a4 c3 20 4c 8b 06 4c 8b 4e 08 4c 8b 56...