Re: When will we can use ZFS v24?
On Tue, Apr 6, 2010 at 10:26 PM, lhmwzy wrote: > I found the zfs on FreeBSD is still V13 > When will we can use ZFS v24? I believe that patches for ZFS v22 is being worked on atm. Sam Fourman Jr. Fourman Networks ___ 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: When will we can use ZFS v24?
> ZFS is still currently in heavy development so it might happen. Having siad > that it looks like oracle have totally buggered it up for everyone with > their retroactive licenses. I hope the CDL was tight enough that stuff wont > have to get pulled from freebsd is that even possible with CDDL? Sam Fourman Jr. Fourman Networks ___ 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: ports and PBIs
On Fri, Apr 9, 2010 at 8:31 PM, Julian Elischer wrote: > sorry for the cross-post.. > > Last night at the Bay Area FreeBSD Users Group meeting we had > a discussion about ports, and what is good about them and what > is bad about them. This has been a topic of discussion quite a > bit recently and we were looking for a solution that would > allow us to keep the good parts of the current ports system > but would allow us to give a better user experience for non > guru users. > > The scheme we came up with involves a merging of the > ports tree and the PBI system, developed for PC-BSD. > > Basically, the addition of a makepbi keyword in the .mk > files to allow the automatic generation of PBIs for 'simple' > ports such as 'cowsay' (the canonical simple app). > More complicated apps would need manual work in Makefile or > in a separate pbi-recipe file, but once the support was done > we could proceed one port at a time. Not all ports make sense > in a PBI format. (e.g. libraries etc. may not) I for one support this Idea, and at a BoF FreeBSD Desktop session at BSDCan 2008 one of my suggestions was to have FreeBSD "bless PBI's" I think this is good For PC-BSD. and in return it is GREAT for FreeBSD, as it will widen the user base and hopefully attract a few more good developers. keep this discussion going, because there isn't mush of a downside so far as I can see. Sam Fourman Jr. > One issue that was raised is the increase of storage > overhead when using PBI packages as they include a copy of > all required libraries and resources, which means that one would > very quickly get duplicate copies of things. > > Our suggestions include the ability of the PBI management software > to resolve and (using hard links) eliminate duplicate items. > This is not as easy as it sounds but can be achieved using a > special variant of 'objcopy' (at least that is our theory). > > The aim is to make all apps installed on a system much more > resilient to dependency problems. > > In addition there was discussion on how builds need to be doable as non-root > uids sometimes, and that users on a system should be > able to install packages (PBIs) as thie selves to get local > versions of apps for themselves. > > Alfred Perlstein , Matt at ix systems Kris (Mr PBI), some > others and I, felt that these ideas seemed to make some sense > and so I put them here for comment. > > > Julian > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ 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: ports and PBIs
On Fri, Apr 9, 2010 at 10:11 PM, Adam Vande More wrote: > On Fri, Apr 9, 2010 at 8:31 PM, Julian Elischer wrote: > >> >> Alfred Perlstein , Matt at ix systems Kris (Mr PBI), some >> others and I, felt that these ideas seemed to make some sense >> and so I put them here for comment. >> >> > FWIW, when I see these discussions I'm always left wondering what's the bad > part? I do think there are problems, but there doesn't seem to be a clear > defined set of what is wrong. IMO, there should be a defined set of goals > to judge possible implementations against. Let me start by saying FreeBSD ports is by far the best system I have used to date. but as good as it is, there is room for improvement. Being a FreeBSD user now for many years, one thing I think would be nice is: being able to have easier access to development ports( Masked ports kinda like Gentoo). right now is a GREAT example, currently there are new Gnome ,KDE and Xorg. these are all MAJOR ports,dependencies run deeper and deeper with every release. there can never be enough testing...but they all exist in random subversion servers around the web... I would very much like to help test these Major ports, but installing them is a pain. there should be some sort of overlay system in place, so I can just build the development ports after agreeing to a few well placed warnings of course. and Well if I hose my system all to hell.. well then I could just click on a bunch of PBI's and I am back in business... better still, make the development ports a PBI, I am just thinking out loud here,but that may work, toughts? one could say I could use merge scripts like marcusmerge for example, or use Virtualbox... but for large ports like Xorg and gnome or KDE, virtualbox doesn't cut it yet... thinks like Nvidia Video cards, multiple monitors, USB devices, and whatnot do not work on virtual box.. PBI's for development ports, with all the dependencies, wrapped in one package. solution? well let all the developers develop working ports in progress in one place, give users like me a way to track these changes and install and test them... I think FreeBSD becomes a better place for it. Sam Fourman Jr. Fourman Networks ___ 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: ports and PBIs
On Sat, Apr 10, 2010 at 2:20 AM, Garrett Cooper wrote: > On Fri, Apr 9, 2010 at 11:28 PM, Sam Fourman Jr. wrote: >> On Fri, Apr 9, 2010 at 10:11 PM, Adam Vande More >> wrote: >>> On Fri, Apr 9, 2010 at 8:31 PM, Julian Elischer wrote: >>> >>>> >>>> Alfred Perlstein , Matt at ix systems Kris (Mr PBI), some >>>> others and I, felt that these ideas seemed to make some sense >>>> and so I put them here for comment. >>>> >>>> >>> FWIW, when I see these discussions I'm always left wondering what's the bad >>> part? I do think there are problems, but there doesn't seem to be a clear >>> defined set of what is wrong. IMO, there should be a defined set of goals >>> to judge possible implementations against. >> >> >> Let me start by saying FreeBSD ports is by far the best system I have >> used to date. >> but as good as it is, there is room for improvement. >> >> Being a FreeBSD user now for many years, one thing I think would be nice is: >> being able to have easier access to development ports( Masked ports >> kinda like Gentoo). > > Masking ports and packages in general introduces all sorts of fun new > complexity for end users as well as maintainers. The last time I used > Gentoo (which was only a matter of months ago), a lot portage packages > were still masked even though they've been stable for months, years, > etc. This is very annoying for me as an end-user because bug blah > could be fixed in a later release but in order to unmask the pieces > for version blah, I had to unmask 10~15 other `unstable packages', > which greatly increased the chance of instability on my system (this > was particularly the case back several years ago, but Gentoo has > become more conservative over the years, and appears to be approaching > some level of equilibrium with Fedora, Ubuntu, etc in terms of > releases and package versioning). I wasn't suggesting that the current way Gentoo did Masking was the correct way, in fact you have valid points that I agree with and I used Gentoo last Week :) What I like is that, most of the portage development in done in tree, maybe the real solution is, to just have a development and release ports tree? > >> right now is a GREAT example, currently there are new Gnome ,KDE and Xorg. >> these are all MAJOR ports,dependencies run deeper and deeper with every >> release. >> there can never be enough testing...but they all exist in random >> subversion servers around the web... > > ports isn't going to solve this. Post the Xorg modularization (which > needed to occur anyhow because Xorg and Xfree86 before that was were > monolithic beasts), I personally don't see that change in the amount > of flux on a quarterly cycle, and the number of packages I install > today isn't that much greater than back 6 years ago when I started > using FreeBSD. So, while there might be some claim here to note, I > think it's mostly exaggerated. Again, I agree with you, I just want a easier way to test these large ports. >> I would very much like to help test these Major ports, but installing >> them is a pain. >> there should be some sort of overlay system in place, so I can just >> build the development ports >> after agreeing to a few well placed warnings of course. and Well if I >> hose my system all to hell.. >> well then I could just click on a bunch of PBI's and I am back in business... > > Ok, apart from the interface (click a PBI, and magically you have > packages installed)... how is this really different from binary > packages? Have you tried installing binary packages lately via > pkg_add? If not, I'd give it a shot instead of installing from ports. pkg_add does work, I have done it several times, upon learning about PBI's a few years back I wondered to myself, why not just use packages,and make some sort of GUI to add a icon to the whole ordeal. but now I get the Idea of dependencies,it pleges evey Open source OS, even ubuntu breaks every now and again. >> better still, make the development ports a PBI, I am just thinking out >> loud here,but that may work, toughts? >> >> one could say I could use merge scripts like marcusmerge for example, >> or use Virtualbox... >> but for large ports like Xorg and gnome or KDE, virtualbox doesn't cut it >> yet... >> thinks like Nvidia Video cards, multiple monitors, USB devices, and >> whatnot do not work on virtual box.. >> PBI's for development ports, with all the dependencies, wrapped in one >> package. > > Ok, well here's the thing. Instead of havin
Re: ports and PBIs
On Sat, Apr 10, 2010 at 8:18 AM, wrote: > > > > > On Sat 10/04/10 3:35 AM , Garrett Cooper wrote: > > [...] > >> >> yes but there are still dependency problems if you want to install a >> single >> package and you installed all the previous ones a year ago. >> With PBIs each package is self standing, so you can install one >> and not worry if it requires a different version of some library >> to what you installed last year. > > If I'm understanding you correctly you're saying it's an issue when I do: > > pkg_add A B C > > # 1 year passes > > pkg_add D > > # D depends on A, B, C, of different revisions. pkg_add barfs because > it can't find the applications, etc. > > This is something that's been hashed over a number of times (a few of > which I've participated in in #bsdports). There needs to be a simple > update command which will handle the action of upgrading packages, > because there isn't a proper command that will do so today. > > Unless PBIs are self-contained entities which have their own sets of > dependent utilities and libraries, etc (which you weren't suggesting > in the sentence above), or install into a common location with > versioned directories (which is a pain in the ass and involves a lot > of hardcoded pains dealing with libtool files, libraries, etc -- been > there, done that with Gentoo Linux -- there are hack scripts written > to work around several possible hardcoded version issue, and there are > a handful), AFAIK there's nothing positive and new that PBIs can bring > to the table in this regard that can't be implemented in pkg_install > as-is, other than the point-click-install user-friendly interface. > > > > Incorrect. The difference is in complexity at install-time. Even if you > improve the package manager > > to better resolve and upgrade all related dependencies as a result of doing > a firefox upgrade, the fact > > still remains that just to update one package, you may have to also update a > TON of various packages > > / libraries, any of which may be critical to other applications on your > system. If just a single one of those > > things fails, you can end up breaking a lot of applications on your system > or even your entire desktop. > > PBI system simplifies this process. Updating firefox, since its > self-contained, does NOT run the risk > > of borking anything else on the system. You don't need to work about libpng, > libjpeg, or some other seemingly > > trivial library (to the end user) causing a huge breakage for xorg, or > KDE/Gnome, etc. > > This in my opinion is the fatal flaw of pretty much every open-source system > out there right now. Something both > > windows & mac have recognized and dealt with. We instead try to write more > and more complex package resolvers, > > while failing to address the main issue, that with such a complex chain of > dependencies for something as simple > > as upgrading firefox, it increases the chances exponentially that something > will break and ruin your day / weekend. > > > >>> PBIs only comprise a small set of packages in FreeBSD; if my >>> understanding is correct based on a mirror referenced in pbidir.com, >>> the number is currently under 500~750 PBIs -- this is drastically >>> smaller than the number of binary packages produced by ports on a >>> regular basis for FreeBSD. >>> solution? well let all the developers develop working ports in progress in one place, give users like me a way to track these changes and install and test them... I think FreeBSD becomes a better place for it. >>> >>> Packages are more of the answer IMO, not PBIs. PBIs are merely a >>> different set of contents and different means of delivering those >>> contents, and while I like the idea of point - click - install, I'm >>> not ready to create unnecessary complexity by having libraries rev'ed >>> according to what the maintainer A believes are correct, even though >>> maintainer B set it differently, and I'm not interested in sacrificing >>> disk space for this reason. If I wanted to use a packaging scheme like >>> this, I should be using Mac OSX as my primary operating system. >> >> well no-one is going to make you use PBIs > > Yes, but if I now have to waste more bandwidth and disk space > installing packages, why shouldn't I go to another operating system? > Switching over to PBIs will reel in more desktop and entry-level > sysadmins, etc, but I fear that it will isolate folks in the embedded > market as well as several more seasoned users because of the > implications involved with the extra bandwidth requirement and > footprint. > > This gave me a bit of a chuckle. PBI would not be intended as a replacement > for ports, > rather a utilizing of ports in such a way that we can start building > self-contained, stand-alone > binaries for end-users and those of us who value their time more than a few > MB of disk space. > Considering at every BSD conference it seems that the majority of developers > are running Mac > laptops,
Re: Official request: Please make GNU grep the default
>> BSD grep >> Elapsed time: 47 seconds > > what about optimizing BSD grep instead? I think this is reasonable, leave BSD grep default for a few more weeks, and work on performance enhancements. I agree that changing the default back for a RELEASE is probably a good idea, but the exposure to wider testing while focusing on performance, can't hurt much can it? -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
pxe NFSroot and firefox 3.6
Hello all I am running several FreeBSD 8/9 systems on a nfsroot, and it seems firefox 3.6.9 (sqllite rather) has issues accessing bookmarks, history and other things unless the /var/lib/nfs path exists. firefox 3.6.9 on NFSroot you must: mkdir -p /var/lib/nfs I found details here https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/237970 Since this simple fix works, and firefox is a popular port I was wondering how would we go about making this path exist by default? I dont know much about this, but if several ports need this path then maybe we could have the installworld script add mkdir -p /var/lib/nfs ? or perhaps just have the firefox port add the path? maybe there is yet another way to achieve this... the end goal here is to make this work by default the way it now does on ubuntu / debian comments welcome -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: ATI Radeon HD 3200 / HP Laptop (Using)
On Mon, Sep 27, 2010 at 3:21 AM, Gary Jennejohn wrote: > On Sun, 26 Sep 2010 23:40:22 -0500 > "Michael R. Rusch" wrote: > >> I see that the Radeon HD 3200 needs r600_dri.so >> > > This is installed by /usr/ports/graphics/dri, which has been around since > the beginning of this year. > > See the 20100207 entry about Mesa3D in /usr/ports/UPDATING. >From /usr/ports/UPDATING 20100207: AFFECTS: users of Mesa3D libraries and x11-drivers/xf86-video-nouveau AUTHOR: n...@freebsd.org If you want to use Mesa3D 7.6.1 and libdrm 2.4.17 rather than 7.4.4 and 2.4.12, you must define WITHOUT_NOUVEAU global macro, at least, enabled on graphics/libGL*, graphics/libglut, graphics/dri, graphics/mesa-demos, and graphics/libdrm. And please give up using x11-drivers/xf86-video-nouveau. At this time, I cannot enable latest Mesa3D and libdrm, because they break xf86-video-nouveau. But old (current?) Mesa3D and libdrm do not break any drivers. AMD Radeon HD 2xxx/3xxx/4xxx users: If you use AMD Radeon HD [234]xxx series, please define WITHOUT_NOUVEAU global macro. You can then use OpenGL Hardware Accelerator feature on these series. how would we define define WITHOUT_NOUVEAU on PC-BSD 8.1 it is pre-compiled? what are our options for 3d accelerated radeonHD 3200 Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: -current under Xen
On Sun, Sep 26, 2010 at 11:06 PM, Julian Elischer wrote: > After bruce C gave me the hint of kern.eventtimer.periodic=1, I was able to > boot -current on my vps > at rootbsd.com, but it hangs on reboot.. some time before the unmounts as > the > file systems need to be cleaned on the next successful boot. > Has anyone had any experience with this? > > unfortunately I can't yet tell you the version of Xen in use there. > For what it is worth, I have the same shutdown issues on real hardware using 9 CURRENT eg dell 6450 (old p3 xeon) dell 2650 as well as a white box (below is a partial dmesg) Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #20: Mon Oct 11 07:57:28 CDT 2010 r...@fnfs.puffybsd.com:/usr/obj/usr/src/sys/FNFS amd64 CPU: AMD Phenom(tm) II X4 B50 Processor (3100.28-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x100f42 Family = 10 Model = 4 Stepping = 2 Features=0x178bfbff Features2=0x802009 AMD Features=0xee500800 AMD Features2=0x37ff TSC: P-state invariant real memory = 8589934592 (8192 MB) avail memory = 7986311168 (7616 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: <041410 APIC1753> FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ACPI Warning: Optional field Pm2ControlBlock has zero address or length: 0x/0x1 (20100915/tbfadt-655) ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: <041410 XSDT1753> on motherboard acpi0: Power Button (fixed) acpi0: reservation of fee0, 1000 (3) failed acpi0: reservation of ffb8, 8 (3) failed acpi0: reservation of fec1, 20 (3) failed acpi0: reservation of fed4, 5000 (3) failed acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cff0 (3) failed Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: at device 1.0 on pci0 I think I have a HP machine that wont shut down either -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
nfs zfs lockup
sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100239 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100240 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100241 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100242 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100243 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100244 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100245 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100246 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100247 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100248 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100249 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100250 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100251 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100252 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100253 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100254 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100255 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100256 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100257 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100258 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100259 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100260 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100261 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline 0 100262 kernel zil_cleanmi_switch sleepq_wait _sleep taskqueue_thread_loop fork_exit fork_trampoline -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: nfs zfs lockup
On Mon, Oct 11, 2010 at 3:45 PM, Sam Fourman Jr. wrote: > I believe NFS is upsetting ZFS v15 on FreeBSD current (kernel sources > from today) > this happened while trying to sftp a 4gb file > here is a lockup without nfs even started FNFS# procstat -k 2503 PIDTID COMM TDNAME KSTACK 2503 100340 sftp-server -mi_switch sleepq_catch_signals sleepq_wait_sig _cv_wait_sig seltdwait kern_select select syscallenter syscall Xfast_syscall FNFS# -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Locked up nfsd after avg@ sendfile patch
FNFS# uname -a FreeBSD FNFS.PuffyBSD.Com 9.0-CURRENT FreeBSD 9.0-CURRENT #23: Wed Oct 13 08:07:13 CDT 2010 r...@fnfs.puffybsd.com:/usr/obj/usr/src/sys/FNFS amd64 FNFS# running CURRENT as of - r213742 FNFS# top -PS last pid: 65634; load averages: 3.39, 2.81, 1.62 up 0+01:47:43 10:07:35 322 processes: 6 running, 295 sleeping, 21 waiting CPU 0: 74.8% user, 0.0% nice, 7.5% system, 0.0% interrupt, 17.7% idle CPU 1: 85.4% user, 0.0% nice, 4.3% system, 0.0% interrupt, 10.2% idle CPU 2: 83.1% user, 0.0% nice, 8.7% system, 0.0% interrupt, 8.3% idle CPU 3: 82.3% user, 0.0% nice, 4.7% system, 0.0% interrupt, 13.0% idle Mem: 145M Active, 17M Inact, 6101M Wired, 1352K Cache, 1402M Free Swap: 63G Total, 63G Free PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 11 root 4 171 ki31 0K64K RUN 0 409:24 203.32% idle 0 root 164 -80 0K 2608K - 0 1:54 0.00% kernel 12 root21 -60- 0K 336K WAIT0 0:15 0.00% intr 1081 root 4 440 10052K 1080K zfs 0 0:14 0.00% nfsd 7 root 1 76- 0K16K ccb_sc 2 0:05 0.00% xpt_thrd 4 root 1 -8- 0K16K - 2 0:02 0.00% g_down 3 root 1 -8- 0K16K - 1 0:02 0.00% g_up 18 root 1 44- 0K16K zio->i 1 0:02 0.00% syncer 5 root 6 -8- 0K 128K tx->tx 0 0:01 0.00% zfskern 2485 root 1 440 42480K 4232K select 0 0:01 0.00% sshd 13 root 1 44- 0K16K - 0 0:01 0.00% yarrow 2425 70 1 440 53492K 5584K select 3 0:00 0.00% postgres 2419 70 1 440 60780K 5804K select 2 0:00 0.00% postgres 2426 70 1 440 53492K 5584K select 0 0:00 0.00% postgres 2420 70 1 440 60780K 5788K select 1 0:00 0.00% postgres 2 root 1 -8- 0K16K - 1 0:00 0.00% g_event 14 root28 -64- 0K 448K - 0 0:00 0.00% usb 1916 70 1 440 53492K 5484K select 0 0:00 0.00% postgres 1594 70 1 440 60780K 5736K select 2 0:00 0.00% postgres 65625 root 1 960 26484K 18328K CPU22 0:00 0.00% cc1 44389 root 1 440 7296K 852K select 3 0:00 0.00% make 44471 root 1 450 7296K 1348K select 3 0:00 0.00% make 2857 sfourman 1 440 42480K 4456K select 0 0:00 0.00% sshd 17 root 1 -16- 0K16K vlruwt 2 0:00 0.00% vnlru 2427 70 1 440 53492K 5564K select 0 0:00 0.00% postgres 2421 70 1 440 60780K 5812K select 2 0:00 0.00% postgres 1066 root 1 440 11280K 1924K select 1 0:00 0.00% mountd 2858 sfourman 1 440 25060K 3400K select 1 0:00 0.00% sftp-server 3065 pixi 1 460 8096K 3716K tx->tx 0 0:00 0.00% cvsup 1625 root 1 440 11976K 3356K select 0 0:00 0.00% sendmail 2257 root 1 440 11976K 2900K select 3 0:00 0.00% sendmail 1955 root 1 440 11976K 3096K select 0 0:00 0.00% sendmail 1257 root 1 440 16408K 3392K select 1 0:00 0.00% sendmail FNFS# procstat -k -k 1081 PIDTID COMM TDNAME KSTACK 1081 100284 nfsd nfsd: master mi_switch+0x176 sleepq_wait+0x42 _cv_wait+0x129 zil_commit+0x7a zfs_freebsd_fsync+0xd6 VOP_FSYNC_APV+0x6c nfsvno_fsync+0xb7 nfsrvd_commit+0xe3 nfsrvd_dorpc+0x39d nfssvc_program+0x447 svc_run_internal+0x6e9 svc_run+0x8f nfsrvd_nfsd+0x92 nfssvc_nfsd+0x9b nfssvc+0xb6 syscallenter+0x331 syscall+0x4b Xfast_syscall+0xe2 1081 100291 nfsd nfsd: servicemi_switch+0x176 sleepq_wait+0x42 _cv_wait+0x129 zil_commit+0x7a zfs_freebsd_fsync+0xd6 VOP_FSYNC_APV+0x6c nfsvno_fsync+0xb7 nfsrvd_commit+0xe3 nfsrvd_dorpc+0x39d nfssvc_program+0x447 svc_run_internal+0x6e9 svc_thread_start+0xb fork_exit+0x11b fork_trampoline+0xe 1081 100292 nfsd nfsd: servicemi_switch+0x176 sleepq_wait+0x42 _cv_wait+0x129 zil_commit+0x7a zfs_freebsd_fsync+0xd6 VOP_FSYNC_APV+0x6c nfsvno_fsync+0xb7 nfsrvd_commit+0xe3 nfsrvd_dorpc+0x39d nfssvc_program+0x447 svc_run_internal+0x6e9 svc_thread_start+0xb fork_exit+0x11b fork_trampoline+0xe 1081 100293 nfsd nfsd: servicemi_switch+0x176 sleepq_wait+0x42 __lockmgr_args+0x7a3 vop_stdlock+0x39 VOP_LOCK1_APV+0x52 _vn_lock+0x47 zfs_fhtovp+0x30e nfsvno_fhtovp+0x4f nfsd_fhtovp+0xa6 nfsrvd_dorpc+0x9d0 nfssvc_program+0x447 svc_run_internal+0x6e9 svc_thread_start+0xb fork_exit+0x11b fork_trampoline+0xe FNFS# -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.com ___ freebsd-current@freebsd.org mailing
Re: Locked up nfsd after avg@ sendfile patch
> procstat -kk -a | fgrep zil_commit > > -- > Andriy Gapon > I rebooted... Next time it locks up, I will run that.. it locks up pretty regular, should not be a few hours -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: Locked up nfsd after avg@ sendfile patch
On Wed, Oct 13, 2010 at 10:59 AM, Sam Fourman Jr. wrote: > > procstat -kk -a | fgrep zil_commit >> >> -- >> Andriy Gapon >> > > > > full procstat -kk -a http://www.puffybsd.com/fnfs.txt -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
ath9k
Recently there were changes made to the ath driver on CURRENT does FreeBSD still need these changes? http://marc.info/?l=linux-wireless&m=128746728412954&w=2 I did notice they went in OpenBSD's Tree today -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: calcru: runtime went backwards
On Wed, Nov 3, 2010 at 4:36 AM, Aragon Gouveia wrote: > I recently saw these on a Dell server. It was caused by power saving being > enabled in the BIOS in a mode where the BIOS takes control instead of > handing it off to the OS. Disable power saving or set it such that the OS > has control (and then enable powerd(8) if you like). > > We disabled AMD C1E support in BIOS (it was Enabled) now we have not seen this problem for 2 days now. -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
ACPI panic on boot recent HEAD
Hello list, here is a digital camera pic of a panic that happened while booting yesterdays Source tree http://www.puffybsd.com/IMG_4136.JPG here is a dmesg from a older current http://www.puffybsd.com/amddmesg.txt -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: ACPI panic on boot recent HEAD
On Sun, Nov 7, 2010 at 1:29 PM, Garrett Cooper wrote: > On Sun, Nov 7, 2010 at 10:02 AM, Sam Fourman Jr. wrote: >> Hello list, >> >> here is a digital camera pic of a panic that happened while booting >> yesterdays Source tree >> >> http://www.puffybsd.com/IMG_4136.JPG >> >> >> here is a dmesg from a older current >> http://www.puffybsd.com/amddmesg.txt > > Uh, that looks like geom to me, not acpi... > -Garrett I saw the ACPI warning on top so I blamed ACPI... maybe I was wrong, this stuff is not my strong suit -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: ACPI panic on boot recent HEAD
>> I saw the ACPI warning on top so I blamed ACPI... >> maybe I was wrong, this stuff is not my strong suit > > It's ok :) (one thing to note is that the ACPI warning is present > in both cases)... It would be interesting to note what modules you > load (in particular the geom ones), and what GEOM options you define > in your kernconf, as well as whether or not you built your kernel and > world from scratch. > Thanks! > -Garrett this kernel is GENERIC + Debugging stuff I built CURRENT with RELENG_8, then I installed the kernel and rebooted I still have a RELENG_8 world, if that matters and this is a ZFS boot machine -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: RFC: etcupdate tool in base?
On Thu, Jun 10, 2010 at 1:14 PM, Joel Dahl wrote: > On 10-06-2010 13:46, John Baldwin wrote: >> I've had several folks ask me recently about importing etcupdate >> (http://www.FreeBSD.org/~jhb/etcupdate) into the base system as an alternate >> tool for updating /etc during upgrades. Do folks have any strong objections >> to doing so? More details about how it works and an HTML version of the >> manpage can be found at the URL above. > > +1 for importing it into base. > +1 for importing into base. I would use it. Sam Fourman Jr. http://www.fourmannetworks.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"
Re: [MFC REQUEST] Filename completion in sh(1)
>> -Brandon > > Oh, I see. The diff doesn't include the change(s) to histedit.h > I would be very interested in a diff for FreeBSD 8.1 Sam Fourman Jr. http://www.fourmannetworks.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"
panic with zfs v16 patch
hello list, I just had a panic on a FreeBSD 9.0 built with yesterdays sources. uname -a FreeBSD 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Sat Jun 26 09:14:30 CDT 2010 sfourman@:/usr/obj/usr/src/sys/ZFSv16 amd64 GENERIC kernel with this patch http://people.freebsd.org/~mm/patches/zfs/v16/head-v16-extended.patch i have a ufs2 boot drive with a separate ZFS pool since this was a fresh install of 9-current(specifically to test the v16 ZFS patches) I was doing a zpool import of a 2TB dataset that has ~100 snapshots it was taking over a hour to import, possibly this zfs bug http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6761786 So I decided to build subversion from ports while I waited on zfs import I got the panic in the following pics http://www.puffybsd.com/img_3995.jpg http://www.puffybsd.com/img_3996.jpg -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: panic with zfs v16 patch
> Curious - this panic is UFS softdep-related - possibly from the SUJ work? > > On which file system type is your ports tree? ufs2 -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: panic with zfs v16 patch
On Mon, Jun 28, 2010 at 9:43 AM, Sam Fourman Jr. wrote: >> Curious - this panic is UFS softdep-related - possibly from the SUJ work? >> >> On which file system type is your ports tree? > > ufs2 it seems ivan may be correct, I went and tried to continue the subversion build I received this panic, while downloading a file (I was doing nothing with ZFS at all this time) ===> License check disabled, port has not defined LICENSE ===> Found saved configuration for postgresql-client-8.2.17_1 => postgresql-8.2.17.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/postgresql. => Attempting to fetch from ftp://ftp9.us.postgresql.org/pub/mirrors/postgresql/source/v8.2.17/. postgresql-8.2.17.tar.bz2 52% of 12 MB 855 kBps http://www.puffybsd.com/img_3997.jpg http://www.puffybsd.com/img_3999.jpg any other useful data I can gather? > -- > > Sam Fourman Jr. > Fourman Networks > http://www.fourmannetworks.com > -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: [CFT] ZFS v15 patch (version 3)
On Wed, Jul 7, 2010 at 1:25 PM, Jason J. W. Williams wrote: > If the target is FreeBSD 9 instead of 8.1, why not merge ZFS v19? 15 > really doesn't give any major enhancements over 14 and FreeBSD 9 isn't > coming out any time. > > 19 would give much need log device removal and triple parity RAID-Z. > Both of which are well tested at this point via OpenSolaris. > these are very valid points, but I am not sure that anyone has zfs v19 patches -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: [CFT] ZFS v15 patch (version 3)
2010/7/5 Martin Matuska :
> Dear FreeBSD community,
>
> there has been a ZFS-related discussion at the meetBSD conference in
> Krakow, Poland and we agreed to push ZFS version 15 (and not 16) to
> -CURRENT.
>
> An upgrade to version 16 gives us no valuable features (to be true, no
> features at all besides ability to import v16 pools).
> As ZFS v15 is already being used in the Solaris 10 enterprise world, we
> can consider it well-tested.
>
> The goal is to provide a filesystem compatible with Solaris 10 update 8,
> which may attract new users to FreeBSD.
> Existing users will get the userquota/groupquota features for ZFS and be
> able to import Solaris 10 update 8 pools.
>
> Import was done by walking through the path of bugfixes from Solaris 10,
> including pre-v15 bugfixes and almost all post-v15 bugfixes.
> Few patches are irrelevant to our code (Solaris-specific features) or
> modify the zvol part, these have been left out.
>
> I have prepared a new patch that includes almost all revision numbers
> Solaris 10 has integrated (we have several of the revisions already in
> our tree).
> Patch also includes updated manpages and may be considered as a
> candidate for head.
>
> Link to the patch information file, including all imported revisions,
> bug-ids and reference to Solairis 10 patch numbers:
> http://people.freebsd.org/~mm/patches/zfs/v15/head-v15-v3.html
> http://people.freebsd.org/~mm/patches/zfs/v15/head-v15-v3.txt
>
> Direct link to the patch:
> http://people.freebsd.org/~mm/patches/zfs/v15/head-v15-v3.patch
>
> The patch applies cleanly against head and stable/8.
using head from 3 hours ago, this patch does not apply cleanly
http://people.freebsd.org/~mm/patches/zfs/v15/head-v15-v3-extension.patch
FNFS# cat sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c.rej
***
*** 529,540
if ((flag & (FSYNC | FDSYNC)) && (count == 1))
atomic_dec_32(&zp->z_sync_cnt);
- /*
-* Clean up any locks held by this process on the vp.
-*/
- cleanlocks(vp, ddi_get_pid(), 0);
- cleanshares(vp, ddi_get_pid());
-
if (!zfs_has_ctldir(zp) && zp->z_zfsvfs->z_vscan &&
ZTOV(zp)->v_type == VREG &&
!(zp->z_phys->zp_flags & ZFS_AV_QUARANTINED) &&
--- 535,540
if ((flag & (FSYNC | FDSYNC)) && (count == 1))
atomic_dec_32(&zp->z_sync_cnt);
if (!zfs_has_ctldir(zp) && zp->z_zfsvfs->z_vscan &&
ZTOV(zp)->v_type == VREG &&
!(zp->z_phys->zp_flags & ZFS_AV_QUARANTINED) &&
***
*** 1055,1060
&acl_ids)) != 0)
goto out;
if (zfs_acl_ids_overquota(zfsvfs, &acl_ids)) {
error = EDQUOT;
goto out;
}
--- 1101,1107
&acl_ids)) != 0)
goto out;
if (zfs_acl_ids_overquota(zfsvfs, &acl_ids)) {
+ zfs_acl_ids_free(&acl_ids);
error = EDQUOT;
goto out;
}
***
*** 2208,2213
return (error);
}
if (zfs_acl_ids_overquota(zfsvfs, &acl_ids)) {
zfs_dirent_unlock(dl);
ZFS_EXIT(zfsvfs);
return (EDQUOT);
--- 2243,2249
return (error);
}
if (zfs_acl_ids_overquota(zfsvfs, &acl_ids)) {
+ zfs_acl_ids_free(&acl_ids);
zfs_dirent_unlock(dl);
ZFS_EXIT(zfsvfs);
return (EDQUOT);
***
*** 3373,3382
if (attrzp)
VN_RELE(ZTOV(attrzp));
- if (aclp) {
zfs_acl_free(aclp);
- aclp = NULL;
- }
if (fuidp) {
zfs_fuid_info_free(fuidp);
--- 3412,3419
if (attrzp)
VN_RELE(ZTOV(attrzp));
+ if (aclp)
zfs_acl_free(aclp);
if (fuidp) {
zfs_fuid_info_free(fuidp);
FNFS#
--
Sam Fourman Jr.
Fourman Networks
http://www.fourmannetworks.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"
Re: Problem with ZFS version 15
> If you have previous saved gpart information (e.g. start/end) then you > can safely destroy and re-create the GPT partitions without destroying > the data. > > Note that you may need to backup and dd the first and last sector of > your hard drive before proceeding. > Could someone post a example of how to correctly backup a gpart partition information -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: Problem with ZFS version 15
On Mon, Jul 19, 2010 at 7:37 PM, Alexander Best wrote: > how about adding a periodic script to /etc/periodic/daily to backup the > information? > > the idea was raised a long time ago already, but was abandoned [1]. > > cheers. > alex > I think that is a good idea, if you have a script to do that I would test it -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
Re: How to get the source code of FreeBSD-Clang?
On Sat, Jan 24, 2015 at 11:16 PM, Yue Chen wrote: > When I use the original versions (even 3.4.1) of LLVM/Clang to compile > FreeBSD kernel, it always has problems. > > Since I need to modify something in LLVM source and then build the kernel, > where can I get the FreeBSD-friendly Clang/LLVM source code? > > It comes in base, if you have FreeBSD 10 or the source for 10.x all the source is included. -- Sam Fourman Jr. ___ 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: UEFI boot doesn't work on 10.1-RELEASE/11.0-CURRENT
On Thu, Feb 5, 2015 at 1:37 PM, Piotr Kubaj wrote: > Hi all, > > I'm trying to set up FreeBSD on MSI X99S SLI Plus. BIOS compatibility > mode doesn't work, so I need to use the new UEFI boot. All is well after > installing FreeBSD, but when I do buildworld/kernel/installworld cycle I > get: > >> FreeBSD Boot Block > Loader: /boot/loader.efi > The same happens on both 10.1-RELEASE and 11.0-CURRENT. I haven't > modified the kernel or anything else. > > I can confirm this, a straight USB image for current doesn't boot, 10.0 boots fine but nothing after. I have a Lenovo B570 uefi -- Sam Fourman Jr. ___ 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: UEFI boot doesn't work on 10.1-RELEASE/11.0-CURRENT
> > Can you tell us which version of CURRENT you tried? > > I tried, r278209 on my lenovo B570, then very early in the boot process it locks up and stops. > -- > Rui Paulo > > > > -- Sam Fourman Jr. ___ 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: UEFI boot doesn't work on 10.1-RELEASE/11.0-CURRENT
On Thu, Feb 5, 2015 at 9:02 PM, Rui Paulo wrote: > On Feb 5, 2015, at 18:29, Sam Fourman Jr. wrote: > > > >> Can you tell us which version of CURRENT you tried? > >> > >> I tried, r278209 on my lenovo B570, then very early in the boot process > it > > locks up and stops. > > If it stops in boot1, then it's because it couldn't find the UFS partition > with loader.efi. Did you test the memstick or your own installation? > > it was memstick > -- > Rui Paulo > > > > -- Sam Fourman Jr. ___ 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: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2)
> Just as a data point, 'stray timeout' happens in clean -current without > new patch as well. So whatever that is, it is not caused by the patch. > > -- > Alexander Kabaev > I can confirm this, however, when it happens is RARE... it seems like it happens when I am typing in the address bar of chromium.. im using HEAD with a RAEDON on amd64 -- Sam Fourman Jr. ___ 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: [CFT] Xorg Upgrade 7.5.2
pci0 pci4: on pcib4 xhci0: mem 0xdd20-0xdd20 irq 19 at device 0.0 on pci4 xhci0: 32 byte context size. usbus1 on xhci0 pcib5: irq 17 at device 28.5 on pci0 pci5: on pcib5 re0: port 0x9000-0x90ff mem 0xd2104000-0xd2104fff,0xd210-0xd2103fff irq 17 at device 0.0 on pci5 re0: Using 1 MSI-X message re0: turning off MSI enable bit. re0: ASPM disabled re0: Chip rev. 0x2c00 re0: MAC rev. 0x miibus0: on re0 rgephy0: PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 14:da:e9:20:d9:96 ehci1: mem 0xdf007000-0xdf0073ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2: on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xe0b0-0xe0b7,0xe0a0-0xe0a3,0xe090-0xe097,0xe080-0xe083,0xe060-0xe07f mem 0xdf006000-0xdf0067ff irq 19 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich0: at channel 0 on ahci0 ahcich2: at channel 2 on ahci0 pci0: at device 31.3 (no driver attached) acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 battery0: on acpi0 atkbdc0: port 0x60,0x64 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse, device ID 3 orm0: at iomem 0xc-0xce7ff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 ppc0: cannot reserve I/O port range est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 est2: on cpu2 p4tcc2: on cpu2 est3: on cpu3 p4tcc3: on cpu3 est4: on cpu4 p4tcc4: on cpu4 est5: on cpu5 p4tcc5: on cpu5 est6: on cpu6 p4tcc6: on cpu6 est7: on cpu7 p4tcc7: on cpu7 Timecounters tick every 1.000 msec hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 27,33 and 24,25 on hdaa0 pcm1: at nid 30 on hdaa0 hdacc1: at cad 3 on hdac0 hdaa1: at nid 1 on hdacc1 pcm2: at nid 6 on hdaa1 usbus0: 480Mbps High Speed USB v2.0 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: <0x1b73> at usbus1 uhub1: <0x1b73 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 uhub1: 2 ports with 2 removable, self powered uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered ugen0.2: at usbus0 uhub3: on usbus0 ugen2.2: at usbus2 uhub4: on usbus2 uhub3: 6 ports with 6 removable, self powered uhub4: 6 ports with 6 removable, self powered ugen0.3: at usbus0 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 610480MB (1250263728 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 SMP: AP CPU #1 Launched! cd0 at ahcich2 bus 0 scbus1 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed SMP: AP CPU #4 Launched! SMP: AP CPU #6 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #7 Launched! SMP: AP CPU #2 Launched! Timecounter "TSC-low" frequency 15589953 Hz quality 1000 WARNING: WITNESS option enabled, expect reduced performance. ugen0.4: at usbus0 Trying to mount root from ufs:/dev/ada0p2 [rw]... wlan0: Ethernet address: 74:2f:68:3d:05:69 ubt0: on usbus0 WARNING: attempt to domain_add(bluetooth) after domainfinalize() WARNING: attempt to domain_add(netgraph) after domainfinalize() ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ng_hci_process_command_timeout: ubt0hci - unable to complete HCI command OGF=0x3, OCF=0x3. Timeout ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_intr_read_callback:767: interrupt transfer failed: USB_ERR_STALLED ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ubt0: ubt_bulk_read_callback:867: bulk-in transfer failed: USB_ERR_STALLED ath0: ath_start: sc_inreset_cnt > 0; bailing Sam Fourman Jr. ___ 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"
USB3 and a Seagate FA GoFlex
: uhub_read_port_status: port 5, wPortStatus=0x0103, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 6, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 2, wPortStatus=0x0500, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: usb_needs_explore: Feb 9 18:13:44 kernel: usb_bus_powerd: bus=0xff8001e04cd8 Feb 9 18:13:44 kernel: uhub_explore: udev=0xfe001bb3d000 addr=1 Feb 9 18:13:44 kernel: uhub_read_port_status: port 1, wPortStatus=0x0503, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_explore: udev=0xfe001bb3c000 addr=2 Feb 9 18:13:44 kernel: uhub_read_port_status: port 1, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 2, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 3, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 4, wPortStatus=0x0503, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 5, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 6, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 7, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 8, wPortStatus=0x0100, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION Feb 9 18:13:44 kernel: uhub_read_port_status: port 2, wPortStatus=0x0500, wPortChange=0x, err=USB_ERR_NORMAL_COMPLETION -- Sam Fourman Jr. ___ 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: USB3 and a Seagate FA GoFlex
On Fri, Feb 10, 2012 at 2:08 AM, Hans Petter Selasky wrote: > On Friday 10 February 2012 07:53:16 Sam Fourman Jr. wrote: > > UQ_MSC > > Try to add some of the quirks like this: > > usbconfig -d X.Y add_quirk UQ_MSC_XXX > > UQ_MSC_NO_INQUIRY > UQ_MSC_NO_SYNC_CACHE > > Then replug your device. > > Icarus# usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.2: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen2.2: at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen0.3: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen0.4: at usbus0, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2: at usbus1, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=ON Icarus# usbconfig -d 1.2 add_quirk UQ_MSC_NO_INQUIRY Icarus# usbconfig -d 1.2 add_quirk UQ_MSC_NO_SYNC_CACHE ugen1.2: at usbus1 (disconnected) umass0: at uhub1, port 1, addr 1 (disconnected) (pass2:umass-sim0:0:0:0): lost device (pass2:umass-sim0:0:0:0): removing device entry (da0:umass-sim0:0:0:0): lost device - 0 outstanding, 0 refs (da0:umass-sim0:0:0:0): removing device entry ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x4400 umass0:3:0:-1: Attached to scbus3 (probe0:umass-sim0:0:0:0): SCSI status error (probe0:umass-sim0:0:0:0): INQUIRY. CDB: 12 1 0 0 ff 0 (probe0:umass-sim0:0:0:0): CAM status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI status: Check Condition (probe0:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:24,0 (Invalid field in CDB) (probe0:umass-sim0:0:0:0): Error 22, Unretryable error pass2 at umass-sim0 bus 0 scbus3 target 0 lun 0 pass2: < > Removable Direct Access SCSI-2 device pass2: 400.000MB/s transfers GEOM: new disk da0 (da0:umass-sim0:0:0:0): SCSI status error (da0:umass-sim0:0:0:0): READ CAPACITY(10). CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI status: Check Condition (da0:umass-sim0:0:0:0): SCSI sense: NOT READY asc:4,1 (Logical unit is in process of becoming ready) (da0:umass-sim0:0:0:0): Polling device for readiness da0 at umass-sim0 bus 0 scbus3 target 0 lun 0 da0: < > Removable Direct Access SCSI-2 device da0: 400.000MB/s transfers da0: 1907729MB (3907029167 512 byte sectors: 255H 63S/T 243201C) (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): AutoSense failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error (da0:umass-sim0:0:0:0): Request completed with CAM_REQ_CMP_ERR (da0:umass-sim0:0:0:0): Retrying command (da0:umass-sim0:0:0:0): AutoSense failed (da0:umass-sim0:0:0:0): Error 5, Unretryable error --HPS > -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
USB keyboard problem
hello, I believe my keyboard is being detected as a mouse by mistake using amd64 HEAD svn r242748 I can not use this keyboard, I have to plug in another one. this is also broken in FreeBSD 9.1RC3 is this simple to patch? any help is appreciated uhid0: on usbus0 uhid1: on usbus3 ums0: on usbus0 ums0: 3 buttons and [XYZ] coordinates ID=0 ums1: on usbus0 ums1: 7 buttons and [XYZ] coordinates ID=0 verbose dmesg follows http://www.samjess.com/keyboard.txt -- Sam Fourman Jr. ___ 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: USB keyboard problem
On Mon, Nov 12, 2012 at 2:22 PM, Sam Fourman Jr. wrote: > hello, > > I believe my keyboard is being detected as a mouse by mistake using amd64 > HEAD svn r242748 > I can not use this keyboard, I have to plug in another one. > > this is also broken in FreeBSD 9.1RC3 > > is this simple to patch? any help is appreciated > > > uhid0: on usbus0 > uhid1: on > usbus3 > ums0: on usbus0 > ums0: 3 buttons and [XYZ] coordinates ID=0 > ums1: on usbus0 > ums1: 7 buttons and [XYZ] coordinates ID=0 > > > verbose dmesg follows > http://www.samjess.com/keyboard.txt > > -- > > Sam Fourman Jr. > What does "usbconfig -d X.Y dump_device_desc dump_curr_config_desc" say about > your device? > > --HPS > http://www.samjess.com/usbconfig.txt Does anyone know where I would start hacking around to fix this? Sam ___ 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"
Clang/LLVM revision 169451
hello list, I like to run FreeBSD HEAD on my workstation, I am wondering if a easy way exists to follow LLVM HEAD in FreeBSD HEAD? I am in need of this patch http://llvm.org/viewvc/llvm-project?view=rev&revision=169451 to specifically fix http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/174459 im not sure how it works, but does someone have a merge script that basically puts LLVM HEAD into FreeBSD HEAD? looking for some tips -- Sam Fourman Jr. ___ 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: Clang/LLVM revision 169451
> No, there is no one-click merge script, it needs humanoid help, I'm > afraid. :-) Is there any reason you cannot just install the port, or > if that is too outdated, just checkout from llvm.org directly and build > it? is it currently possible to build FreeBSD world, without clang and then build clang from ports? ___ 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: Clang/LLVM revision 169451
On Mon, Dec 17, 2012 at 6:50 AM, Dimitry Andric wrote:
> On 2012-12-17 09:36, Sam Fourman Jr. wrote:
>>>
>>> No, there is no one-click merge script, it needs humanoid help, I'm
>>> afraid. :-) Is there any reason you cannot just install the port, or
>>> if that is too outdated, just checkout from llvm.org directly and build
>>> it?
>>
>>
>> is it currently possible to build FreeBSD world, without clang and
>> then build clang from ports?
>
>
> There is no real need, as you can just put /usr/local/bin before
> /usr/bin in your PATH, but if you really want to do so, you can put the
> following in /etc/src.conf:
>
> CC=gcc
> CXX=g++
> CPP=gcpp
> WITHOUT_CLANG=
>
> From then on, you build world with gcc, which will also be installed as
> /usr/bin/cc again.
I ended up generating and applying this patch, and rebuilt world again
root@www:/root # cat clang-169451.patch
Index: contrib/llvm/tools/clang/include/clang/Sema/Scope.h
===
--- contrib/llvm/tools/clang/include/clang/Sema/Scope.h (revision 244350)
+++ contrib/llvm/tools/clang/include/clang/Sema/Scope.h (working copy)
@@ -84,11 +84,18 @@
/// TryScope - This is the scope of a C++ try statement.
TryScope = 0x1000,
+/// CatchScope - This is the scope of a C++ catch statement.
+CatchScope = 0x2000,
+
+/// FnTryCatchScope - This is the scope for a function-level C++ try or
+/// catch scope.
+FnTryCatchScope = 0x4000,
+
/// FnTryScope - This is the scope of a function-level C++ try scope.
-FnTryScope = 0x3000,
+FnTryScope = TryScope | FnTryCatchScope,
/// FnCatchScope - This is the scope of a function-level C++ catch scope.
-FnCatchScope = 0x4000
+FnCatchScope = CatchScope | FnTryCatchScope
};
private:
/// The parent scope for this scope. This is null for the translation-unit
Index: contrib/llvm/tools/clang/lib/Parse/ParseStmt.cpp
===
--- contrib/llvm/tools/clang/lib/Parse/ParseStmt.cpp(revision 244350)
+++ contrib/llvm/tools/clang/lib/Parse/ParseStmt.cpp(working copy)
@@ -2197,7 +2197,7 @@
// The name in a catch exception-declaration is local to the handler and
// shall not be redeclared in the outermost block of the handler.
ParseScope CatchScope(this, Scope::DeclScope | Scope::ControlScope |
- (FnCatch ? Scope::FnCatchScope : 0));
+ (FnCatch ? Scope::FnCatchScope : Scope::CatchScope));
// exception-declaration is equivalent to '...' or a parameter-declaration
// without default arguments.
Index: contrib/llvm/tools/clang/lib/Sema/IdentifierResolver.cpp
===
--- contrib/llvm/tools/clang/lib/Sema/IdentifierResolver.cpp
(revision 244350)
+++ contrib/llvm/tools/clang/lib/Sema/IdentifierResolver.cpp(working copy)
@@ -135,16 +135,13 @@
// of the controlled statement.
//
assert(S->getParent() && "No TUScope?");
- if (S->getFlags() & Scope::FnTryScope)
-return S->getParent()->isDeclScope(D);
if (S->getParent()->getFlags() & Scope::ControlScope) {
-if (S->getParent()->getFlags() & Scope::FnCatchScope) {
- S = S->getParent();
- if (S->isDeclScope(D))
-return true;
-}
+S = S->getParent();
+if (S->isDeclScope(D))
+ return true;
+ }
+ if (S->getFlags() & Scope::FnTryCatchScope)
return S->getParent()->isDeclScope(D);
- }
}
return false;
}
___
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: [HEADS UP] Imported llvm/clang 3.2 RC2 into head
> With (WITH_GCC) gcc47 I've successfully built and I'm running > libreoffice after icu bump. just to be clear, what exactly do you put in /etc/make.conf to build all ports with GCC on a fresh install of HEAD? is it simply WITH_GCC=YES Sam Fourman Jr. ___ 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"
AMD K15 sensor support
I was wondering if anyone is aware of any ongoing effort to support the on CPU temp sensors on the AMD K15 CPU's amdtemp only supports up to K11 so far as I can tell Sam Fourman Jr. Titan# dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #1 r231712: Tue Feb 14 15:46:59 CST 2012 root@Titan:/usr/obj/usr/src/sys/TITAN amd64 WARNING: WITNESS option enabled, expect reduced performance. link_elf_obj: symbol PHYS_TO_VM_PAGE undefined KLD file vboxdrv.ko - could not finalize loading module_register: module pci/sdhci already exists! Module pci/sdhci failed to register: 17 CPU: AMD FX(tm)-6100 Six-Core Processor (3624.21-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x600f12 Family = 15 Model = 1 Stepping = 2 Features=0x178bfbff Features2=0x1e98220b AMD Features=0x2e500800 AMD Features2=0x1c9bfff,> TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16497942528 (15733 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs FreeBSD/SMP: 1 package(s) x 6 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ctl: CAM Target Layer loaded cryptosoft0: on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, cfca (3) failed cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 attimer0: port 0x40-0x43 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed0-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 atrtc0: port 0x70-0x73 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <32-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 18 at device 2.0 on pci0 pci1: on pcib1 vgapci0: port 0xdf00-0xdf7f mem 0xf800-0xf9ff,0xd000-0xd7ff,0xdc00-0xdfff irq 18 at device 0.0 on pci1 nvidia0: on vgapci0 vgapci0: child nvidia0 requested pci_enable_io vgapci0: child nvidia0 requested pci_enable_io hdac0: mem 0xfbffc000-0xfbff irq 19 at device 0.1 on pci1 pcib2: irq 17 at device 9.0 on pci0 pci2: on pcib2 xhci0: mem 0xfd1f8000-0xfd1f irq 17 at device 0.0 on pci2 xhci0: 64 byte context size. usbus0 on xhci0 pcib3: irq 18 at device 10.0 on pci0 pci3: on pcib3 ahci0: port 0xef00-0xef07,0xee00-0xee03,0xed00-0xed07,0xec00-0xec03,0xeb00-0xeb0f mem 0xfdbff000-0xfdbff1ff irq 18 at device 0.0 on pci3 ahci0: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS ahcich0: at channel 0 on ahci0 ahcich1: at channel 1 on ahci0 ahci1: port 0xff00-0xff07,0xfe00-0xfe03,0xfd00-0xfd07,0xfc00-0xfc03,0xfb00-0xfb0f mem 0xfdfff000-0xfdfff3ff irq 19 at device 17.0 on pci0 ahci1: AHCI v1.20 with 6 6Gbps ports, Port Multiplier supported ahcich2: at channel 0 on ahci1 ahcich3: at channel 1 on ahci1 ahcich4: at channel 2 on ahci1 ahcich5: at channel 3 on ahci1 ahcich6: at channel 4 on ahci1 ahcich7: at channel 5 on ahci1 ohci0: mem 0xfdffe000-0xfdffefff irq 18 at device 18.0 on pci0 usbus1: on ohci0 ehci0: mem 0xfdffd000-0xfdffd0ff irq 17 at device 18.2 on pci0 usbus2: EHCI version 1.0 usbus2: on ehci0 ohci1: mem 0xfdffc000-0xfdffcfff irq 18 at device 19.0 on pci0 usbus3: on ohci1 ehci1: mem 0xfdffb000-0xfdffb0ff irq 17 at device 19.2 on pci0 usbus4: EHCI version 1.0 usbus4: on ehci1 pci0: at device 20.0 (no driver attached) hdac1: mem 0xfdff4000-0xfdff7fff irq 16 at device 20.2 on pci0 isab0: at device 20.3 on pci0 isa0: on isab0 pcib4: at device 20.4 on pci0 pci4: on pcib4 fwohci0: port 0xbf00-0xbf7f mem 0xfddff000-0xfddff7ff irq 22 at device 14.0 on pci4 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:49:e5:50:51:51:05:00 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0xcfd84000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:49:e5:51:05:00 fwe0: Ethernet address: 02:49:e5:51:05:00 fwip0: on firewire0 fwip0: Firewire address: 00:49:e5:50:51:51:05:00 @ 0xfffe, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, CYC
Re: AMD K15 sensor support
able, self powered uhub8: 4 ports with 4 removable, self powered uhub2: 5 ports with 5 removable, self powered uhub4: 5 ports with 5 removable, self powered ugen3.2: at usbus3 ugen1.2: at usbus1 ums0: on usbus1 ukbd1: on usbus3 ums0: 8 buttons and [XYZ] coordinates ID=0 kbd2 at ukbd1 uhid0: on usbus3 ada0 at ahcich1 bus 0 scbus3 target 0 lun 0 ada0: ATA-7 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 238475MB (488397168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad10 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #5 Launched! SMP: AP CPU #3 Launched! SMP: AP CPU #4 Launched! Timecounter "TSC-low" frequency 12977308 Hz quality 1000 WARNING: WITNESS option enabled, expect reduced performance. cd0 at ahcich0 bus 0 scbus2 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 150.000MB/s transfers (SATA 1.x, UDMA5, ATAPI 12bytes, PIO 8192bytes) cd0: cd present [120625 x 2048 byte records] -- Sam Fourman Jr. Fourman Networks ___ 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: AMD K15 sensor support
> > BTW, the temperature reading goes up when the system is loaded and > goes down when it is idle, right? Just making sure... > > Thanks, > > Jung-uk Kim > yes that is correct I tested this patch on 2 FX series Processors a 6 core and 8 core, both work fine. any chance you could commit this patch to HEAD? -- Sam Fourman Jr. ___ 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"
CURRENT is broken as of r255958
r255958 builds world and kernel fine, but make release fails
I used vi to wield # signs, and produced a patch that fixes the
problem, however
this is not the correct fix.
could someone help me write the correct patch?
root@NewBSD:/usr/src # svnlite info
Path: .
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 255960
Node Kind: directory
Schedule: normal
Last Changed Author: dteske
Last Changed Rev: 255958
Last Changed Date: 2013-09-30 21:26:03 + (Mon, 30 Sep 2013)
Index: etc/periodic/daily/Makefile
===
--- etc/periodic/daily/Makefile (revision 255960)
+++ etc/periodic/daily/Makefile (working copy)
@@ -24,9 +24,9 @@
FILES+= 310.accounting
.endif
-.if ${MK_BIND_NAMED} != "no"
-FILES+= 470.status-named
-.endif
+#.if ${MK_BIND_NAMED} != "no"
+#FILES+= 470.status-named
+#.endif
.if ${MK_CALENDAR} != "no"
FILES+= 300.calendar
--
Sam Fourman Jr.
___
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: [RFC] libdispatch (aka Grand Central Dispatch) in base
On Wed, Oct 30, 2013 at 2:04 AM, Teske, Devin wrote: > Hi all, > > I'd like to bring up the discussion for topic.. > > Importing libdispatch (aka Apple's Grand Central Dispatch) into base > (contrib?). > > Specifically into HEAD then MFC'd only as far back as stable/10. > > Here's the reason why: > http://devinteske.com/freebsd-installer-enhancements > > I say +1 to your idea Sam Fourman Jr. ___ 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: [CFT] Kernel-Selection Enhancemnt to Boot Menu
On Sat, Nov 2, 2013 at 7:09 AM, Teske, Devin wrote: > Hi all, > > Here's a chance to test out the kernel selection menu enhancements > to the boot loader menu before they go into HEAD. > > Discussion welcome, feedback desired. > > No recompile needed, just drop the new forth files onto a HEAD or > stable/9 box and reboot. > -- > Cheers, > Devin > where are the forth files in question? -- Sam Fourman Jr. ___ 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"
RTL8111/8168B not negotiating 1GB
Hello list, I have a Asus Sabertooth 990FXv2 motherboard, and a run of the mill NetGear DGS2205 desktop gig switch with linux my Ethernet can negotiate at 1GB but with FreeBSD it can not if I force the device to 1000baseT with ifconfig it does not work. uname -a FreeBSD NewBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r260188M: Thu Jan 2 04:27:49 CST 2014 sfourman@NewBSD:/usr/obj/usr/src/sys/GENERIC amd64 re0@pci0:10:0:0: class=0x02 card=0x85051043 chip=0x816810ec rev=0x09 hdr=0x00 vendor = 'Realtek Semiconductor Co., Ltd.' device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' class = network subclass = ethernet root@NewBSD:/usr/home/sfourman/Desktop # ifconfig re0: flags=8843 metric 0 mtu 1500 options=8209b ether 60:a4:4c:60:d5:a7 inet 192.168.1.31 netmask 0xff00 broadcast 192.168.1.255 inet6 fe80::62a4:4cff:fe60:d5a7%re0 prefixlen 64 scopeid 0x1 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active -- Sam Fourman Jr. ___ 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: RTL8111/8168B not negotiating 1GB
On Thu, Jan 2, 2014 at 9:06 PM, Adam Vande More wrote: > On Thu, Jan 2, 2014 at 7:39 PM, Sam Fourman Jr. wrote: > >> Hello list, >> >> I have a Asus Sabertooth 990FXv2 motherboard, and a run of the mill >> NetGear DGS2205 desktop gig switch >> >> with linux my Ethernet can negotiate at 1GB but with FreeBSD it can not >> if I force the device to 1000baseT with ifconfig it does not work. >> >> >> uname -a >> FreeBSD NewBSD 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r260188M: Thu Jan 2 >> 04:27:49 CST 2014 sfourman@NewBSD:/usr/obj/usr/src/sys/GENERIC amd64 >> >> >> >> re0@pci0:10:0:0: class=0x02 card=0x85051043 chip=0x816810ec rev=0x09 >> hdr=0x00 >> vendor = 'Realtek Semiconductor Co., Ltd.' >> device = 'RTL8111/8168B PCI Express Gigabit Ethernet controller' >> class = network >> subclass = ethernet >> >> >> >> root@NewBSD:/usr/home/sfourman/Desktop # ifconfig >> re0: flags=8843 metric 0 mtu 1500 >> >> options=8209b >> ether 60:a4:4c:60:d5:a7 >> inet 192.168.1.31 netmask 0xff00 broadcast 192.168.1.255 >> inet6 fe80::62a4:4cff:fe60:d5a7%re0 prefixlen 64 scopeid 0x1 >> nd6 options=29 >> media: Ethernet autoselect (100baseTX ) >> status: active > > > /etc/rc.conf is important here as well as the complete steps and output > which provoked this response: > > "but with FreeBSD it can not > if I force the device to 1000baseT with ifconfig it does not work." > > In the given output, autoselect clearly selects 100Mb connection, the > question is why. > > > rc.conf is this: defaultrouter="192.168.1.1" ifconfig_re0="inet 192.168.1.31 netmask 0xff00" but the problem is we need to patch the re driver somehow because I have many motherboards where this exact nic does not work correctly. > > -- > Adam > -- Sam Fourman Jr. ___ 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: RFC: Remove pty(4)
Sam Fourman Jr. On Aug 20, 2014 1:00 PM, "Davide Italiano" wrote: > > One of my personal goals for 11 is to get rid of cloning mechanism > entirely, and pty(4) is one of the few in-kernel drivers still relying > on such mechanism. > It's not possible, at least to my understanding, converting pty(4) to > cdevpriv(9) as happened with other drivers. This is mainly because we > always need a pair of devices (/dev/ptyXX and /dev/ttyXX) and > userspace loops over ptyXX and after it successfully opens it tries to > open the other one with the same suffix. So, having a single device is > not really enough. > My option, instead, is that of removing pty(4), which is nothing more > than a compatibility driver, and move pmtx(4) code somewhere else. > The main drawback of the removal of this is that it makes impossible > to run FreeBSD <= 7 jails and SSH into them. I personally don't > consider this a huge issue, in light of the fact that FreeBSD-7 has > been EOL for a long time, but I would like to hear other people > comments. > > The code review for the proposed change can be found here: > https://reviews.freebsd.org/D659 > > If I won't get any objection I'll commit this in one week time, i.e. > August 27th. > > -- > Davide > I am all for the advancement of FreeBSD, but I for one maintain appliance products based on 7.x, most of the time I vote for out with the old in with the new... But are we certain all options for keeping compat have been explored? Just my 2c Sam Fourman Jr. > "There are no solved problems; there are only problems that are more > or less solved" -- Henri Poincare > ___ > 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" ___ 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: [HEADSUP] pkg(8) is now the only package management tool
> > And for the portsnap users? > > In short, this change doesn't directly effect portsnap users. Portsnap is a tool that used to obtain a copy of the ports tree. Portsnap is only one way, another way to get a copy of the ports tree is by using subversion and checking it out by using the svn command. pkg(8) is a package management tool, and to make use of most packages having a copy of the ports tree is not required. > > > -- > Michelle Sullivan > http://www.mhix.org/ > > ___ > freebsd-po...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > -- Sam Fourman Jr. ___ 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: Re[2]: ipfilter(4) needs maintainer
I agree with this, we dont need 3 packet filters, it seems like we should focus the people interested in working on packet filters,toward the packet filter most actively maintained, the fact that there is 3 in base is overkill, Just depreciate it and be done with it a new email, asking for help to bring pf closer to OpenBSD, is more of a productive conversation. On Sun, Apr 14, 2013 at 1:30 PM, wishmaster wrote: > > > --- Original message --- > From: "Gary Palmer" > Date: 14 April 2013, 19:06:59 > > > > On Sun, Apr 14, 2013 at 09:48:33AM -0600, Warren Block wrote: > > > Is it possible to move ipfilter into a port? > > > > That may work short term, but the ENOMAINTAINER problem will quickly > creep > > up again as kernel APIs change. If the author has lost interest in > > maintaining the FreeBSD port of ipfilter then unless someone steps > forward > > to carry on the work, I don't see much of a future for ipfilter in > > FreeBSD > > > > Do we honestly need three packet filters? > > Yes! This is the most clever thought in this thread. Why we need 3 > firewalls? Two packet filters it's excess too. > We have two packet filters: one with excellent syntax and > functionality but with outdated bandwidth control mechanism (aka ALTQ); > another - with nice traffic shaper/prioritization (dummynet)/classification > (diffused) but with complicated implementation in not trivial tasks. > May be the next step will be discussion about one packet filter in the > system?.. > > Cheers, > > > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org" > -- Sam Fourman Jr. ___ 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: ipfilter(4) needs maintainer
Thank you to those that have expressed interest in maintaining IP Filter.. My thoughts are, could we consider putting a option in the kernel config, and leaving it off by default for GENERIC? I think this is a acceptable compromise, considering some people wish for it to be removed. Sam Fourman Jr. On Mon, Apr 15, 2013 at 1:48 PM, Cy Schubert wrote: > In message <18df99b0-6e66-4906-a233-7778451b8...@felyko.com>, Rui Paulo > writes: > > 2013/04/15 9:55、Cy Schubert のメッセージ: > > > > > I've been planning on taking on IP Filter for quite some time. > > > Unfortunately I've left my src commit bit lapse (my ports commit bit is > > > alive and well though) thus I'm looking for a mentor. In addition I'm > > > working on an ACER WMI/ACPI kld. One mentor would be preferred but two > > > would be fine too. > > > > What are your plans regarding ipfilter? I remain unconvinced that it > should b > > e in the base system. Perhaps you can work on it as a port? > > The initial plan was to import IP Filter 5.1.2 into HEAD. darrenr@ hadn't > done much with IPF while employed with Sun. Since then there has been some > development that is long overdue for HEAD. > > I'm not sure if I'd MFC it into 9 or not. > > I did consider a port but given it would has to touch bits and pieces of > the source tree (/usr/src), a port would be messy and the decision was made > to work on importing it into base. > > > > > Why do you want to work on something that people have been trying to > remove s > > ince 2005? > > I and others have been using it in FreeBSD for over decade. For the longest > of time we'd use a common set of rules across a FreeBSD and Solaris farm > (using ipfmeta, makefiles, rsync, rdist, and a local CVS repo). > Interoperability with other systems which use IP Filter is a plus. If > there's a maintainer, it only makes FreeBSD richer. Losing IP Filter would > be a loss. > > > -- > Cheers, > Cy Schubert > FreeBSD UNIX: Web: http://www.FreeBSD.org > > > ___________ > 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" > -- Sam Fourman Jr. ___ 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: ipfilter(4) needs maintainer
To my knowledge it is already off by default and you need these options to enable it options IPFILTER options IPFILTER_LOG so to those that wish to have it removed from base, if it has a maintainer whats the trouble? On Mon, Apr 15, 2013 at 2:49 PM, Sam Fourman Jr. wrote: > > Thank you to those that have expressed interest in maintaining IP Filter.. > > My thoughts are, could we consider putting a option in the kernel config, > and leaving it off by default for GENERIC? > I think this is a acceptable compromise, considering some people wish for > it to be removed. > > Sam Fourman Jr. > > > On Mon, Apr 15, 2013 at 1:48 PM, Cy Schubert wrote: > >> In message <18df99b0-6e66-4906-a233-7778451b8...@felyko.com>, Rui Paulo >> writes: >> > 2013/04/15 9:55、Cy Schubert のメッセージ: >> > >> > > I've been planning on taking on IP Filter for quite some time. >> > > Unfortunately I've left my src commit bit lapse (my ports commit bit >> is >> > > alive and well though) thus I'm looking for a mentor. In addition I'm >> > > working on an ACER WMI/ACPI kld. One mentor would be preferred but two >> > > would be fine too. >> > >> > What are your plans regarding ipfilter? I remain unconvinced that it >> should b >> > e in the base system. Perhaps you can work on it as a port? >> >> The initial plan was to import IP Filter 5.1.2 into HEAD. darrenr@ hadn't >> done much with IPF while employed with Sun. Since then there has been some >> development that is long overdue for HEAD. >> >> I'm not sure if I'd MFC it into 9 or not. >> >> I did consider a port but given it would has to touch bits and pieces of >> the source tree (/usr/src), a port would be messy and the decision was >> made >> to work on importing it into base. >> >> > >> > Why do you want to work on something that people have been trying to >> remove s >> > ince 2005? >> >> I and others have been using it in FreeBSD for over decade. For the >> longest >> of time we'd use a common set of rules across a FreeBSD and Solaris farm >> (using ipfmeta, makefiles, rsync, rdist, and a local CVS repo). >> Interoperability with other systems which use IP Filter is a plus. If >> there's a maintainer, it only makes FreeBSD richer. Losing IP Filter would >> be a loss. >> >> >> -- >> Cheers, >> Cy Schubert >> FreeBSD UNIX: Web: http://www.FreeBSD.org >> >> >> ___ >> 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 >> " >> > > > > -- > > Sam Fourman Jr. > -- Sam Fourman Jr. ___ 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"
ZFS error referencing Solaris
Hello list, today I am trying to upgrade my fileserver, I was running a kernel based on a then HEAD snapshot from sometime in late 2009.. I exported the ZFS dataset... booted from a current HEAD snapshot and I got this error message... ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Solaris: WARNING: can't open objset for Network/home/lmi/Public/%20091012 its not a big deal, I don't care about anything in that dataset, however I thought someone might want to know a error message still makes reference to Solaris... this is from a recent snapshot of HEAD uname -a FreeBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #29 r249631M: Thu Apr 18 22:30:06 EDT 2013 root@MiniBSD:/usr/obj/usr/src/sys/GENERIC amd64 root@:~ # -- Sam Fourman Jr. ___ 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"
buildworld failed on HEAD
hello all, I cant seem to figure out what is making build world fail, I could use some help from someone that knows more Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r253459: Fri Jul 19 00:47:22 UTC 2013 root@Border:/usr/obj/usr/src/sys/BORDER amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Core(TM)2 Quad CPU @ 2.40GHz (2400.04-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x6f7 Family = 0x6 Model = 0xf Stepping = 7 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 7970164736 (7600 MB) --- var-tracking.o --- cc -O2 -pipe -DGCCVER=\"4.2\" -DIN_GCC -DHAVE_CONFIG_H -DPREFIX=\"/usr\" -I/usr/obj/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libcpp/include -I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcclibs/libdecnumber -std=gnu89 -Qunused-arguments -fstack-protector -c /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/var-tracking.c -o var-tracking.o --- usr.sbin.all__D --- --- acpi.o --- cc -O2 -pipe -I/usr/src/usr.sbin/acpi/acpidump/../../../sys -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.sbin/acpi/acpidump/acpi.c --- lib.all__D --- --- tty_update.po --- cc -pg -O2 -pipe -I. -I/usr/obj/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../ncurses -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/include -I/usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses -Wall -DNDEBUG -DHAVE_CONFIG_H -DFREEBSD_NATIVE -DTERMIOS -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wno-uninitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -c /usr/src/lib/ncurses/ncurses/../../../contrib/ncurses/ncurses/tty/tty_update.c -o tty_update.po --- usr.bin.all__D --- --- parsedata.o --- cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/calendar/parsedata.c --- io.o --- --- parsedata.o --- /usr/src/usr.bin/calendar/parsedata.c:989:17: error: null character ignored [-Werror,-Wnull-character] i = strtol (s, ^ --- io.o --- cc -O2 -pipe -std=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs -Wredundant-decls -Wold-style-definition -Wmissing-variable-declarations -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -c /usr/src/usr.bin/calendar/io.c --- parsedata.o --- 1 error generated. *** [parsedata.o] Error code 1 make: stopped in /usr/src/usr.bin/calendar -- Sam Fourman Jr. ___ 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: buildworld failed on HEAD
On Fri, Jul 19, 2013 at 1:53 PM, Ryan Stone wrote:
> On Fri, Jul 19, 2013 at 1:35 PM, Sam Fourman Jr. wrote:
>
>> /usr/src/usr.bin/calendar/parsedata.c:989:17: error: null character
>> ignored
>> [-Werror,-Wnull-character]
>> i = strtol (s,
>>
>
> Try looking at this file in vi. It sounds like a '\0' has somehow been
> inserted into this file and corrupted it. How did you get your source tree?
>
thats EXACTLY whats happening here...
988 if (s[0] == '+' || s[0] == '-') {
989 i = strtol (s,^@&es, 10);
990 if (*es != '\0') /* trailing
junk */
991 errx (1, "Invalid specifier format: %s\n",
s);
992 return (i);
993 }
994
I used the new svnlite tool to get the src... so I did this:
rm /usr/src/usr.bin/calendar/parsedata.c
svnlite up
and it restored the file but it still has the ^@ so im just going to
manually remove it... im not sure whats going on here...
Sam
--
Sam Fourman Jr.
___
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"
Network card issues ifconfig down ifconfig up required
0xefcf8000, size 16384, enabled bar [20] = type I/O Port, range 32, base 0xbc00, size 128, enabled cap 01[54] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[5c] = MSI supports 1 message, 64 bit cap 10[70] = PCI-Express 1 legacy endpoint max data 256(1024) link x1(x1) speed 2.5(2.5) ASPM disabled(L0s) ecap 0001[100] = AER 1 0 fatal 1 non-fatal 0 corrected ath0@pci0:4:0:0: class=0x028000 card=0x009a106b chip=0x0030168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR9300 Wireless LAN adaptor' class = network bar [10] = type Memory, range 64, base 0xefac, size 131072, enabled cap 01[40] = powerspec 2 supports D0 D1 D2 D3 current D0 cap 05[50] = MSI supports 4 messages, 64 bit, vector masks cap 10[70] = PCI-Express 2 endpoint max data 128(128) link x1(x1) speed 2.5(2.5) ASPM disabled(L0s/L1) ecap 0001[100] = AER 1 0 fatal 0 non-fatal 1 corrected ecap 0002[140] = VC 1 max VC0 ecap 0003[300] = Serial 1 root@Border:~ # root@Border:~ # kenv | grep smbios smbios.bios.reldate="04/28/2009" smbios.bios.vendor="Phoenix Technologies, LTD" smbios.bios.version="ASUS StrikerExtreme ACPI BIOS Revision 1901" smbios.chassis.maker="Chassis Manufacture" smbios.chassis.serial="EVAL " smbios.chassis.tag="123456789000" smbios.chassis.version="Chassis Version" smbios.memory.enabled="8388608" smbios.planar.maker="ASUSTeK Computer INC." smbios.planar.product="StrikerExtreme" smbios.planar.serial="123456789000" smbios.planar.version="1.XX" smbios.socket.enabled="1" smbios.socket.populated="1" smbios.system.maker="System manufacturer" smbios.system.product="System Product Name" smbios.system.serial="System Serial Number" smbios.system.uuid="becbf4de-e6e7-53eb-eafa-1c0fc0145223" smbios.system.version="System Version" smbios.version="2.4" root@Border:~ # root@Border:~ # ifconfig re0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:14:d1:25:d8:23 inet 99.55.241.27 netmask 0xfc00 broadcast 99.55.243.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active re1: flags=8843 metric 0 mtu 1500 options=8209b ether 00:14:d1:25:d8:44 inet 192.168.12.1 netmask 0xff00 broadcast 192.168.12.255 inet6 fe80::214:d1ff:fe25:d844%re1 prefixlen 64 scopeid 0x2 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active nfe0: flags=8802 metric 0 mtu 1500 options=c219b ether 00:1a:92:46:e0:44 nd6 options=29 media: Ethernet autoselect (none) status: no carrier nfe1: flags=8843 metric 0 mtu 1500 options=c219b ether 00:1a:92:46:ed:f7 inet 75.133.75.194 netmask 0xfff8 broadcast 75.133.75.199 inet6 fe80::21a:92ff:fe46:edf7%nfe1 prefixlen 64 scopeid 0x4 nd6 options=29 media: Ethernet autoselect (1000baseT ) status: active ath0: flags=8843 metric 0 mtu 2290 ether 7c:c3:a1:b3:fc:af nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running lo0: flags=8049 metric 0 mtu 16384 options=63 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x6 inet 127.0.0.1 netmask 0xff00 nd6 options=21 wlan0: flags=8843 metric 0 mtu 1500 ether 7c:c3:a1:b3:fc:af inet 192.168.13.1 netmask 0xff00 broadcast 192.168.13.255 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: running ssid BlackBox channel 6 (2437 MHz 11g ht/20) bssid 7c:c3:a1:b3:fc:af regdomain 100 indoor ecm authmode OPEN privacy OFF txpower 20 scanvalid 60 protmode RTSCTS ampdulimit 64k ampdudensity 8 shortgi wme burst dtimperiod 15 -dfs bintval 1000 pflog0: flags=141 metric 0 mtu 33152 nd6 options=9 root@Border:~ # -- Sam Fourman Jr. ___ 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"
Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
= supervisor read data, page not present instruction pointer = 0x20:0x809937a8 stack pointer = 0x28:0xff8000278870 frame pointer = 0x28:0xff80002788c0 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 12 (swi4: clock) trap number = 12 panic: page fault cpuid = 0 Uptime: 23h57m13s Dumping 2452 out of 8070 MB:^@^@^@^@^@^@^@^@^@^@^@^@^@^ -- Kernel config is as follows... root@Border:/var/crash # cat /usr/src/sys/amd64/conf/BORDER include GENERIC nocpu i486_CPU ident BORDER nooptions WITNESS nooptions INVARIANTS nodeviceeisa nodevicefdc nooptions SCTP #Pretty console options SC_NORM_ATTR=(FG_GREEN|BG_BLACK) options SC_NORM_REV_ATTR=(FG_YELLOW|BG_GREEN) options SC_KERNEL_CONS_ATTR=(FG_LIGHTRED|BG_BLACK) options SC_KERNEL_CONS_REV_ATTR=(FG_BLACK|BG_RED) options SC_HISTORY_SIZE=8192 # Firewalling device pf device pflog options ROUTETABLES=6 options ALTQ options ALTQ_HFSC options ALTQ_NOPCC options IPSTEALTH # The nullFS to mount local directory options NULLFS # VIMAGE stuff #makeoptions NO_MODULES=yes #options VIMAGE options NETGRAPH options NETGRAPH_ETHER options NETGRAPH_BRIDGE options NETGRAPH_EIFACE options NETGRAPH_SOCKET device epair device if_bridge # Atheros Wireless NIC card options options AH_DEBUG options ATH_DEBUG options ATH_DIAGAPI nodevicebwn nodevicebwi # Delete Sound support nodevice sound # Generic sound driver (required) nodevice snd_cmi # CMedia CMI8338/CMI8738 nodevice snd_csa # Crystal Semiconductor CS461x/428x nodevice snd_emu10kx # Creative SoundBlaster Live! and Audigy nodevice snd_es137x # Ensoniq AudioPCI ES137x nodevice snd_hda # Intel High Definition Audio nodevice snd_ich # Intel, NVidia and other ICH AC'97 Audio nodevice snd_via8233 # VIA VT8233x Audio root@Border:/var/crash # Sam Fourman Jr. ___ 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: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
On Sun, Aug 4, 2013 at 6:52 PM, Craig Rodrigues wrote: > On Sun, Aug 4, 2013 at 12:33 PM, Sam Fourman Jr. wrote: > >> hello list, >> >> could someone help me figure out why this machine kernel paniced? >> I have a full crashdump file if needed, >> this machine is configured as a Firewall and wifi hostap running pf in a >> small office >> >> >> here is a mailing list post to someone that had a similar problem a few >> years back >> http://lists.freebsd.org/pipermail/freebsd-bugs/2011-April/043985.html >> >> a backtrace, full dmesg, and kernel config are below >> >> >> kgdb /boot/kernel/kernel /var/crash/vmcore.0 >> #4 0x80bd6027 in trap_pfault (frame=0x0, usermode=> optimized >> out>) at /usr/src/sys/amd64/amd64/trap.c:699 >> #5 0x80bd5876 in trap (frame=0xff80002787c0) at >> /usr/src/sys/amd64/amd64/trap.c:463 >> #6 0x80bc06b2 in calltrap () at >> /usr/src/sys/amd64/amd64/exception.S:232 >> #7 0x809937a8 in in6_tmpaddrtimer (arg=0xfe00170fc0b6) at >> /usr/src/sys/netinet6/in6_ifattach.c:935 >> #8 0x8085140a in softclock_call_cc (c=0x81325210, >> cc=0x8131c700, direct=0) at /usr/src/sys/kern/kern_timeout.c:674 >> #9 0x80851704 in softclock (arg=) at >> /usr/src/sys/kern/kern_timeout.c:802 >> #10 0x80815dc3 in intr_event_execute_handlers (p=> out>, ie=0xfe0014ab3400) at /usr/src/sys/kern/kern_intr.c:1263 >> #11 0x80816716 in ithread_loop (arg=0xfe0014a896e0) at >> /usr/src/sys/kern/kern_intr.c:1276 >> #12 0x80813b31 in fork_exit (callout=0x80816680 >> , arg=0xfe0014a896e0, frame=0xff8000278a40) at >> /usr/src/sys/kern/kern_fork.c:991 >> #13 0x80bc0bee in fork_trampoline () at >> /usr/src/sys/amd64/amd64/exception.S:606 >> #14 0x in ?? () >> Current language: auto; currently minimal >> (kgdb) >> >> >> > > You have VIMAGE enabled in your kernel config. I have debugged a few of > these VIMAGE problems > before. > > Can you do the following for me: > > Craig, Thank you for getting back to me, I will get to work on this right away and get you what you need. but are we CERTAIN this panic could be from VIMAGE? I totally thought I had a # infront of that line when I built this kernel... if you notice I did post the kernel config at the bottom of that email, and VIMAGE is NOT included... but maybe I did something wrong and somehow built VIMAGE in anyway.. is there some sort of command I can run to ask the system if it does indeed have VIMAGE? -- Sam Fourman Jr. ___ 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: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
> Can you try to update the kernel to r253950 or later? This is > probably because one of my recent commits broke IPv6 temporary > address timer on non-IPv6 interfaces. > > -- Hiroki > I just built a kernel based on r253950, I will keep the list updated if the panic happens again -- Sam Fourman Jr. ___ 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: Linux epoll(7) patch
> The glory days of the Linuxulator were around FreeBSD 6 when basically > everything ran and often it ran much faster. We could really use a > revival of this with the FreeBSD 10 release... > ___ > 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" > epoll is needed to get the linux version of plex media server working in FreeNAS, however in the last month or so it looks as if a FreeBSD native app has been released also I believe Yuri is working on a Linuxulator refresh up to at least Fedora 19 -- Sam Fourman Jr. ___ 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: LOR on head ...
pcib6: at device 20.4 on pci0 pci6: on pcib6 re1: port 0xd100-0xd1ff mem 0xfe141000-0xfe1410ff irq 20 at device 5.0 on pci6 re1: Chip rev. 0x1000 re1: MAC rev. 0x miibus1: on re1 rgephy1: PHY 1 on miibus1 rgephy1: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re1: Ethernet address: 00:14:d1:25:d8:23 re2: port 0xd000-0xd0ff mem 0xfe14-0xfe1400ff irq 21 at device 6.0 on pci6 re2: Chip rev. 0x1000 re2: MAC rev. 0x miibus2: on re2 rgephy2: PHY 1 on miibus2 rgephy2: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re2: Ethernet address: 00:14:d1:25:d8:44 ohci2: mem 0xfe506000-0xfe506fff irq 18 at device 20.5 on pci0 usbus6 on ohci2 ohci3: mem 0xfe505000-0xfe505fff irq 22 at device 22.0 on pci0 usbus7 on ohci3 ehci2: mem 0xfe504000-0xfe5040ff irq 23 at device 22.2 on pci0 usbus8: EHCI version 1.0 usbus8 on ehci2 acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: cannot reserve I/O port range acpi_throttle0: on cpu0 hwpstate0: on cpu0 acpi_throttle1: on cpu1 acpi_throttle1: failed to attach P_CNT device_attach: acpi_throttle1 attach returned 6 acpi_throttle2: on cpu2 acpi_throttle2: failed to attach P_CNT device_attach: acpi_throttle2 attach returned 6 acpi_throttle3: on cpu3 acpi_throttle3: failed to attach P_CNT device_attach: acpi_throttle3 attach returned 6 ZFS filesystem version: 5 ZFS storage pool version: features support (5000) Timecounters tick every 1.000 msec usbus0: 5.0Gbps Super Speed USB v3.0 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 usbus4: 12Mbps Full Speed USB v1.0 usbus5: 480Mbps High Speed USB v2.0 usbus6: 12Mbps Full Speed USB v1.0 usbus7: 12Mbps Full Speed USB v1.0 usbus8: 480Mbps High Speed USB v2.0 ugen0.1: <0x1b21> at usbus0 uhub0: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus0 ugen3.1: at usbus3 uhub1: on usbus3 ugen2.1: at usbus2 uhub2: on usbus2 ugen1.1: <0x1b21> at usbus1 uhub3: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ugen6.1: at usbus6 uhub4: on usbus6 ugen5.1: at usbus5 uhub5: on usbus5 ugen4.1: at usbus4 uhub6: on usbus4 ugen8.1: at usbus8 uhub7: on usbus8 ugen7.1: at usbus7 uhub8: on usbus7 ada0 at ahcich0 bus 0 scbus0 target 0 lun 0 ada0: ATA-7 SATA 1.x device ada0: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) ada0: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad4 ada1 at ahcich2 bus 0 scbus1 target 0 lun 0 ada1: ATA-7 SATA 1.x device ada1: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad6 ada2 at ahcich5 bus 0 scbus2 target 0 lun 0 ada2: ATA-7 SATA 1.x device ada2: 150.000MB/s transfers (SATA 1.x, UDMA6, PIO 8192bytes) ada2: 38166MB (78165360 512 byte sectors: 16H 63S/T 16383C) ada2: Previously was known as ad8 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Timecounter "TSC-low" frequency 1800148234 Hz quality 1000 uhub4: 2 ports with 2 removable, self powered uhub8: 4 ports with 4 removable, self powered uhub6: 5 ports with 5 removable, self powered uhub2: 5 ports with 5 removable, self powered uhub0: 4 ports with 4 removable, self powered uhub3: 4 ports with 4 removable, self powered GEOM: ada2: the secondary GPT table is corrupt or invalid. GEOM: ada2: using the primary only -- recovery suggested. GEOM: diskid/DISK-MDT-MCANKK515312: the secondary GPT table is corrupt or invalid. GEOM: diskid/DISK-MDT-MCANKK515312: using the primary only -- recovery suggested. Root mount waiting for: usbus8 usbus5 usbus3 Root mount waiting for: usbus8 usbus5 usbus3 uhub7: 4 ports with 4 removable, self powered uhub5: 5 ports with 5 removable, self powered uhub1: 5 ports with 5 removable, self powered Trying to mount root from zfs:Puffy []... ugen4.2: at usbus4 ukbd0: on usbus4 kbd2 at ukbd0 ar9300_Stub_GetCTSTimeout: called ar9300_Stub_GetCTSTimeout: called ar9300_Stub_GetAntennaSwitch: called ar9300_Stub_GetAntennaSwitch: called wlan0: Ethernet address: 7c:c3:a1:b3:fc:af uhid0: on usbus4 uhid1: on usbus4 root@Border:~ # uptime 11:20PM up 15:06, 1 user, load averages: 0.34, 0.33, 0.25 -- Sam Fourman Jr.
Re: Kernel Panic on FreeBSD 10.0-CURRENT #1 r253918
I forgot to mention, sysctl kern.conftxt > will only display something if you have this in your kernel config: > > options INCLUDE_CONFIG_FILE # Include this file in kernel > > It's always handy to have that in your kernel config. > > -- > Craig > No wonder why, it wasn't working for me and I didn't know why -- Sam Fourman Jr. ___ 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: Light humour
On Sat, Apr 27, 2013 at 6:31 PM, Paul Webster wrote: > Just got this link on IRC, (freenode/##freebsd) was so funny I thought > I would see if I could get any of you guys to spit out you're coffee > :) > > http://antibsd.wordpress.com/ > ___ Sorry I am REALLY late to this party, but wow this site made me laugh :) I straight up choked on my soda...... -- Sam Fourman Jr. ___ 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: Light humour
On Sat, Aug 10, 2013 at 7:07 PM, Sam Fourman Jr. wrote: > On Sat, Apr 27, 2013 at 6:31 PM, Paul Webster > wrote: >> Just got this link on IRC, (freenode/##freebsd) was so funny I thought >> I would see if I could get any of you guys to spit out you're coffee >> :) >> >> http://antibsd.wordpress.com/ >> ___ > > > Sorry I am REALLY late to this party, but wow this site made me laugh :) > I straight up choked on my soda.. > -- > > Sam Fourman Jr. he changed the link... http://aboutthebsds.wordpress.com/ -- Sam Fourman Jr. ___ 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: ZFS Crashes
> same hardware was ROCK STABLE till this weekend. > Larry, it would help if you had a svn revision #, for what it is worth, I had a machine that was crashing all over the place, after r254141 a fresh svnlite up and new kernel r254196 seems to have fixed my problem atleast... -- Sam Fourman Jr. ___ 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: ZFS Crashes
> The SVN rev was AWOL from the uname till this AM. > Oh snap you are right, I didn't even notice uname -a lost the rev # looks like I have some compiling to do :) -- Sam Fourman Jr. ___ 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: GCC withdraw
> If the 150 ports that only work with gcc, all work with a ports > > gcc and do not need the gcc from base, would the following be OK ? > > > > - 9.x gcc default and clang in base; > > - 10.x clang default and gcc in ports; > > Well, we write rules and we brake them. ;-) > > Just say that we know we brake them but it's inevitable because... > And go futher. > I am not a developer, just a user, so I am not versed in all of the issues but I would REALLY like to see gcc moved to ports for 10.x In my opinion this just needs to happen, if ports break, we deal with that on a case by case basis. FreeBSD as a community made the decision to move to clang as a compiler, and moving gcc to ports enforces that decision, I prefer the "rip the band aid off" approach because it brings issues to light faster, and now people have real reasons to fix things. Now, I am aware that other architectures like ARM etc. need gcc in base for basic things like building kernel/world, because clang cant do this yet. Maybe this is over simplifying it a bit but can't we just modify scripts in some way to pull gcc from ports into base, for these platforms at build time? SVN *is* in base now (svnlite) >From an outside look at this, it seems to me that we're holding back the amd64 platform just because the developer activity is a little more sparse than we would prefer on other platforms. Other platforms are important and they are needed, but those platforms are the ones that need patched up, they are the ones that need the band-aids implemented so that gcc still works for them. So I vote, let's not give ourselves the burden of "lugging" dead weight in base for another 5 years. (in 2017 do we still want to be worrying about gcc in base?) So in the name of progress, let's make a comfortable final resting place for gcc in our ports tree and look to clang for our future. Thoughts, Sam Fourman Jr. ___ 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: GCC withdraw
> In my opinion this just needs to happen, if ports break, we deal with that > > on a case by case basis. > > Oh, I remember. mplayer on i386 can't be builded witch clang -- clang > don't understand inlined asm. > > Well, in this case, you would just have the mplayer maintainer configure the port to use gcc for the i386 build of mplayer... problem solved -- Sam Fourman Jr. ___ 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 to add AES intrinsics to gcc
On Sat, Aug 24, 2013 at 12:33 PM, Adrian Chadd wrote: > You know, I could be a total jerk and say: > > "If you push gcc out to a port, and you have the 'external compiler' > toolchain support working correctly enough to build with this, why don't we > just push clang out to a port, and be done with it?" > > ... just saying. +1 GREAT idea!!! that is a better plan for 11.x -- Sam Fourman Jr. ___ 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: 2 crashes.... (today's -CURRENT)
On Sat, Aug 24, 2013 at 6:47 PM, Larry Rosenman wrote: > Both full core.txt's are available at: > > http://www.lerctr.org/~ler/**FreeBSD/<http://www.lerctr.org/~ler/FreeBSD/> > > Larry, I am not certain I can be of much help but i am curious what hardware you have. do you have a full dmesg? i went back in your previous post and i didn't see one. Sam Fourman Jr. ___ 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"
LSI SAS2008 mps(4) 4TB disk only shows 2TB on CURRENT r255089
Hello list I have two issues that may in fact be both related to the LSI SAS2008 card or the mps(4) driver. this server is running FreeBSD 10.0-CURRENT #0 r255089 1) All of the SSD disks are showing up at SATA2 300MB's but the card is in fact a 6GB Sata3 card.. 2) a Westren Digital 4TB disk only shows 2TB (connected to the LSI controller) full dmesg here https://gist.github.com/sfourman/6399419 full pciconf here https://gist.github.com/sfourman/6399454 Below is some disk info, $ sudo camcontrol identify da6 pass6: ATA-8 SATA 3.x device pass6: 300.000MB/s transfers, Command Queueing Enabled protocol ATA/ATAPI-8 SATA 3.x device model WDC WD4000FYYZ-01UL1B0 firmware revision 01.01K01 serial number WD-WCC130721596 WWN 50014ee25de95b67 cylinders 16383 heads 16 sectors/track 63 sector size logical 512, physical 512, offset 0 LBA supported 268435455 sectors LBA48 supported 7814037168 sectors PIO supported PIO4 DMA supported WDMA2 UDMA6 media RPM 7200 Feature Support Enabled Value Vendor read ahead yes yes write cacheyes yes flush cacheyes yes overlapno Tagged Command Queuing (TCQ) no no Native Command Queuing (NCQ) yes 32 tags SMART yes yes microcode download yes yes security yes no power management yes yes advanced power management yes yes 128/0x80 automatic acoustic management no no media status notification no no power-up in Standbyyes no write-read-verify no no unload yes yes free-fall no no Data Set Management (DSM/TRIM) no Host Protected Area (HPA) yes no 7814037168/7814037168 HPA - Security no $ sudo gpart create -s gpt /dev/da6 da6 created $ gpart show => 34 234441581 da0 GPT (111G) 341281 freebsd-boot (64k) 162 2243951362 freebsd-ufs (107G) 22439529883886083 freebsd-swap (4.0G) 2327839061657709 - free - (809M) =>34 4294967227 da6 GPT (2T) 34 4294967227 - free - (2T) $ sudo gpart add -a 4k -t freebsd-zfs -l backup da6 da6p1 added $ $ $ $ $ $ gpart show => 34 234441581 da0 GPT (111G) 341281 freebsd-boot (64k) 162 2243951362 freebsd-ufs (107G) 22439529883886083 freebsd-swap (4.0G) 2327839061657709 - free - (809M) =>34 4294967227 da6 GPT (2T) 34 6 - free - (3.0k) 40 42949672161 freebsd-zfs (2T) 4294967256 5 - free - (2.5k) -- Sam Fourman Jr. ___ 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: LSI SAS2008 mps(4) 4TB disk only shows 2TB on CURRENT r255089
On Sat, Aug 31, 2013 at 1:07 PM, Sam Fourman Jr. wrote: > Hello list > > I have two issues that may in fact be both related to the LSI SAS2008 card > or > the mps(4) driver. > > this server is running FreeBSD 10.0-CURRENT #0 r255089 > > > 1) All of the SSD disks are showing up at SATA2 300MB's > but the card is in fact a 6GB Sata3 card.. > > 2) a Westren Digital 4TB disk only shows 2TB (connected to the LSI > controller) > > full dmesg here > https://gist.github.com/sfourman/6399419 > > full pciconf here > https://gist.github.com/sfourman/6399454 > > > > Below is some disk info, > > > $ sudo camcontrol identify da6 > pass6: ATA-8 SATA 3.x device > pass6: 300.000MB/s transfers, Command Queueing Enabled > > protocol ATA/ATAPI-8 SATA 3.x > device model WDC WD4000FYYZ-01UL1B0 > firmware revision 01.01K01 > serial number WD-WCC130721596 > WWN 50014ee25de95b67 > cylinders 16383 > heads 16 > sectors/track 63 > sector size logical 512, physical 512, offset 0 > LBA supported 268435455 sectors > LBA48 supported 7814037168 sectors > PIO supported PIO4 > DMA supported WDMA2 UDMA6 > media RPM 7200 > > Feature Support Enabled Value Vendor > read ahead yes yes > write cacheyes yes > flush cacheyes yes > overlapno > Tagged Command Queuing (TCQ) no no > Native Command Queuing (NCQ) yes 32 tags > SMART yes yes > microcode download yes yes > security yes no > power management yes yes > advanced power management yes yes 128/0x80 > automatic acoustic management no no > media status notification no no > power-up in Standbyyes no > write-read-verify no no > unload yes yes > free-fall no no > Data Set Management (DSM/TRIM) no > Host Protected Area (HPA) yes no 7814037168/7814037168 > HPA - Security no > $ > > > sudo gpart create -s gpt /dev/da6 > da6 created > $ gpart show > => 34 234441581 da0 GPT (111G) > 341281 freebsd-boot (64k) > 162 2243951362 freebsd-ufs (107G) > 22439529883886083 freebsd-swap (4.0G) > 2327839061657709 - free - (809M) > > =>34 4294967227 da6 GPT (2T) > 34 4294967227 - free - (2T) > > > $ sudo gpart add -a 4k -t freebsd-zfs -l backup da6 > da6p1 added > $ > $ > $ > $ > $ > $ gpart show > => 34 234441581 da0 GPT (111G) > 341281 freebsd-boot (64k) > 162 2243951362 freebsd-ufs (107G) > 22439529883886083 freebsd-swap (4.0G) > 2327839061657709 - free - (809M) > > => 34 4294967227 da6 GPT (2T) > 34 6 - free - (3.0k) > 40 42949672161 freebsd-zfs (2T) > 4294967256 5 - free - (2.5k) > -- > > Sam Fourman Jr. > is it possible that the problem is in the cam layer and not the mps(4) driver? -- Sam Fourman Jr. ___ 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"
Regression with nfe interface since r219740
Hello list, Running FreeBSD 9 amd64, I have found a regression, after r219740 assigning a ip address to my nfe interface will completely hard lock the entire machine. both static and dhclient lock the machine. I have spent some time to bisect the kernel and everything works as expected with a r219739 kernel , r219740 breaks it. here is some information about my system http://www.puffybsd.com/FreeBSDinfo.txt -- Sam Fourman Jr. Fourman Networks http://www.fourmannetworks.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"
