| From | Subject | Date |
|---|---|---|
| Xin LI | [zfs] Mounting from (...) failed with error 19
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
With latest kernel I got:
Mounting from (...) failed with error 19
On boot. The system is using pure ZFS setup. It seems that 19 means
ENODEV but according to the dmesg the device do exist.
At the beginning I thought it was because that zpool.cache was destroyed
somehow, so I have tried to use LiveFS and mkdir /boot/zfs, hostid
start, zpool import -f, mount pool/root, and copy /boot/zfs/zpool.cache
over it but unluckily this ...
| Oct 18, 4:50 pm 2010 |
| volker | c 213323 breaks Sony Vaio P11Z w/o acpi
Hi Andriy & list!
Since rev 213323 my Sony Vaio P11Z was unable to boot up. It broke with
a divide by zero in topo_probe_0x4 at line 289 as cpu_logical is 0.
The cpu is an Intel Atom Z520 (single core). System doesn't boot at all
w/ acpi enabled.
The following patch made me to boot up again.
Index: i386/i386/mp_machdep.c
===================================================================
--- i386/i386/mp_machdep.c (revision 213936)
+++ i386/i386/mp_machdep.c (working copy)
@@ -286,7 ...
| Oct 18, 3:31 pm 2010 |
| mdf | uma_zfree(NULL) is broken
There's explicit protection for free(NULL, M_FOO), but uma_zfree(zone,
NULL) will put NULL in the local bucket and then probably return it
later from a uma_zalloc call. Obviously it's not a good idea to call
uma_zfree(9) on NULL, but in this case it's an easy mistake to make
when e.g. converting a set of malloc(9)/free(9) uses into uma(9).
So is the "right" thing to allow a uma_zfree(NULL) and silently
succeed, like for free(9)? That would be my guess, but I'm open ...
| Oct 18, 1:59 pm 2010 |
| Dan Nelson | Re: CPU report in first line of "vmstat 1" is meaningless
It is documented to do that, though, and could affect scripts that expect to
--
Dan Nelson
dnelson@allantgroup.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 18, 12:39 pm 2010 |
| Ed Maste | Re: CPU report in first line of "vmstat 1" is meaningless
Well, it won't roll over, but it's still different from all following
lines (in that it effectively shows user/system/idle CPU usage since
boot on the first line, and a snapshot over the last interval from then
on). I think it's still better to avoid printing it in that case.
On a related note I'm not sure if it makes sense to have the same
behaviour for the first line when an interval is set as when it is
invoked with no ...
| Oct 18, 12:30 pm 2010 |
| Dan Nelson | Re: CPU report in first line of "vmstat 1" is meaningless
Maybe only blank it out on 32-bit machines? It's a long, and a 64-bit
cp_time value essentially won't roll over (at 1 billion increments per
second it will roll over in 500 years; we currently increment 133 times per
second, I think). If the value can be calculated accurately, it should be
printed.
--
Dan Nelson
dnelson@allantgroup.com
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To ...
| Oct 18, 11:11 am 2010 |
| Ed Maste | CPU report in first line of "vmstat 1" is meaningless
The us/sy/id CPU usage numbers in the first line of vmstat are not useful,
because they're calculated based on kern.cp_times since boot, and not a
delta as are all subsequent lines. If the system has been up long enough
wrapping may come in to play, giving negative results. For example, on
one machine I see:
$ vmstat 1
procs memory page disks faults cpu
r b w avm fre flt re pi po fr sr da0 pa0 in sy cs us sy id
1 0 2 1097M 227M 101 ...
| Oct 18, 10:43 am 2010 |
| Buganini | wpa_supplicant and ssid
It seems that wpa_supplicant iterate through all scanned ssids and try to
associate with each,
and that cause two problem for me.
1) in my school, there are many AP, and connection is not stable, when
disconnect,
it take many time to try and fail to associate with those ssids until the
one I want.
2) i can't associate with a non-discoverable ssid
but probably it is my wireless driver's problem,
i'm using bwn0 and currently I need to force it to use mode 11b or it is
unusable.
or ...
| Oct 18, 9:55 am 2010 |
| Garrett Cooper | Re: mfiutil reports "PSTATE 0x0020" new drive state
Check with LSI before you commit that; you might not understand
the overall nuances of that value.
Thanks,
-Garrett
_______________________________________________
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, 10:25 am 2010 |
| Sergey Kandaurov | Re: mfiutil reports "PSTATE 0x0020" new drive state
So, it no one objects, I'd like to commit this change.
--
wbr,
pluknet
| Oct 18, 9:55 am 2010 |
| David Naylor | geom_sched usage
Hi,
I've used geom_sched to some success. Normally I do not notice anything but
today I was copying big files over a gigabit ethernet and my laptop was not
very responsive. I loaded gsched and the responsiveness improved (although
still rather bad for anything requiring something from the HDD).
Thank you for all this work :-)
Some questions I have:
- with a gmirror should the gsched be attached to the underlying devices (aka
/dev/ad?) or to the mirror device (aka ...
| Oct 18, 12:43 am 2010 |
| Luigi Rizzo | Re: geom_sched usage
no way to do that, but you can modify the quantum size and time to
let sequential reads get shorter chunks
kern.geom.sched.rr.quantum_kb: 8192
kern.geom.sched.rr.quantum_ms: 100
kern.geom.sched.rr.wait_ms: 10
e.g. on a laptop it might make sense to set
true, gsched_as was just a proof of concept and gsched_rr
includes anticipation and round robin, so it is a superset of gsched_as
cheers
luigi
_______________________________________________
freebsd-current@freebsd.org mailing ...
| Oct 18, 12:51 pm 2010 |
| Barbara | LOR vfs_lookup.c + ffs_softdep.c + vfs_subr.c
$ uname -a
FreeBSD satanasso.local.net 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Mon Oct 11 09:
10:51 CEST 2010 root@satanasso.local.net:/usr/obj/usr/src/sys/SATANASSO
i386
lock order reversal:
1st 0xc68ec278 ufs (ufs) @ /usr/src/sys/kern/vfs_lookup.c:501
2nd 0xd995fc70 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_softdep.c:11310
3rd 0xc6993278 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2111
KDB: stack backtrace:
db_trace_self_wrapper(c0914c5e,632e7262,3131323a,a0d31,70656474,...) at ...
| Oct 17, 11:35 pm 2010 |
| Barbara | LOR kern_sig.c + vm_kern.c
$ uname -a
FreeBSD satanasso.local.net 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Mon Oct 11 09:
10:51 CEST 2010 root@satanasso.local.net:/usr/obj/usr/src/sys/SATANASSO
i386
lock order reversal:
1st 0xc6befdd0 process lock (process lock) @ /usr/src/sys/kern/kern_sig.c:3341
2nd 0xc19b60e4 system map (system map) @ /usr/src/sys/vm/vm_kern.c:315
KDB: stack backtrace:
db_trace_self_wrapper(c0914c5e,762f7379,6d762f6d,72656b5f,3a632e6e,...) at ...
| Oct 17, 11:28 pm 2010 |
| Xin LI | Re: 2TB HDD = TIMEOUT - READ_DMA48 ....
Hi,
Have you tried the new ahci(4) driver? What controller are you using
by the way?
Cheers,
--
Xin LI <delphij@delphij.net> http://www.delphij.net
_______________________________________________
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 17, 8:58 pm 2010 |
| Peter Jeremy | Re: 2TB HDD = TIMEOUT - READ_DMA48 ....
You'll need to provide some more details such as how old your FreeBSD
8 is, drive model number, controller details and the actual error
message you are getting.
I recently bought a Hitachi Deskstar 7K2000, which is sitting in an
Astone enclosure (identifying as "Sunplus Technology Co.,Ltd.").
Unfortunately, I'm limited to USB2 whilst I wait for the correct eSATA
adapter. Whilst the first disk was DOA, its replacement is running
perfectly (though slowly) with my 2-week-old FreeBSD 8.1-stable. ...
| Oct 18, 1:02 pm 2010 |
| Andriy Gapon | Re: 2TB HDD = TIMEOUT - READ_DMA48 ....
Sounds like sector number possibly overflowing 32-bit integer.
--
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 17, 10:35 pm 2010 |
| István | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
what should I do with the Makefile exactly? I can't see any dtrace related
information in it.
_______________________________________________
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, 2:30 pm 2010 |
| Rui Paulo | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
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 18, 2:40 pm 2010 |
| István | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
Hey,
how come it doesn't work?
What are the necessary requirements for using dtrace on freebsd? Do you need
a library or something?
Do you know why Ruby has no dtrace bindings on Freebsd?
Thank you.
Istvan
--
the sun shines for all
http://blog.l1x.me
_______________________________________________
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, 1:12 pm 2010 |
| Rui Paulo | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
The Ruby port doesn't have DTrace support, but the PostgreSQL port has a DTrace option (only the latest postgresql port).
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 18, 11:45 am 2010 |
| Rui Paulo | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
Each software package has it's way of enabling DTrace during the build. Check the postgres90-server port for an example on how to add DTrace support to a port.
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 18, 2:33 pm 2010 |
| István | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
So there is no out of the box solution for FreeBSD to use DTrace for any
userland app.
Is there somebody in the FreeBSD team actively working on this?
I.
--
the sun shines for all
http://blog.l1x.me
_______________________________________________
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, 2:37 pm 2010 |
| István | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
I perfectly understand what you are saying and I have been DTracing on
Solaris many times.
Only problem here is that you don't get my point, but I try to explain it on
the level you can get it.
[root@freebsd9 /usr/ports/databases/postgresql90-server]# grep -iA3
WITH_DTRACE Makefile
. if defined(WITH_DTRACE)
CONFIGURE_ARGS+=--enable-dtrace
LDFLAGS+=-lelf
. endif
[root@freebsd9 /usr/ports/databases/postgresql90-server]# grep -i ...
| Oct 18, 2:48 pm 2010 |
| Garrett Cooper | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
1. I'd do clean install, not install clean to start from a consistent state.
2. What do the autoconf logs say about dtrace support being
enabled (make clean configure will provide that data with the least
number of cycles spent)?
Thanks,
-Garrett
_______________________________________________
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, 3:48 pm 2010 |
| István | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
Hey Garrett,
thanks for coming back to me.
1. I had make clean before I did make install clean.
2.
$ ./configure --with-libraries=/usr/local/lib
--with-includes=/usr/local/include --enable-thread-safety --with-openssl
--enable-dtrace --with-pam --enable-nls --prefix=/usr/local
--mandir=/usr/local/man --infodir=/usr/local/info/
--build=amd64-portbld-freebsd9.0
uname -v = FreeBSD 9.0-CURRENT #0: Fri Oct 8 21:09:20 UTC 2010
root@freebsd9:/usr/obj/usr/src/sys/DTRACE
configure:2820: ...
| Oct 18, 4:05 pm 2010 |
| Rui Paulo | Re: DTrace bindings are missing in FreeBSD 9.0 - CURRENT ...
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 18, 1:57 pm 2010 |
| Alexey Dokuchaev | Re: Is nvidia-driver 256.53 expected to work on -current?
Or install from ports, which also patch the driver to support -CURRENT.
./danfe
_______________________________________________
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 17, 6:56 pm 2010 |
| Garrett Cooper | Re: Is nvidia-driver 256.53 expected to work on -current?
I've given up on linux emulation support since 256.3x as it was
the factor that was causing lockups on my two machines.
Thanks,
-Garrett
_______________________________________________
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 17, 11:39 pm 2010 |
| Daniel Nebdal | Re: Is nvidia-driver 256.53 expected to work on -current?
For what it's worth, the newest nvidia driver in ports (256.53)
reliably freezes both my 8-STABLE and 9-CURRENT machine dead within
minutes (amd64 , KDE4 both with and without compositing, Geforce GT240
cards. The mouse stops moving, no keyboard input does anything, it
doesn't answer on the network.)
I haven't had time to look at it, so I'm using the nv driver for now.
--
Daniel Nebdal
_______________________________________________
freebsd-current@freebsd.org mailing ...
| Oct 18, 2:44 am 2010 |
| Doug Barton | Re: Is nvidia-driver 256.53 expected to work on -current?
Thanks. I tried again without linux support, no change, it still froze
up. I suppose I can try again tomorrow without any of the options
selected.
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover! http://SupersetSolutions.com/
Computers are useless. They can only give you answers.
-- Pablo Picasso
_______________________________________________
freebsd-current@freebsd.org mailing ...
| Oct 17, 11:54 pm 2010 |
| Doug Barton | Re: Is nvidia-driver 256.53 expected to work on -current?
Hmm. I had all the options off except linux. I'll try with your
combination and see if that improves things.
Thanks,
Doug
--
Breadth of IT experience, and | Nothin' ever doesn't change,
depth of knowledge in the DNS. | but nothin' changes much.
Yours for the right price. :) | -- OK Go
http://SupersetSolutions.com/
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To ...
| Oct 17, 6:16 pm 2010 |
| Marius Strobl | Re: bge0 does not work anymore
Sorry, it looks like it was my fault this time, should be fixed again
with r214012.
Marius
_______________________________________________
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, 1:38 am 2010 |
| Ivan Klymenko | Re: bge0 does not work anymore
В Mon, 18 Oct 2010 10:38:45 +0200
r214012.
Thank you! it worked! :)
_______________________________________________
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, 3:25 am 2010 |
| Buganini | Re: bge0 does not work anymore
my last known usable kernel revision is r213813
with r213920, leds are extinguished when executing dhclient
_______________________________________________
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 17, 6:32 pm 2010 |
| fidaj | Re: bge0 does not work anymore
I am using FreeBSD 9.0-CURRENT (amd64) on a DELL Latitude D630. With
todays kernel the driver 'bge0' does not work anymore. With kernel from
October 9th it does.
The network controller is a Broadcom NetXtreme Gigabit Ethernet, ASIC
rev. 0x00a002; CHIP ID 0x0000a0002; ASIC REV 0x0a; CHIP REV 0xa0; PCI-E.
The entry in /etc/rc.conf is 'ifconfig_bge0="DHCP".
Does anyone else observe this behaviour? Is there something I can try?
...
| Oct 18, 12:22 am 2010 |
| Alexander Best | Re: some camcontrol(8) cleanups
here's a slighly updated version without any whitespace diffs.
cheers.
alex
--
a13x
| Oct 18, 12:25 pm 2010 |
| Andriy Gapon | Re: panic in uma_startup for many-core amd64 system
Here is a simple solution that seems to work:
http://people.freebsd.org/~avg/uma-many-cpus.diff
Not sure if it's the best we can do.
--
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 17, 11:40 pm 2010 |
| Giovanni Trematerra | Re: panic in uma_startup for many-core amd64 system
I don't know if it makes sense I only want to raise a flag.
Is it safe to call kmem_malloc() before bucket_init() during
uma_startup() to reserve room for CPU caches?
Reading the top uma_int.h comment, it seems that the best way to
handle this issue
would be to implement and allow for dynamic slab sizes.
I'm also afraid that memory footprint will be larger than now.
--
Trematerra Giovanni
_______________________________________________
freebsd-current@freebsd.org mailing ...
| Oct 18, 6:40 am 2010 |
| Andriy Gapon | Re: panic in uma_startup for many-core amd64 system
Again, not sure if I follow you, I don't see relation between per-cpu caches and
Of course, but only by sizeof(pointer) per zone.
--
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, 7:18 am 2010 |
| Giovanni Trematerra | Re: panic in uma_startup for many-core amd64 system
Your patch seems just a work around about initial slab size where the
keg is backed.
Having dynamic slab sizes would allow to have the keg backed on a larger slab
without going OFFPAGE.
--
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 18, 2:01 pm 2010 |
| Alexander Best | Re: sysctl -a is slow
these are the results from the following script:
#!/bin/sh
TESTS="kern vm vfs net debug hw user p1003_1b compat security dev"
for i in $TESTS; do echo $i:; time sysctl $i > /dev/null; done
kern:
0,09 real 0,00 user 0,07 sys
vm:
0,05 real 0,00 user 0,05 sys
vfs:
0,00 real 0,00 user 0,00 sys
net:
0,01 real 0,01 user 0,00 sys
debug:
0,36 real 0,00 user 0,35 sys
hw:
...
| Oct 18, 3:56 pm 2010 |
| Alexander Best | Re: Regarding pciids
oh...and i think it would be a good idea to move from ";" as comment character
to "#". that way we wouldn't need to run a script, but could include the vendor
file directly into the src tree.
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, 8:28 am 2010 |
| Alexander Best | Re: Regarding pciids
sorry it seems i missed your post back then.
i found two more lists:
http://rh-software.com/downloads/pcidevs.txt
and
http://hobbes.nmsu.edu/h-browse.php?dir=/pub/incoming (seems to be based on the
Hart list)
the actual Hart list seems to have vanished and the web location is no longer
accessible.
personally i don't think it's necessary to combine the data of two files. the
mares database seems extremely elaborate. all my pci devices get described
properly. also making use of only ...
| Oct 18, 8:23 am 2010 |
| Garrett Cooper | Re: Regarding pciids
Most of the values (above 99%) were the same actually between the
2 lists. I think the point was to avoid churn in the description
fields because a lot of the description fields were different, the
Linux list was produced by questionable sources (IIRC the other list
was produced by vendors, but I could be wrong). Rather than guessing I
would just ask Brookes and Warner directly though, offlist...
Cheers,
-Garrett
_______________________________________________
freebsd-current@freebsd.org ...
| Oct 18, 12:13 pm 2010 |
| Garrett Cooper | Re: Regarding pciids
I noted this a while back to Warner and Brooke as I came up with a
short script to do this, and they suggested that it be supplemented to
the existing list, not replace it.
Cheers,
-Garrett
_______________________________________________
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, 10:27 am 2010 |
| Alexander Best | Re: Regarding pciids
why? the mares list is obviosly superior, because linux contributes to it and
thus has far more people submitting changes than any other list.
is there a case where the old list has an entry the mares list is missing?
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, 11:36 am 2010 |
| previous day | today | next day |
|---|---|---|
| October 17, 2010 | October 18, 2010 | October 19, 2010 |
