On 8/26/2014 at 1:02 PM, "Brent Cook" <bust...@gmail.com> wrote:
>That sounds really familiar. I had a random sparc machine show
>very similar behavior with multiple operating systems. It turned
>out it did not like to play nicely with my gigabit switch and was
>constantly renegotiating link speed. I think it had something to
>do with the power efficient ethernet support.
>
>I bought a new switch, and everything worked properly.
>
I did the initial install as a PXE boot from another computer,
I was busy doing something else at the time but I remember
thinking it was taking a really long time to tftp bsd.rd
(this was via a crossover cable). Because of that I'm hesitant
to believe it's related to my networking gear but perhaps
something is borked with the power settings.
After reading jsg's "Driver Architecture and Implementation in OpenBSD"
I ran the following commands while ftping a large file:
$ netstat -i
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Colls
re0 1500 <Link> 00:21:cc:50:2e:32 7513 0 4637 0 0
re0 1500 10.0.0/24 10.0.0.48 7513 0 4637 0 0
... 10 seconds go by ...
re0 1500 <Link> 00:21:cc:50:2e:32 7711 0 4780 0 0
re0 1500 10.0.0/24 10.0.0.48 7711 0 4780 0 0
... 10 seconds go by ...
re0 1500 <Link> 00:21:cc:50:2e:32 7910 0 4928 0 0
re0 1500 10.0.0/24 10.0.0.48 7910 0 4928 0 0
... 10 seconds go by ...
re0 1500 <Link> 00:21:cc:50:2e:32 8110 0 5084 0 0
re0 1500 10.0.0/24 10.0.0.48 8110 0 5084 0 0
$ netstat -m
93 mbufs in use:
84 mbufs allocated to data
4 mbufs allocated to packet headers
5 mbufs allocated to socket names and addresses
17/48/6144 mbuf 2048 byte clusters in use (current/peak/max)
64/72/6144 mbuf 4096 byte clusters in use (current/peak/max)
0/8/6144 mbuf 8192 byte clusters in use (current/peak/max)
0/8/6144 mbuf 9216 byte clusters in use (current/peak/max)
0/8/6144 mbuf 12288 byte clusters in use (current/peak/max)
0/8/6144 mbuf 16384 byte clusters in use (current/peak/max)
0/8/6144 mbuf 65536 byte clusters in use (current/peak/max)
596 Kbytes allocated to network (52% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
$ sysstat vm (wasn't able to capture the output very cleanly)
... 259 interrupts, 200 clock, 8 ipi, 49 re0 and 2 ahci0
I don't see anything there that appears to be out of order...
-Chester
"See? Kids love pizza, and they love squalor." - James Madison
