Hi,
On 4/22/21 6:00 PM, Alan Somers wrote:
Because we have a policy of never releasing anything even a little bit
backwards-incompatible in a minor release.
I believe we have made backwards incompatible changes in minor branches
in the fairly recent past, at least compiler changes and VM
Hi,
On 2/18/21 9:14 AM, Jakob Alvermark wrote:
It used to start webcamd for both of them, now it is only started for
the built in Chicony.
I have a similar problem. I have 3 cameras (one Logitech and two USB UVD
things) and now it only starts webcamd for one. I can start it manually
for the
Hi,
On 9/1/20 1:14 PM, Ed Maste wrote:
We've been updating the svn-git converter and pushing out a new
converted repo every two weeks, and are now approaching the time where
we'd like to commit to the tree generated by the exporter, and
guarantee that hashes will remain consistent from this
Hi,
On 7/10/20 7:12 PM, Yuri Pankov wrote:
Thanks.
The attached diff seems to take care of the issue for me, adding VIS_TAB
and removing VIS_SAFE, which can be blamed for passing through the
following:
VIS_SAFE Currently this form allows space, tab, newline, backspace,
On 11/28/19 4:08 PM, Mark Millard via svn-src-head wrote:
Author: daichi
Date: Fri Sep 20 17:37:23 2019
New Revision: 352558
URL:
https://svnweb.freebsd.org/changeset/base/352558
Log:
top(1): support multibyte characters in command names (ARGV array)
depending on locale.
- add
Hi,
On 06/18/18 17:42, Rick Macklem wrote:
Steve Wills wrote:
Would it be possible or reasonable to use the client ID to log a message
telling the admin to enable a sysctl to enable the hacks?
Yes. However, this client implementation id is only seen by the server
when the client makes a mount
Would it be possible or reasonable to use the client ID to log a message
telling the admin to enable a sysctl to enable the hacks?
Steve
On 06/17/18 08:35, Rick Macklem wrote:
Hi,
Andreas Nagy has been doing a lot of testing of the NFSv4.1 client in ESXi 6.5u1
(VMware) against the FreeBSD
I may be seeing similar issues. Have you tried leaving top -SHa running
and seeing what threads are using CPU when it hangs? I did and saw pid
17 [zfskern{txg_thread_enter}] using lots of CPU but no disk activity
happening. Do you see similar?
Steve
On 05/22/18 04:17, Alexander Leidinger
can't find any
other evidence of it. Any ideas?
Steve
On 04/24/2018 19:30, Steve Wills wrote:
Hi,
Recently on multiple systems running CURRENT, I've been seeing the
system become unresponsive. Leaving top(1) running has lead me to notice
that when this happens, the system is still respondi
Hi,
Recently on multiple systems running CURRENT, I've been seeing the
system become unresponsive. Leaving top(1) running has lead me to notice
that when this happens, the system is still responding to ping and top
over ssh is still working, but no new processes can start and switching
to
FWIW, I ran into this issue on an i386 image I built from an amd64 host
using poudriere and poudriere image.
Steve
On 03/13/2018 14:44, Warner Losh wrote:
Makes sense. I'd forgotten that kldxref can't do cross-platform stuff
One could arrange to build it targeting arch X but running on
Hi,
On 12/21/2016 06:58, Konstantin Belousov wrote:
> What is the exact version of the kernel you are running and which hangs ?
Right now I'm running r310303, booted with SMP disabled.
> Try to bisect.
>
The issue appeared without updating the OS, but I have since updated.
That said, I have
Hi,
On 12/16/2016 16:20, John Baldwin wrote:
> On Thursday, December 15, 2016 03:57:58 PM Adrian Chadd wrote:
>> heh, an updated BIOS that solves the problem will solve the problem. :)
>>
>> I think you have enough information to provide to supermicro. Ie,
>> "SMAP says X, when physical memory
On 05/ 2/16 11:24 PM, Warner Losh wrote:
>
>
> On Mon, May 2, 2016 at 6:55 PM, Steve Wills <swi...@freebsd.org
> <mailto:swi...@freebsd.org>> wrote:
>
> Hi,
>
> On 05/ 2/16 09:32 AM, Steve Wills wrote:
> > Hi,
> >
>
Hi,
On 05/ 2/16 09:32 AM, Steve Wills wrote:
> Hi,
>
> Just did my monthly update and r298785 seems to be leaking wired memory
> rather rapidly. My system has 8gb of RAM and the amount of wired memory
> just goes up and up continuously. It takes about 12 hours before it
> ex
On Wed, Oct 08, 2014 at 08:55:26AM +0300, Andriy Gapon wrote:
On 08/10/2014 03:40, Steve Wills wrote:
Hi,
Not sure which thread this belongs to, but I have a zfs hang on one of my
boxes
running r272152. Running procstat -kka looks like:
http://pastebin.com/szZZP8Tf
My zpool
On Fri, Oct 10, 2014 at 02:35:14AM +0100, Steven Hartland wrote:
- Original Message -
From: Steve Wills swi...@freebsd.org
To: Andriy Gapon a...@freebsd.org
Cc: curr...@freebsd.org; f...@freebsd.org
Sent: Friday, October 10, 2014 2:27 AM
Subject: Re: zfs hang
On Wed, Oct 08
Hi,
Not sure which thread this belongs to, but I have a zfs hang on one of my boxes
running r272152. Running procstat -kka looks like:
http://pastebin.com/szZZP8Tf
My zpool commands seem to be hung in spa_errlog_lock while others are hung in
zfs_lookup. Suggestions?
Thanks,
Steve
Hi,
I've got some new hardware and have been experiencing lockups using the em
driver. They seem to only happen on large downloads, smaller things like ssh
and web browsing work OK. The hardware is:
em0@pci0:0:25:0:class=0x02 card=0x309f17aa chip=0x153a8086 rev=0x04
hdr=0x00
On Mon, Sep 08, 2014 at 01:29:31PM -0400, Allan Jude wrote:
Try periodically setting dev.em.0.debug=1
it will dump a bunch of stats to syslog then set it self back to -1
there are also a bunch of useful stats under:
dev.em.0 including things like:
dev.em.0.mbuf_alloc_fail
Hi,
On Thu, Jul 31, 2014 at 06:22:27PM +0200, Anton Berezin wrote:
Jan,
On Thu, Jul 31, 2014 at 05:56:23PM +0200, Jan Kokemüller wrote:
On 31.07.2014 16:21, Anton Berezin wrote:
At the console, depressing and holding a key does not lead to auto-repeat.
At the console, sometimes a key
Hi,
Just experienced this tmpfs panic on r268160:
Freed UMA keg (TMPFS node) was not empty (16 items). Lost 1 pages of memory.
Fatal trap 12: page fault while in kernel mode
cpuid = 12; apic id = 0c
fault virtual address = 0x378
fault code = supervisor read data, page not
__func__, m, owner);
(kgdb)
I'm told that MTX_CONTESTED was set on the unlocked mtx and that MTX_CONTENDED
is spuriously left behind, and to ask how lock prefix is handled in bhyve. Any
of that make sense to anyone?
Thanks,
Steve
On Sun, Jul 06, 2014 at 01:53:37PM +, Steve Wills
On Sun, Jul 06, 2014 at 12:28:07PM -0400, Ryan Stone wrote:
On Sun, Jul 6, 2014 at 11:46 AM, Steve Wills swi...@freebsd.org wrote:
I should have noted this system is running in bhyve. Also I'm told this
panic
may be related to the fact that the system is running in bhyve.
Looking
On Sun, Jul 06, 2014 at 01:49:04PM -0700, Neel Natu wrote:
Hi Steve,
On Sun, Jul 6, 2014 at 8:46 AM, Steve Wills swi...@freebsd.org wrote:
I should have noted this system is running in bhyve. Also I'm told this
panic
may be related to the fact that the system is running in bhyve
On Wed, Apr 02, 2014 at 03:56:35PM -0700, Sean Bruno wrote:
On Wed, 2014-04-02 at 18:06 -0400, Garrett Wollman wrote:
In article 1396457629.2280.2.ca...@powernoodle.corp.yahoo.com,
sbr...@freebsd.org writes:
I'd like to make this change to login.conf for default installs.
This
On Wed, Apr 02, 2014 at 09:31:08PM -0400, Daniel Eischen wrote:
On Thu, 3 Apr 2014, Steve Wills wrote:
On Wed, Apr 02, 2014 at 03:56:35PM -0700, Sean Bruno wrote:
On Wed, 2014-04-02 at 18:06 -0400, Garrett Wollman wrote:
In article 1396457629.2280.2.ca...@powernoodle.corp.yahoo.com,
sbr
Hi,
I had a panic on a box running r260369. I unfortunately didn't get a core dump,
but did take a picture, available here:
http://meatwad.mouf.net/~swills/panic_r260369_1.jpg
and the backtrace, here:
http://meatwad.mouf.net/~swills/panic_r260369_2.jpg
The box was very heavily loaded doing
I would love to have a native driver for this:
none2@pci0:2:0:0: class=0x028000 card=0x00101028 chip=0x472714e4 rev=0x01
hdr=0x00
vendor = 'Broadcom Corporation'
device = 'BCM4313 802.11b/g/n Wireless LAN Controller'
class = network
Are there docs or other drivers
I'm having the same issue.
Steve
On Fri, Oct 11, 2013 at 03:05:51PM +0200, Remko Lodder wrote:
Dear Current readers,
Please find issues that I have with the latest /etc/rc.d/jail changes and the
use of ezjail.
Thanks
remko
Begin forwarded message:
From: Remko Lodder
Hi,
I was testing a patch on r246300 or so, and wanted to see if it would
apply
cleanly to a newer copy of HEAD.
Well it did, except I had a hang at boot, shortly after ZFS version and
the
last scsi devices appear.
This easily could have been related to the patch I was testing, so I wiped
On 11/13/12 18:51, AN wrote:
Can anyone comment on current built with clang as default compiler and
ports? Are there any major problems, programs that don't run?
Specifically, I am interested in how Gnome and Xorg (Gnome and Xorg
built with default system gcc) work on world built with clang.
Hi All,
Has something changed in the scheduler recently? I don't have anything
concrete, just anecdotal evidence, but my current desktop feels a little
less responsive under heavy CPU load than it did a few weeks ago.
Usually my high CPU processes (builds) are nice'd, but even with that,
thing
Hi,
I get this panic:
Fatal trap 18: integer divide fault while in kernel mode
cpuid = 4; apic id = 04
instruction pointer = 0x20:0x808f0c23
stack pointer = 0x28:0xff83693b8b40
frame pointer = 0x28:0xff83693b8ba0
code segment= base 0x0, limit
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command gets different results the second time it is
run vs. the first time. I can imagine a user saying I ran pkg, but it
On Aug 23, 2012, at 9:57 PM, Eitan Adler wrote:
On 23 August 2012 18:19, Steve Wills swi...@freebsd.org wrote:
Hi,
It seems to me that renaming the pkg binary in /usr/sbin/pkg to
/usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is
confusing that running the command
On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote:
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because the how-to may not be for a new system ;)
The possibility of bad docs somewhere outside of our control, when we can
On Aug 23, 2012, at 10:23 PM, Eitan Adler wrote:
On 23 August 2012 22:15, Steve Wills swi...@freebsd.org wrote:
On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote:
On 23 August 2012 22:05, Steve Wills swi...@freebsd.org wrote:
Why can't one of those steps be to run pkg-bootstrap?
Because
On 08/16/12 17:13, O. Hartmann wrote:
Am 08/16/12 22:58, schrieb Warren Block:
On Thu, 16 Aug 2012, O. Hartmann wrote:
I find myself a bit floating when I looked for snapshot images for
DVD/CD for rescue discs for FreeBSD 10.0-CURRENT/amd64. I can not find
anything following the webpage
On 08/16/12 17:44, Steve Wills wrote:
On 08/16/12 17:13, O. Hartmann wrote:
Am 08/16/12 22:58, schrieb Warren Block:
On Thu, 16 Aug 2012, O. Hartmann wrote:
I find myself a bit floating when I looked for snapshot images for
DVD/CD for rescue discs for FreeBSD 10.0-CURRENT/amd64. I can
On 08/14/12 15:42, Andrey V. Elsukov wrote:
On 14.08.2012 21:03, Steve Wills wrote:
Any ideas if this is a bug or something wrong with my system would be
appreciated.
Can you boot with serial console and show what show the `lsdev` command
in the loader?
And from the running system
Hi,
I just upgraded my system from r238261 to r239244 and was unable to boot
one of my zfs root systems. I had to recover using the zfsloader.old
that is kept in /boot. The messages from zfsloader were:
ZFS: can't find pool by guid
ZFS: can't find pool by guid
can't load 'kernel'
followed by a
On 07/08/12 13:56, Alan Cox wrote:
In r237513 on 6/23 I made a mistake that was corrected in r238124 on 7/5.
I can vaguely see a connection between kern.ipc.shm_use_phys and the
problem fixed in r238124. So, I'd like to know if this problem still
exists. Wait, however, until you see
Following up to myself, with some things I should have mentioned before:
On 07/05/12 19:59, Steve Wills wrote:
On 07/05/12 03:00, Alan Cox wrote:
On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills swi...@freebsd.org wrote:
Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set
On 07/05/12 03:00, Alan Cox wrote:
On Wed, Jul 4, 2012 at 4:57 PM, Steve Wills swi...@freebsd.org wrote:
Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set
it to 1 for some reason that I can't recall.
That shouldn't cause a crash in pmap_enter(). What is line 3587
Hi,
After updating to r238120, I get a panic whenever X starts up. It works for a
few seconds, then panics. The messages don't look too useful to me, but here
they are:
Unread portion of the kernel message buffer:
processor eflags= interrupt enabled, resume, IOPL = 0
current process
Setting kern.ipc.shm_use_phys back to 0 (the default) fixed it. I had set it to
1 for some reason that I can't recall.
Steve
On Jul 4, 2012, at 5:41 PM, Steve Wills wrote:
Hi,
After updating to r238120, I get a panic whenever X starts up. It works for a
few seconds, then panics
Hi Matthais,
On 06/27/12 01:19, Matthias Apitz wrote:
El día Saturday, June 16, 2012 a las 08:11:40AM -0400, John Baldwin escribió:
On Saturday, June 16, 2012 04:51:06 AM Matthias Apitz wrote:
El día Friday, June 15, 2012 a las 08:18:22AM -0400, John Baldwin escribió:
the panic says:
mutex
Hi,
I just got a panic out of my r237195 system. The panic looks like:
Sleeping thread (tid 173153, pid 42034) owns a non-sleepable lock
KDB: stack backtrace of thread 173153:
sched_switch() at sched_switch+0x28a
mi_switch() at mi_switch+0xdf
sleepq_timedwait() at sleepq_timedwait+0x3a
_sleep()
On 05/08/12 00:46, Jason Evans wrote:
How recent is your system? This problem should have been fixed by
r234569, so if you're still seeing problems after that revision,
there's another problem we need to figure out. (By the way, it's
possible for an application to trigger this assertion,
On 2012/5/6 5:08, b. f. wrote:
On 5/5/12, Steve Willsswi...@freebsd.org wrote:
Thanks for the info. I took a look at the dump and see this:
% sudo gdb /usr/bin/ctfmerge ctfmerge.core
[GDB will not be able to debug user-mode threads: Undefined symbol
td_thr_getxmmregs]
Hmm, is the thread
On Apr 21, 2012, at 11:54 AM, David Wolfskill wrote:
After applying Dimitry Andric's patches to contrib/jemalloc and
replacing
/usr/bin/as with one built last Sunday, I was finally(!) able to rebuild
head as of 234536:
FreeBSD freebeast.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #797
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
Bus error (core dumped)
*** [libc.so.7] Error code 138
Anyone else seeing this or have any idea how to avoid it? Let me know
On 05/05/12 15:43, b. f. wrote:
Steve Wills wrote:
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
Bus error (core dumped)
*** [libc.so.7] Error code 138
Anyone else
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/29/12 13:17, K. Macy wrote:
.
I tried it, on both FreeBSD routers, web systems, and database
servers; all on 8.2+. It still causes massive instability.
Disabling the sysctl, and/or removing it from the kernel solved
the problems.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/27/12 10:53, Łukasz Wąsikowski wrote:
W dniu 2012-02-22 23:31, Bjoern A. Zeeb pisze:
You cannot ship that on by default for non-tecnical reasons in a
kernel. Please do not commit a kernel config that can be booted
(no LINT cannot be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Yesterday afternoon, I updated my -CURRENT host. Then I updated the
jails (chroots) that my ports tinderbox uses. Now I've found that the
7.x and 8.x ones can't run gcc as it reports:
gcc: Internal error: Abort trap: 6 (program cc1)
9.x things
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please disregard this, it was a local issue that I resolved. I had tried
to enable userland Dtrace (WITH_CTF), but mistakenly did it for 7.x and
8.x as well as 9.x. Sorry for the noise.
Steve
On 09/17/11 23:40, Steve Wills wrote:
Hi,
Yesterday
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/27/11 21:23, Steve Wills wrote:
On 08/27/11 20:55, Rick Macklem wrote:
I don't know why the nfsd wouldn't be able to bind(2) to port #2049 a
second time for UDP, but someone on the net side might know? (Just in
case it is a problem that has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 08/29/11 11:47, Rick Macklem wrote:
I think it did. Lookup of .. was failing. I think that was because
ni_strictrelative (added for capabilities) wasn't initialized and
happened to be non-zero.
Please try this patch and let us know if it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/27/11 09:00, Rick Macklem wrote:
This line indicates that mountd over tcp is registered for v3,
so I suspect the error message is misleading??
Forgot to reply to this part, and I should have been more clear earlier.
When I used the default
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/27/11 20:55, Rick Macklem wrote:
I don't know why the nfsd wouldn't be able to bind(2) to port #2049 a
second time for UDP, but someone on the net side might know? (Just in
case it is a problem that has already been fixed, I'd try a newer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi 4.1.0.
When I attempt the mount, it logs this message:
The NFS server does not support MOUNT version 3 over TCP
Have I configured something wrong and if so what? Or is this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/11 21:41, Steve Wills wrote:
Hi,
I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi 4.1.0.
When I attempt the mount, it logs this message:
The NFS server does not support MOUNT version 3 over TCP
Have I configured
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/26/11 22:16, Steve Wills wrote:
On 08/26/11 21:41, Steve Wills wrote:
Hi,
I'm trying to use 9.0-CURRENT as an NFS server for a VMWare ESXi 4.1.0.
When I attempt the mount, it logs this message:
The NFS server does not support MOUNT
On 07/21/11 15:10, Scot Hetzel wrote:
On Thu, Jul 21, 2011 at 10:53 AM, John Baldwin j...@freebsd.org wrote:
Hmm, so there does look to be a reasonable _CRS method. Oh, I think I see
what I don't like:
DWordMemory (ResourceProducer, PosDecode, MinNotFixed,
MaxFixed,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/20/11 09:04, John Baldwin wrote:
On Wednesday, July 20, 2011 8:33:07 am Bernhard Froehlich wrote:
On Wed, 20 Jul 2011 07:41:26 -0400, John Baldwin wrote:
On Tuesday, July 19, 2011 10:35:42 pm Steve Wills wrote:
Hi,
While testing some other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
While testing some other things, I found -CURRENT from yesterday doesn't
work with the em0 in my VirtualBox 4.0.8 (a little out of date
admittedly). It worked Friday or Saturday I think. Anyone else seen this
or should I open a PR? Has the code
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've noticed lately that when doing heavy IO, my 9-CURRENT system (Fri
Apr 15 23:33:46 EDT 2011) is quite unresponsive. I have two ZFS mirrors
setup and run KDE4. The system has 12GB of RAM.
When I, for example, copy an ISO image from one mirror
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I have a similar issue. I have:
ifconfig_re0_ipv6=inet6 accept_rtadv
And after boot, I get:
% ping6 www.google.com
PING6(56=40+8+8 bytes) 2001:470:::::: --
2a00:1450:8005::68
^C
- --- www.l.google.com ping6 statistics ---
5
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 04:22, Edward Tomasz Napierała wrote:
Wiadomość napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11:
[..]
Thanks for your work on this, I'm very happy to have ZFS v28. I just
updated my -CURRENT system from a snapshot from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 08:35, Steve Wills wrote:
On 03/06/11 04:22, Edward Tomasz NapieraBa wrote:
Wiadomo[ napisana przez Steve Wills w dniu 2011-03-06, o godz. 05:11:
[..]
Thanks for your work on this, I'm very happy to have ZFS v28. I just
updated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 10:37, Jeremy Chadwick wrote:
At first glance it looks like acl_set_fd_np(3) isn't working on an
md-backed filesystem; specifically, it's returning EOPNOTSUPP. You
should be able to reproduce the problem by doing a setfacl on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 11:30, Jeremy Chadwick wrote:
On Sun, Mar 06, 2011 at 08:23:42AM -0800, Jeremy Chadwick wrote:
On Sun, Mar 06, 2011 at 11:06:09AM -0500, Steve Wills wrote:
Sorry, I should have been more clear -- my investigation wasn't to
determine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/06/11 12:49, Edward Tomasz Napierała wrote:
The above looks like old-style, canonical six trivial ACL. Now,
cp(1) shouldn't even try to copy the ACL in this case, since there
is nothing to copy. So, for some reason, something failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Pawel,
On 02/27/11 15:29, Pawel Jakub Dawidek wrote:
Hi.
I just committed ZFSv28 to HEAD.
New major features:
- Data deduplication.
- Triple parity RAIDZ (RAIDZ3).
- zfs diff.
- zpool split.
- Snapshot holds.
- zpool import -F.
76 matches
Mail list logo
