Re: ixl and BOOTP
On 2015-5-20, at 17:42, Ryan Stone wrote: > Oh, I bet that you have a bunch of CPUs and ixl is consuming all of your > interrupt vectors. Does setting this tunable fix the issue? > > hw.ixl.max_queues=1 Yeah, this box has 40 cores, but unfortunately that tunable doesn't change things in terms of BOOTP (I do see 2 vectors assigned not instead of 41 though). Lars signature.asc Description: Message signed with OpenPGP using GPGMail
Re: ixl and BOOTP
Oh, I bet that you have a bunch of CPUs and ixl is consuming all of your interrupt vectors. Does setting this tunable fix the issue? hw.ixl.max_queues=1 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ixl and BOOTP
On 2015-5-18, at 19:22, Ryan Stone wrote: > Hm, I'm unable to reproduce this on the latest -CURRENT (r283059). My > hardware is a little different from yours -- my CPU is a Haswell Xeon, and I > have only 1 igb port and no ixgbe. Also, I was just booting GENERIC. I > didn't have Xen or anything running. Happens also without Xen. I will dig a bit further. Thanks for testing! Lars signature.asc Description: Message signed with OpenPGP using GPGMail
Re: ixl and BOOTP
Hm, I'm unable to reproduce this on the latest -CURRENT (r283059). My hardware is a little different from yours -- my CPU is a Haswell Xeon, and I have only 1 igb port and no ixgbe. Also, I was just booting GENERIC. I didn't have Xen or anything running. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ixl and BOOTP
On Mon, May 18, 2015 at 12:30 PM, Slawa Olhovchenkov wrote: > On Mon, May 18, 2015 at 02:42:51PM +, Eggert, Lars wrote: > > > > > Legacy mode, and it hangs in the kernel. > > > > Without if_ixl in loader.conf, it does the usual BOOTP logic: > ^^^ ^^ > > Sending DHCP Discover packet from interface ix0 (90:e2:ba:77:d4:9c) > ^^ > > Sending DHCP Discover packet from interface ix1 (90:e2:ba:77:d4:9d) > ^^ > how this is posible? > > ix0 interfaces are created by the ixgbe driver, not ixl. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ixl and BOOTP
On Mon, May 18, 2015 at 02:42:51PM +, Eggert, Lars wrote: > > Legacy mode, and it hangs in the kernel. > > Without if_ixl in loader.conf, it does the usual BOOTP logic: ^^^ ^^ > Sending DHCP Discover packet from interface ix0 (90:e2:ba:77:d4:9c) ^^ > Sending DHCP Discover packet from interface ix1 (90:e2:ba:77:d4:9d) ^^ how this is posible? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ixl and BOOTP
On 2015-5-18, at 16:08, Ryan Stone wrote: > This is very strange. I have successfully netbooted -CURRENT in a very > similar environment (ixl compiled into kernel and booting over igb). I > can't remember when the last time I did this but it was probably within the > last couple of weeks. I routinely netboot an 8.2 derivative in this kind > of environment and I've never seen this kind of problem. It used to work here, too. Something recently must have broken this. > Could it be related to the size of the kernel, and not ixl specifically? I don't know. Why would the size of the kernel matter? > Also, do you have any indication as to where the hang happens? Is it still > in the BIOS, or in pxeloader, or in the kernel itself? Are you booting in > legacy mode or EFI? Legacy mode, and it hangs in the kernel. Without if_ixl in loader.conf, it does the usual BOOTP logic: ses0 at ahciem0 bus 0 scbus7 target 0 lun 0 ses0: SEMB S-E-S 2.00 device ses0: SEMB SES Device ada0 at ahcich0 bus 0 scbus1 target 0 lun 0 ada0: ACS-2 ATA SATA 3.x device ada0: Serial Number CVCV3102050X180EGN ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 171705MB (351651888 512 byte sectors: 16H 63S/T 16383C) ada0: quirks=0x1<4K> ada0: Previously was known as ad4 Sending DHCP Discover packet from interface igb0 (00:25:90:9b:73:2e) Sending DHCP Discover packet from interface igb1 (00:25:90:9b:73:2f) Sending DHCP Discover packet from interface ix0 (90:e2:ba:77:d4:9c) Sending DHCP Discover packet from interface ix1 (90:e2:ba:77:d4:9d) uhub1: 2 ports with 2 removable, self powered uhub0: 2 ports with 2 removable, self powered ugen0.2: at usbus0 uhub2: on usbus0 ugen1.2: at usbus1 uhub3: on usbus1 uhub2: 6 ports with 6 removable, self powered uhub3: 8 ports with 8 removable, self powered ugen0.3: at usbus0 ukbd0: on usbus0 ums0: on usbus0 ums0: 3 buttons and [Z] coordinates ID=0 igb0: link state changed to UP Received DHCP Offer packet on igb0 from 192.168.0.2 (accepted) (no root path) (boot_file) Received DHCP Offer packet on igb0 from 192.168.0.2 (ignored) (no root path) (boot_file) Received DHCP Offer packet on igb0 from 192.168.0.2 (ignored) (no root path) (boot_file) Sending DHCP Request packet from interface igb0 (00:25:90:9b:73:2e) Received DHCP Ack packet on igb0 from 192.168.0.2 (accepted) (got root path) DHCP timeout for interface igb1 DHCP timeout for interface ix0 DHCP timeout for interface ix1 Wired loader interface (IP 192.168.11.1) is igb0 igb0 at 192.168.11.1 server 192.168.0.2 boot file /pxe/pxelinux.0 subnet mask 255.255.0.0 router 192.168.0.2 rootfs 192.168.0.10:/home/elars/dst hostname phobos2 Adjusted interface igb0 Shutdown interface igb1 Shutdown interface ix0 Shutdown interface ix1 ... And then later on mount the rootfs correctly: Trying to mount root from nfs: []... NFS ROOT: 192.168.0.10:/home/elars/dst Interface igb0 IP-Address 192.168.11.1 Broadcast 192.168.255.255 Setting hostuuid: ----0025909b732e. Setting hostid: 0xe85d6456. ... If I enable if_ixl in loader.conf, I don't see any "Sending DHCP Discover packet" messages in the log at all, and consequently the NFS mount fails. See the attached diff; on the left is a boot without if_ixl, and on the right, with if_ixl. Lars ok nok B2 B2 __ _ _ __ _ _ | | | _ \ / | __ \ | | | _ \ / | __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | | | | | | __/ __/| |_) |) | |__| | | | | | | __/ __/| |_) |) | |__| | | | | | | | || | | | | | | | | | || | | | Xen 4.6-unstabled.ko size 0x2c00 at 0x10620` ` /boot/kernel/cc_htcp.ko size 0x2f90 at 0x109e ` (XEN) Xen version 4.6-unstable (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 4.7.4) debug=y Mon May 18 14:50:17 CEST 2015ko size 0x30d0 at 0x1068000 .--` /y:` +. /boot/kernel/cc_vegas.ko size 0x30d0 at 0x10a1000.---...--.``` -/ (XEN) Latest ChangeSet: | yo`:. :o `+- Booting...el/cc_hd.ko size 0x2c00 at 0x109b000o .--` /y:` +. (XEN) Bootloader: FreeBSD Loader | y/ -/` -o/ Xen 4.6-unstable | yo`:. :o `+- (XEN) Command line: dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com1. (XEN) Xen version 4.6-unstable (r...@netapp.com) (gcc47 (FreeBSD Ports Collection) 4.7.4) debug=y Mon May 18 14:50:17 CEST 2015ser | .- ::/sy+:. (XEN) Video information:r prompt | / `-- / (XEN) Latest ChangeSet: r p | / `-- / (XEN) VGA is text mode 80x25, font 8x16 | `: :` (XEN) Bootloader: FreeBSD Loader | `: :` (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds :` (XEN) Command line: dom0_mem=4096M dom0pvh=1 com1=115200,8n1 console=com1:` (XEN) EDID info not retrieved because no DDC retrieval method detected / (XEN) Video information: | / / (XEN) Disc informat
Re: ixl and BOOTP
On Mon, May 18, 2015 at 10:08 AM, Ryan Stone wrote: > I can't remember when the last time I did this but it was probably within > the last couple of weeks. > Pardon me, I meant months, not weeks. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: ixl and BOOTP
On Mon, May 18, 2015 at 8:40 AM, Eggert, Lars wrote: > Hi, > > when I have the ixl driver compiled into my -CURRENT kernel (or loaded as > a module via loader.conf), the boot seems to hang (or silently crash) when > BOOTP starts bringing up interfaces to send out probes. (I'm not netbooting > over an ixl, the boot interface is an igb.) > > What works is building the kernel without the ixl driver and then loading > it manually once the system is up. That way, BOOTP via igb succeeds. > > Any ideas what could be causing this? > > Lars > This is very strange. I have successfully netbooted -CURRENT in a very similar environment (ixl compiled into kernel and booting over igb). I can't remember when the last time I did this but it was probably within the last couple of weeks. I routinely netboot an 8.2 derivative in this kind of environment and I've never seen this kind of problem. Could it be related to the size of the kernel, and not ixl specifically? Also, do you have any indication as to where the hang happens? Is it still in the BIOS, or in pxeloader, or in the kernel itself? Are you booting in legacy mode or EFI? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
ixl and BOOTP
Hi, when I have the ixl driver compiled into my -CURRENT kernel (or loaded as a module via loader.conf), the boot seems to hang (or silently crash) when BOOTP starts bringing up interfaces to send out probes. (I'm not netbooting over an ixl, the boot interface is an igb.) What works is building the kernel without the ixl driver and then loading it manually once the system is up. That way, BOOTP via igb succeeds. Any ideas what could be causing this? Lars signature.asc Description: Message signed with OpenPGP using GPGMail
