Re: [CFT] alc(4) QAC AR816x/AR817x ethernet controller support
On Wed, Oct 01, 2014 at 10:36:37AM +0900, Yonghyeon PYUN wrote: > On Tue, Sep 30, 2014 at 10:57:41AM +0900, Yonghyeon PYUN wrote: > > Hi, > > I've added support for QAC AR816x/AR817x ethernet controllers. It > > passed my limited testing and I need more testers. You can find > > patches from the following URLs. > > > > http://people.freebsd.org/~yongari/alc/pci.quirk.diff > > and > > http://people.freebsd.org/~yongari/alc/alc.diff.20140930 > > > > pci.qurik.diff is to workaround silicon bug of AR816x. Without it > > MSI/MSIX interrupt wouldn't work. If you just want to use > > legacy INTx interrupt you don't have to apply it but you have to > > tell alc(4) not to use MSI/MSIX interrupt with tunables( > > hw.alc.msi.disable and hw.alc.msix_disable). > > > > alc.diff.20140930 will add support for AR8161/AR8162/AR8171/AR8172 > > and E2200 controllers. It supports all hardware features except > > RSS. If you have any QAC AR816x/AR817x or old AR813x/AR815x > > controllers please test and report how the diff works for you. > > Thanks. > > http://people.freebsd.org/~yongari/alc/pci.quirk.diff > http://people.freebsd.org/~yongari/alc/alc.diff.20141001 > > Patch updated to address link establishment issue. http://people.freebsd.org/~yongari/alc/alc.diff.20141002 Patch updated again to correct wrong lock assertion. ___ 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: pkg/ports system terribly messed up?
On Wednesday, October 01, 2014 7:48:08 AM Rainer Hurling wrote: > Am 01.10.2014 um 05:44 schrieb Chuck Burns: > > On Tuesday, September 30, 2014 8:13:01 AM O. Hartmann wrote: > >> Hello. > >> > >> I just made the last update of the ports yesterday (I use portmaster -da > >> performing this task) and obviously or superficially everything went all > >> right. > > > > > > > > It's portmaster actually. While it -usually- works great, I've noticed > > that occassionally it loops like that. > > > > kill the script, upgrade the port that is looping. > > Because it seems that I have the same problem as Oliver: What script you > are talking about? > > > That usually fixes it. portmaster is just a (not-so-)simple shell script. Kill portmaster (CTRL-C a few times) then build the offending port with "make && make deinstall reinstall clean" -- Chuck ___ 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: pkg/ports system terribly messed up?
On Mon, Sep 29, 2014 at 11:13 PM, O. Hartmann wrote: > > Hello. > > I just made the last update of the ports yesterday (I use portmaster -da > performing this > task) and obviously or superficially everything went all right. > > I'm running on the boxes in question most recent CURRENT. > > On one system, a subsequent start of updating ports starts to freak out when > updateing > lang/gcc: it loops over and over on some ports already updated, especially > devel/binutils, but the port looping on isn't specific and varies. > > On every CURRENT box I tried this morning to update the ports again, I find > this > frsutrating message (depends on installation, but it seems in principal the > same, only > the affected ports in dependency chain varies): Are you using portmaster? If so, it might be fallout from r272282. Cheers, ___ 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: What do you use for kernel debugging?
On 1 October 2014 03:12, Hans Petter Selasky wrote: > On 10/01/14 07:03, Adrian Chadd wrote: >> >> There's also something for XHCI. >> >> Please please write it for freebsd. :) >> >> > > Hi, > > The FreeBSD bootloader can run a regular USB stack which connects to the > XHCI/EHCI and any supported serial adapter for example. What is currently > missing is some PCI pieces to attach the drivers. You don't need the USB > debug port to get keyboard/console input. We actually _want_ the debug port support. The EHCI/XHCI debugging stuff is separate from the whole normal USB stack and is really designed for lower level debugging - ie, when everything is actually busted. Think of it as being the polled conduit for doing remote kgdb and (hopefully, with the XHCI stuff) remote memory inspection when things go off the deep end. -a ___ 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: [PATCH] Fix OACTIVE for an(4)
Hi,
On 1 October 2014 07:14, John Baldwin wrote:
> This small patch correctly sets OACTIVE when an(4) gets backed up. Right now
> I believe it will never set the flag. It is only an optimization, it should
> not affect correctness.
>
> Index: an/if_an.c
> ===
> --- an/if_an.c (revision 270968)
> +++ an/if_an.c (working copy)
> @@ -2906,11 +2906,11 @@
> CSR_WRITE_2(sc, AN_INT_EN(sc->mpi350), AN_INTRS(sc->mpi350));
> }
>
> - if (m0 != NULL)
> + if (sc->an_rdata.an_tx_prod != idx) {
> ifp->if_drv_flags |= IFF_DRV_OACTIVE;
> + sc->an_rdata.an_tx_prod = idx;
> + }
>
> - sc->an_rdata.an_tx_prod = idx;
> -
> return;
> }
I haven't looked at the rest of the driver; is everything else around
OACTIVE locked correctly and consistently?
There's no single-entry into if_start(). It can be called from
multiple paths at the same time.
-a
___
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: Intel SoC's
On 1 October 2014 14:12, John-Mark Gurney wrote: > > Just install FreeBSD on them? If you can't boot from USB, it isn't > hard to build and install a new dist on an SD card or other > media to boot from.. As far as I know Galileo only boots from UEFI and we don't yet have i386 UEFI boot bits. ___ 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: Intel SoC's
Larry Rosenman wrote this message on Sun, Sep 21, 2014 at 21:13 -0500: > I got 2 Intel SoC's at the Intel IOT Hackathon here in Austin this > weekend. > > They are both I586/Pentium processors, with some other stuff hanging > out. They currently run Yactoh Linux. > > I'm wondering how hard it would be to get FreeBSD up on them > > They are the Galileo Gen 2, and Edison boards. > > Any ideas on how/where to start? Just install FreeBSD on them? If you can't boot from USB, it isn't hard to build and install a new dist on an SD card or other media to boot from.. I recently ran up FreeBSD on an old K6/200, so close to same era, and it just worked... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ 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: zpool frag
Allan Jude wrote this message on Sun, Sep 21, 2014 at 11:06 -0400: > On 2014-09-21 04:57, Beeblebrox wrote: > > FRAG means fragmentation, right? Zpool fragmentation? That's news to me. If > > this is real how do I fix it? > > > > NAME SIZE ALLOC FREE FRAG EXPANDSZCAP DEDUP HEALTH ALTROOT > > pool1 75.5G 53.7G 21.8G60% -71% 1.00x ONLINE - > > pool2 48.8G 26.2G 22.6G68% -53% 1.00x ONLINE - > > pool3 204G 177G 27.0G53% -86% 1.11x ONLINE - > > > > Regards. > > > > > > > > - > > FreeBSD-11-current_amd64_root-on-zfs_RadeonKMS > > -- > > View this message in context: > > http://freebsd.1045724.n5.nabble.com/zpool-frag-tp5950788.html > > Sent from the freebsd-current mailing list archive at Nabble.com. > > ___ > > 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" > > > > It is not something you 'fix', it is just a metric to help you > understand the performance of your pool. The higher the fragmentation, > the longer it might take to allocate new space, and obviously you will > have more random seek time while reading from the pool. > > As Steven mentions, there is no defragmentation tool for ZFS. You can > zfs send/recv or backup/restore the pool if you have a strong enough > reason to want to get the fragmentation number down. > > It is a fairly natural side effect of a copy-on-write file system. > > Note: the % is not the % fragmented, IIRC, it is the percentage of the > free blocks that are less that a specific size. I forget what that size is. Can we get this documented in the zpool man page? I assume that the FRAG is the same as: fragmentation The amount of fragmentation in the pool. and that description is woefully lacking.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ 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"
[PATCH] Fix OACTIVE for an(4)
This small patch correctly sets OACTIVE when an(4) gets backed up. Right now
I believe it will never set the flag. It is only an optimization, it should
not affect correctness.
Index: an/if_an.c
===
--- an/if_an.c (revision 270968)
+++ an/if_an.c (working copy)
@@ -2906,11 +2906,11 @@
CSR_WRITE_2(sc, AN_INT_EN(sc->mpi350), AN_INTRS(sc->mpi350));
}
- if (m0 != NULL)
+ if (sc->an_rdata.an_tx_prod != idx) {
ifp->if_drv_flags |= IFF_DRV_OACTIVE;
+ sc->an_rdata.an_tx_prod = idx;
+ }
- sc->an_rdata.an_tx_prod = idx;
-
return;
}
--
John Baldwin
___
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: pkg/ports system terribly messed up?
Am 01.10.2014 um 05:44 schrieb Chuck Burns: On Tuesday, September 30, 2014 8:13:01 AM O. Hartmann wrote: Hello. I just made the last update of the ports yesterday (I use portmaster -da performing this task) and obviously or superficially everything went all right. It's portmaster actually. While it -usually- works great, I've noticed that occassionally it loops like that. kill the script, upgrade the port that is looping. Because it seems that I have the same problem as Oliver: What script you are talking about? That usually fixes it. ___ 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: What do you use for kernel debugging?
On 1 Oct 2014, at 14:33, Adrian Chadd wrote: > There's also something for XHCI. So I see.. Section 7.6 in here has details.. http://www.intel.com.au/content/dam/www/public/us/en/documents/technical-specifications/extensible-host-controler-interface-usb-xhci.pdf Interestingly unlike the EHCI version it does not require hardware between the debugger and debugee, only a special cable. (see http://msdn.microsoft.com/en-us/library/windows/hardware/hh439372(v=vs.85).aspx) A quick search shows the cable is pretty cheap ($15 for a short one) > Please please write it for freebsd. :) Not sure I have the cycles :( > > -a > > > On 30 September 2014 21:45, O'Connor, Daniel wrote: >> >> On 1 Oct 2014, at 0:14, Julian Elischer wrote: >>> Unfortunately you can't use a USB serial as it requires the USB stack >>> be working before it can be used.. >>> similar with ethernet connected debugging which requires that the >>> driver for the ethernet hardware support it. >>> (which why we don't have it in the tree though it has been done >>> several times in the past). >> >> There IS a USB debug standard, Linux has some code to support it. >> >> I am not sure what percentage of hardware has it hooked up though (the host >> controller has a designated debug port but it could physically be anything). >> >> http://www.coreboot.org/EHCI_Debug_Port >> >> The hardware is bit more expensive than a null modem or firewire cable >> though :( >> >> Regards, >>Daniel O’Connor >> >> Senior Software Engineer >> Isilon Platforms Team >> >> >> >> ___ >> 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" Regards, Daniel O’Connor Senior Software Engineer Isilon Platforms Team ___ 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: What do you use for kernel debugging?
On 10/01/14 07:03, Adrian Chadd wrote: There's also something for XHCI. Please please write it for freebsd. :) Hi, The FreeBSD bootloader can run a regular USB stack which connects to the XHCI/EHCI and any supported serial adapter for example. What is currently missing is some PCI pieces to attach the drivers. You don't need the USB debug port to get keyboard/console input. --HPS ___ 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"
