Re: [qubes-users] Fresh installation, no network Q4.0-rc3
W dniu środa, 20 grudnia 2017 15:00:52 UTC+1 użytkownik awokd napisał: > On Wed, December 20, 2017 1:34 pm, X4lldux wrote: > > Hi, > > > > > > I've installed Qubes4 rc3 but it has no network. Dmesg from sys-net had > > this in it: > > > [1.626169] igb :00:05.0: Using MSI interrupts. 1 rx queue(s), 1 tx > > queue(s) [1.626642] xen: --> pirq=18 -> irq=40 (gsi=40) > > I've been troubleshooting a similar issue. Try qvm-prefs sys-net. Note the > kernelopts line, then: > qvm-prefs sys-net kernelopts "[original kernelopts] pci=nomsi" > > It didn't work for me but might help yours, but not sure what performance > impact there will be. You could also try changing virt_mode to pv if it > still doesn't work. adding pci=nomsi worked. Thanks! Though, I hope this will not be needed in the future. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b3b280b6-1eda-463f-b037-ba679dc0e422%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Fresh installation, no network Q4.0-rc3
224] IPv6: ADDRCONF(NETDEV_UP): ens6: link is not ready [8.175197] IPv6: ADDRCONF(NETDEV_UP): ens6: link is not ready [8.293958] Netfilter messages via NETLINK v0.30. [8.298363] nf_tables: (c) 2007-2009 Patrick McHardy <ka...@trash.net> [9.934955] IPv6: ADDRCONF(NETDEV_UP): vif12.0: link is not ready [ 10.029315] vif vif-12-0 vif12.0: Guest Rx ready [ 10.031383] IPv6: ADDRCONF(NETDEV_CHANGE): vif12.0: link becomes ready [ 10.404071] IPv6: ADDRCONF(NETDEV_UP): vif11.0: link is not ready [ 12.704830] igb :00:06.0 ens6: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 12.705602] IPv6: ADDRCONF(NETDEV_CHANGE): ens6: link becomes ready [ 17.888087] [ cut here ] [ 17.888151] WARNING: CPU: 1 PID: 0 at /home/user/rpmbuild/BUILD/kernel-4.9.56/linux-4.9.56/net/sched/sch_generic.c:316 dev_watchdog+0x22c/0x230 [ 17.888232] NETDEV WATCHDOG: ens6 (igb): transmit queue 0 timed out [ 17.888273] Modules linked in: iptable_raw nf_conntrack_ipv6 nf_defrag_ipv6 nft_ct nf_tables_ipv6 nf_tables_ipv4 nf_tables nfnetlink xt_REDIRECT nf_nat_redirect xen_netback ip6table_filter ip6_tables xt_conntrack ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack joydev intel_rapl sb_edac edac_core crct10dif_pclmul crc32_pclmul crc32c_intel ppdev ghash_clmulni_intel input_leds psmouse pcspkr serio_raw parport_pc floppy parport fjes bochs_drm ttm igb drm_kms_helper drm ptp pps_core i2c_piix4 i2c_algo_bit uhci_hcd dca ehci_pci ehci_hcd tpm_tis tpm_tis_core ata_generic pata_acpi tpm xenfs xen_privcmd xen_blkback u2mfn(O) xen_blkfront [ 17.888783] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G O 4.9.56-21.pvops.qubes.x86_64 #1 [ 17.37] Hardware name: Xen HVM domU, BIOS 4.8.2 11/05/2017 [ 17.77] 97e697903d88 b33ea212 97e697903dd8 [ 17.888939] 97e697903dc8 b30a02eb 013c97903dd0 [ 17.889004] 0008 0001 97e68ccb8000 97e694fdb940 [ 17.889064] Call Trace: [ 17.889068] [ 17.889068] [] dump_stack+0x63/0x81 [ 17.889068] [] __warn+0xcb/0xf0 [ 17.889068] [] warn_slowpath_fmt+0x5f/0x80 [ 17.889068] [] ? tick_program_event+0x44/0x70 [ 17.889068] [] dev_watchdog+0x22c/0x230 [ 17.889068] [] ? qdisc_rcu_free+0x40/0x40 [ 17.889068] [] call_timer_fn+0x35/0x120 [ 17.889068] [] run_timer_softirq+0x333/0x9d0 [ 17.889068] [] ? handle_percpu_irq+0x3a/0x50 [ 17.889068] [] __do_softirq+0x104/0x28c [ 17.889068] [] irq_exit+0xea/0xf0 [ 17.889068] [] xen_evtchn_do_upcall+0x35/0x40 [ 17.889068] [] xen_hvm_callback_vector+0x8c/0xa0 [ 17.889068] [ 17.889068] [] ? native_safe_halt+0x6/0x10 [ 17.889068] [] default_idle+0x20/0xd0 [ 17.889068] [] arch_cpu_idle+0xf/0x20 [ 17.889068] [] default_idle_call+0x23/0x30 [ 17.889068] [] cpu_startup_entry+0x1d0/0x240 [ 17.889068] [] start_secondary+0x151/0x190 [ 17.889068] ---[ end trace c02494804aa4bef3 ]--- [ 17.889068] igb :00:06.0 ens6: Reset adapter [ 18.439126] vif vif-11-0 vif11.0: Guest Rx ready [ 18.439186] IPv6: ADDRCONF(NETDEV_CHANGE): vif11.0: link becomes ready [ 21.728681] igb :00:06.0 ens6: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 27.104143] igb :00:06.0 ens6: Reset adapter [ 31.712962] igb :00:06.0 ens6: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 36.832132] igb :00:06.0 ens6: Reset adapter [ 40.736884] igb :00:06.0 ens6: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 46.048136] igb :00:06.0 ens6: Reset adapter [ 50.720706] igb :00:06.0 ens6: igb: ens6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 55.776125] igb :00:06.0 ens6: Reset adapter I'm not having any problems on other distros, and I'm not sure what can be causing hits. Any ideas how to get the netowrk on? I'm using Asus Z10PED16 WS and it's built in network interface. Thanks, X4lldux -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAM%3Dat3KzpXyxcGCu_c5SFTO-U9yubyomyMFe2Ex9yXKdtWd88Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
