freebsd-current mailing list

FromSubjectsort iconDate
Sam Fourman Jr.
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 ...
Oct 19, 1:36 pm 2010
FreeBSD Tinderbox
[head tinderbox] failure on sparc64/sun4v
TB --- 2010-10-19 04:03:09 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-10-19 04:03:09 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2010-10-19 04:03:09 - cleaning the object tree TB --- 2010-10-19 04:04:56 - cvsupping the source tree TB --- 2010-10-19 04:04:56 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2010-10-19 04:09:53 - building world TB --- 2010-10-19 04:09:53 - MAKEOBJDIRPREFIX=/obj TB --- 2010-10-19 04:09:53 ...
Oct 19, 3:16 am 2010
FreeBSD Tinderbox
[head tinderbox] failure on powerpc64/powerpc
TB --- 2010-10-19 01:15:02 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-10-19 01:15:02 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2010-10-19 01:15:02 - cleaning the object tree TB --- 2010-10-19 01:17:08 - cvsupping the source tree TB --- 2010-10-19 01:17:08 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2010-10-19 01:21:43 - building world TB --- 2010-10-19 01:21:43 - MAKEOBJDIRPREFIX=/obj TB --- 2010-10-19 ...
Oct 19, 3:05 am 2010
FreeBSD Tinderbox
[head tinderbox] failure on sparc64/sparc64
TB --- 2010-10-19 01:55:54 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-10-19 01:55:54 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-10-19 01:55:54 - cleaning the object tree TB --- 2010-10-19 01:58:17 - cvsupping the source tree TB --- 2010-10-19 01:58:17 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2010-10-19 02:03:02 - building world TB --- 2010-10-19 02:03:02 - MAKEOBJDIRPREFIX=/obj TB --- 2010-10-19 ...
Oct 19, 1:22 am 2010
Andrey V. Elsukov
Re: [zfs] Mounting from (...) failed with error 19
It is ZFS-only system and I have this line in /boot/loader.conf: vfs.root.mountfrom="zfs:zroot" With "boot -a -v -s" I got the same result that with "boot -s -v" but when I enter zfs:zroot in mountroot prompt it printed: Trying to mount root from zfs:zroot []... mountroot: waiting for device zroot ... Mounting from zfs:zroot failed with error 19. Trying to mount root from zfs:zroot []... mountroot: waiting for device zroot ... Mounting from zfs:zroot failed with error 19. panic: ...
Oct 19, 9:24 am 2010
Andrey V. Elsukov
Re: [zfs] Mounting from (...) failed with error 19
Yes, i have the same problem. -- WBR, Andrey V. Elsukov
Oct 18, 10:03 pm 2010
Andrey V. Elsukov
Re: [zfs] Mounting from (...) failed with error 19
I fixed it with attached patch. -- WBR, Andrey V. Elsukov
Oct 19, 7:55 am 2010
Marcel Moolenaar
Re: [zfs] Mounting from (...) failed with error 19
Makes sense. "tank" (or its namesake) isn't a real device. Feel free to commit to unbreak things, but we may want to rethink this from a generality point of view. Listing exceptions doesn't scale and we now have 2 (the first was the empty device name as used by nfs, and now also zfs). Good catch, BTW. -- Marcel Moolenaar xcllnt@mac.com _______________________________________________ freebsd-current@freebsd.org mailing ...
Oct 19, 8:49 am 2010
KOT MATPOCKuH
Re: [zfs] Mounting from (...) failed with error 19
I think you forgot to load zpool.cache: load -t /boot/zfs/zpool.cache /boot/zfs/zpool.cache _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 12:50 pm 2010
Marcel Moolenaar
Re: [zfs] Mounting from (...) failed with error 19
Interesting. I've been thinking about this too, but isn't exactly fool-proof. When devfs is the root file system, you can use "ufs:da0s1a" to refer to the device special file. It seems inconsistent to have "ufs:da0s1" fail when ufs:/dev/da0s1" works (a real scenario with USB based mass storage devices -- root mount is unheld as soon as umass is created, but before daX exists for it). This patch at least covers the problem cases with a single strstr(), and we may get away with the ...
Oct 19, 3:33 pm 2010
Xin LI
Re: [zfs] Mounting from (...) failed with error 19
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Yes good catch, it fixed the problem for me as well. What about the attached patch? I'm going to give it a swirl soon. The difference is that it tests whether dev begins with /dev/. Note that I'm not quite convinced with this yet as we may want to wait for the devices from a zpool be ready, which may also need some yielding during boot. A better way of solving this might be to register a "watchlist" of devices (so that ZFS can register ...
Oct 19, 2:21 pm 2010
Marcel Moolenaar
Re: [zfs] Mounting from (...) failed with error 19
Can you both boot verbose and send me the output. Also, please boot with -a and show me the console output, as well as the output of the '?' command. Thanks, -- Marcel Moolenaar xcllnt@mac.com _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 8:43 am 2010
KOT MATPOCKuH
Re: [zfs] Mounting from (...) failed with error 19
On my sparc64 system with today kernel I also got this problem. With old kernel system boots properly. boot -sv log attached. -- MATPOCKuH
Oct 19, 11:16 am 2010
Andriy Gapon
Re: c 213323 breaks Sony Vaio P11Z w/o acpi
Definitely not - it violates style(9). Kidding, of course :-) Could you please download and run the following script and send back output? http://people.freebsd.org/~jkim/cpu_topology-12212009.sh Thank you very much! -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 18, 9:56 pm 2010
John Baldwin
Re: uma_zfree(NULL) is broken
Given that free(3) and free(9) both handle NULL, I think it makes sense for uma_zfree() to do so as well. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 5:55 am 2010
Alexander Best
Re: CPU report in first line of "vmstat 1" is meaningless
...also vmstat seems to exist in a few other OSes (linux e.g). maybe they've fixed it already (or the netbsd/openbsd/dragonflybsd folks or apple?). cheers. -- a13x _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 18, 5:13 pm 2010
John Baldwin
Re: CPU report in first line of "vmstat 1" is meaningless
All of the first line is that way though. To do this "right" you'd need to blank out the entire first line. vm_stat and iostat on OS X have the current FreeBSD behavior (instant first line that summarizes all activity since uptime), so I'd be inclined to just leave the existing behavior. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to ...
Oct 19, 5:54 am 2010
John Baldwin
Re: CPU report in first line of "vmstat 1" is meaningless
I would be fine with that, but I wouldn't alter the format of that line by default. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 8:23 am 2010
Alexander Best
Re: CPU report in first line of "vmstat 1" is meaningless
don't know if you have seen this, but this behavior has been documented in a PR back in 2001: http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/30360 cheers. -- a13x _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 18, 5:11 pm 2010
Lars Engels
Re: CPU report in first line of "vmstat 1" is meaningless
I'd be very happy if all vmstat and iostat would get a command line switch to suppress the "summary since last reboot" line. This information may be useful for some cases but in other cases, like creating performance data for monitoring systems like Icinga / Nagios one has to remove the first line(s) manually.
Oct 19, 7:40 am 2010
Gavin Atkinson
Re: wpa_supplicant and ssid
This appears to be the same as the bug reported in PR bin/98220. wpa_supplicant is contributed code, so I think the correct answer is to report this upstream. As far as I could tell when I last checked, this hasn't yet been fixed upstream. Gavin -- Gavin Atkinson FreeBSD committer and bugmeister GPG: A093262B (313A A79F 697D 3A5C 216A EDF5 935D EF44 A093 262B) _______________________________________________ freebsd-current@freebsd.org mailing ...
Oct 19, 7:04 am 2010
Bernhard Schmidt
Re: wpa_supplicant and ssid
You can add a 'priority' statement to each network block in Before doing so, can you capture the output of 'wlandebug 0xffffffff' while trying to get a connection? -- Bernhard _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 18, 11:30 pm 2010
Scott Long
Re: mfiutil reports "PSTATE 0x0020" new drive state
In all fairness, we're talking about an information reporting attribute, not an action attribute. And yes, most of us in this discussion have been writing device drivers and working with vendors for years. Scott _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 7:16 am 2010
Sergey Kandaurov
Re: mfiutil reports "PSTATE 0x0020" new drive state
Hi, John. I've no such access unfortunately. As for FreeBSD vendor's driver, it doesn't list PD states at all (and looks like their version lags behind other OS versions). However, they (LSI) are listing COPYBACK entry as 0x20 in its Linux driver, and there: http://lkml.org/lkml/2009/5/5/389 -- wbr, pluknet _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail ...
Oct 19, 7:05 am 2010
John Baldwin
Re: mfiutil reports "PSTATE 0x0020" new drive state
Ok. You should add the SYSTEM state too (0x40) while you are at it. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 7:11 am 2010
John Baldwin
Re: mfiutil reports "PSTATE 0x0020" new drive state
If you have access to the MFI docs (or a reference in the Linux driver, e.g.) then this is fine. The existing pd_state enum lists the values for PD state that were listed in the MFI docs I had access to at the time I wrote mfiutil. -- John Baldwin _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 5:49 am 2010
David Naylor
Re: geom_sched usage
Would there be any interest in having a rc.d/ script? I would find it conveniant to specify a single rc.conf line and get scheduling for all my devices. PC-BSD might find such functionality useful. See attached for my first draft at such a script, I'm willing to hash it into Is there a manual page that describes these sysctls? It looks like, in my case, scp just hogs resources. Thanks for clarity. Regards, David
Oct 18, 11:07 pm 2010
Miroslav Lachman
Re: geom_sched usage
[...] You can use `sysctl kern.disks` to find available disk devices in your rc script. Miroslav Lachman _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 6:20 am 2010
Luigi Rizzo
Re: geom_sched usage
it would surely be useful but try to keep it simple and user-driven (this is a general comment on rc.d scripts). Some things i think you should simplify in your script: - remove support for guessing which devices should get the scheduler. This is really a user decision and if the user names no devices then i believe it is better/safer not to install any scheduler. - use standard names such as gsched_flags or gsched_flags_${dev} to hold generic and specific flags for the insert command. ...
Oct 19, 1:18 am 2010
Rui Paulo
Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
cd /usr/ports/*/postgres90-server make clean export DTRACE_DEBUG=1 make install Check what dtrace is doing. BTW have you added postgres to the wheel group? Regards, -- Rui Paulo _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 12:18 am 2010
Rui Paulo
Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
Send me the build log, gzipped. Regards, -- Rui Paulo _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 2:33 am 2010
Robert Watson
Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
In the medium term, part of the solution here will be to finish adding a role-based privilege system. I had this on my todo list for 8.0 but didn't manage to get it finished. With any luck, it will make 9.0 in plenty of time. this would allow specific kernel privileges to be delegated to specific users and groups (among other things). Many of the kernel changes to support this have been done since 7.0 when I added priv(9), but we've not yet selected a specific policy and API to bind to ...
Oct 19, 3:00 am 2010
István
Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
and you think the only way to do that is to add pgsql to wheel group?!? yes sir yes! (and you are talking about ppl being rude) what file do you need and which directory ___excatly___ btw. it would be beneficial for you as the DTrace maintainer of FreeBSD to have your own environment and prove me that I am wrong since you are happily your own words: "Tracing and instrumenting userland programs is very important because it allows the understanding of what's going on, especially on ...
Oct 19, 2:53 am 2010
István
Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
you think adding pgsql to wheel might help? cc freebsd-security@ and see their opinion about the topic. i modified the permission of /dev/dtrace/helper instead but it gives the following error still: dtrace DOF postgres: DTrace ioctl failed for DOF at 0x801c35000: Invalid argument do you mean /usr/ports/databases/postgresql90-server? I was rebuilding it with that switch, what now? I. -- the sun shines for ...
Oct 19, 2:15 am 2010
Andriy Gapon
Re: panic in uma_startup for many-core amd64 system
Well, setting aside my confusion with the terminology - yes, the patch is just I agree in principle. But without seeing code that implements that I can't guess if it would really be more efficient or more maintainable, i.e. more useful in general. Still a very good idea. -- Andriy Gapon _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to ...
Oct 18, 11:55 pm 2010
Giovanni Trematerra
Re: panic in uma_startup for many-core amd64 system
I'm going to work on that. Unfortunately I think that could take a long time to me. I hope someone will have some insight to share. -- Giovanni Trematerra _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 19, 12:48 pm 2010
Jaakko Heinonen
Re: sysctl -a is slow
I couldn't reproduce the problem myself but I bet that it's a lost wakeup in g_waitfor_event(). Can you try this patch? %%% Index: sys/geom/geom_event.c =================================================================== --- sys/geom/geom_event.c (revision 214048) +++ sys/geom/geom_event.c (working copy) @@ -220,11 +220,12 @@ one_event(void) mtx_lock(&g_eventlock); TAILQ_REMOVE(&g_events, ep, events); ep->flag &= ~EV_INPROGRESS; - mtx_unlock(&g_eventlock); if (ep->flag & ...
Oct 19, 1:59 am 2010
Jack Vogel
Re: Regarding pciids
Questionable, you mean like Intel? :) I brought this up in the first place asking because our new ID's go direct into the sf list. I understand the desire to avoid churn, but I suspect this would be a change for the longer term good. Just my .02 Jack _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Oct 18, 11:37 pm 2010
previous daytodaynext day
October 18, 2010October 19, 2010October 20, 2010