10:52:31 <Woodstock> assertion failed: lso_max > 0 (0x0 > 0x0), file: ../../common/inet/tcp/tcp.c, line: 3364
10:52:48 <Woodstock> has anyone else been getting this recently?
11:07:28 <tsoome> havent seen, sorry.
15:08:27 <rzezeski> Woodstock: That's a first for me. IPv4 or 6? underlying link?
15:09:21 <jbk> i see LSO and I shiver having dealt with it in i40e
15:09:38 <jbk> (though that's mostly intel's fault)
15:11:26 <jbk> which reminds me... I need to see if I ever upstreamed the bits for jumbo frames+LSO for i40e
15:12:34 <jbk> (it limits the size of a DMA buffer to <= 4k and has the card do more segmentation/scatter gather so adding a vnic after the system is running doesn't take the upwards of 30 minutes to complete)
15:18:35 <jbk> we've been running it for a couple of years and haven't had any problems since.. and I know I gave a copy to Dan, not sure how much he's been able to do with it
16:21:45 <danmcd> Not much jbk, and someone else is asking for a common-code update because honestly, we're behind on it.
16:22:09 <Woodstock> rzezeski: ipv6, i presume
16:22:12 <Woodstock> rzezeski: on ixgbe
16:23:42 <danmcd> Odd.
16:23:58 <danmcd> A quick follow-the-bouncing-values and 
16:23:59 <danmcd> usr/src/uts/common/io/ixgbe/ixgbe_gld.c:                        cap_lso->lso_basic_tcp_ipv6.lso_max = IXGBE_LSO_MAXLEN; 
16:24:05 <danmcd> I wonder if that's not getting set?!
16:24:42 <danmcd>                 if (ixgbe->lso_enable) { 
16:24:55 <danmcd> THat's what sets the other line above.  That percolates up.
16:25:17 <Woodstock> i'm bisecting it, i should be able to point to a changeset causing it really soon
16:25:50 <danmcd> Oh... it's something new?  Ping me for review, please.
16:26:22 <danmcd> I need to see if FiOS has removed their heads from their rear-ends about co-existence of static-IPv4 and IPv6 co-existing on their business class.
16:26:28 <Woodstock> not exactly new, but it must be something recent
16:26:43 <danmcd> (Also an opportunity to bring > GigE to my-house aka. kebe.com )
16:26:51 <jbk> at least you get static IPv4 :P
16:27:05 <jbk> i have CGN for IPv4 (but seem to have a static-ish at least IPv6)
16:27:06 <danmcd> Sorry for whining.
16:27:38 <jbk> and periodically, it seems like it loses state for long-running TCP connections
16:27:53 <danmcd> Lily Tomlin's Ernestine-from-The-Phone-Company enters my head whenever I think of VZ, AT&T...
16:28:11 <danmcd> NAT LOSING STATE?  I'm SHOCKED.
16:28:26 <jbk> this is the local power co-op that's run fiber along all the power lines
16:28:37 <jbk> but being small, I'm guessing they can't get many public IPv4 IPs
16:34:35 <AmyMalik> yeah, probably not
16:40:58 <jbk> just need more things to adopt IPv6 :P
16:41:08 <jbk> (including work's VPN)
16:52:29 <AmyMalik> would that IPv4 died outside of retrocomputing already
16:52:55 <ENOMAD> All of the networks I'm responsible for have static IPv6 configurations.
16:53:09 <ENOMAD> I wish I could say that about the networks I was tangentially responsible for. <sigh>
17:43:58 <jbk> hrm.. we don't really have a standard way of 'inventoring' things... e.g. gettign things like serial#s of components, do we?
17:49:19 <Woodstock> if it's in fmtopo, then that's the standard way, I guess :)
17:58:00 <jbk> yeah, but for like PCI devices, there's no standard way (AFAIK), so you'd need a driver specific topo module
17:58:36 <jbk> (i wonder if that was part of what libfru was meant to help with on sparc, but since it's almost completely undocumented, it's hard to know if there might still be bits that are useful outside of sparc or not)
17:58:51 <jbk> or could be useful w/ some work
18:32:39 <jacuzzibob> Hello lovely Illumos people! Does someone know why physmem and pagestotal differ, or point me in the right direction? The mdb output suggests it's the other way around, which seems odd to me. Keep in mind: My knowledge of operating system kernels is quite limited.
18:32:41 <jacuzzibob> [root@host01 ~]# kstat -n system_pages -p | grep -E "physmem|pagestotal"
18:32:42 <jacuzzibob> unix:0:system_pages:pagestotal 33513938
18:32:44 <jacuzzibob> unix:0:system_pages:physmem 33513939
18:32:45 <jacuzzibob> [root@host01 ~]# echo ::memstat | mdb -k | grep -E "Total|Physical"
18:32:47 <jacuzzibob> Total 33513939 130913
18:32:48 <jacuzzibob> Physical 33513938 130913
19:01:11 <sommerfeld> jacuzzibob: if you look at the mdb source, you'll see that it (confusingly) prints out the kernel's total_pages as "Physical", and physmem as 'Total'.
19:02:25 <jacuzzibob> Thank you!
19:03:14 <sommerfeld> it's not clear to me why they differ by one page; there's a comment in mdb's memory.c about "if physmem != total_pages" but that appears to not be relevant on x86
19:06:22 <tsoome> off by one bug?:)
19:07:57 <jbk> one of the three hardest problems in CS (along with naming)
19:07:59 <jbk> :)
19:08:02 <jacuzzibob> :D
20:04:17 <richlowe> alanc: I had mentioned somewhere during the break about pkg.summary v. pkg.description and what the right thing to do if they both basically matched was.  I think you know the old answer?
20:04:53 <richlowe> I have the memory that only one should exist if they're both basically the same? but I guess that wasn't it
20:05:29 <richlowe> sommerfeld: if you're in that mdb stuff, and rudely, could you confirm for me that "::report_maps" doesn't even nearly work?
20:05:42 <richlowe> sommerfeld: the code seems clear it expects miracles, but I haven't been in a position to file a bug
21:19:49 <sommerfeld> richlowe: only to the extent that I looked at files that turned up on a "git grep" of pagestotal, physmem, and total_pages
21:23:00 <richlowe> ah, it'll stay on my todo list until it's todone then
21:24:38 <sommerfeld> (if I'm reading it correctly it intends to walk all page tables looking for mappings to the requested page number)
21:26:06 <richlowe> it does, but then it just does something else entirely
21:26:20 <richlowe> reading the code, at least
21:28:09 <richlowe> I was convinced from code reading, but then I saw they mention it -- with examples -- in solaris internals 2nd ed.
21:34:43 <alanc> https://github.com/oracle/solaris-ips/blob/master/doc/tags-and-attributes.txt#L68 - summary is supposed to be a few words, description up to a paragraph - if they're both the same and just a few words, I'd probably drop the description - but if they're much longer, I'd leave the description and replace the summary with something short
21:39:09 <richlowe> I forgot ips/doc contained things that were still relevant :\