https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203873
--- Comment #3 from eu...@grosbein.net ---
> Are there other warnings we should capture as well?
None I am aware of.
> I'd like to see mention of the exit status in the man page as well.
Feel free to add :-) English is not my nativa langu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203704
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203646
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203647
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203648
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203645
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201435
John Baldwin changed:
What|Removed |Added
CC||j...@freebsd.org
Status
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203645
--- Comment #1 from scdbac...@gmx.net ---
Also present in NetBSD.
http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/makefs/cd9660.c?annotate=1.49
280:OPT_NUM('l', "isolevel", isoLevel,
281:1, 3, "ISO Leve
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203646
--- Comment #1 from scdbac...@gmx.net ---
Also present in NetBSD.
http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/makefs/cd9660/cd9660_eltorito.c?annotate=1.17.2.3
359:cd9660_bothendian_dword(first_sector,
360:disk
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203648
--- Comment #1 from scdbac...@gmx.net ---
This one is not present in NetBSD (any more ?).
http://cvsweb.netbsd.org/bsdweb.cgi/src/usr.sbin/makefs/cd9660/iso9660_rrip.c?annotate=1.11.2.2
660:if (sizeof (fnode->inode->st.st_rdev) > 4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203647
--- Comment #2 from scdbac...@gmx.net ---
It looks like it is still in lines 214+215.
The variable buffer_head (=buffer) is used in the return statement
and thus cannot be freed before the context gets dropped.
http://cvsweb.netbsd.org/bsdw
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203647
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #1 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203704
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
--- Comment #5 from
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203879
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||be...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203873
--- Comment #2 from Ed Maste ---
Thank you for the submission. The change seems reasonable to me. Are there
other warnings we should capture as well?
If you're keen I'd like to see mention of the exit status in the man page as
well. AFA
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187081
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203879
Bug ID: 203879
Summary: mount_smbfs panic at smbutil logout
Product: Base System
Version: 11.0-CURRENT
Hardware: amd64
OS: Any
Status: New
Severity:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203877
Garrett Wollman changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-zfs-devel@FreeBSD.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203877
--- Comment #1 from Garrett Wollman ---
(I finally figured out that it was somewhere deep in ZFS by running a "procstat
-a -kk | fgrep nfsd" last time this happened -- but of course it always happens
when we need to get the server back up a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203877
Bug ID: 203877
Summary: NFS threads get blocked when writing to ZFS dataset
that has reached quota
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203867
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203876
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203876
--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:
Author: ngie
Date: Mon Oct 19 18:29:33 UTC 2015
New revision: 289600
URL: https://svnweb.freebsd.org/changeset/base/289600
Log:
Initialize `quiet` to false so
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203876
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||b...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203876
Bug ID: 203876
Summary: "pw groupnext" does not output anything
Product: Base System
Version: 10.2-STABLE
Hardware: Any
OS: Any
Status: New
Severity
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=168315
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|n...@freebsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203649
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
--- Comment #1 from bhav...@vmware.com ---
Created attachment 162212
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162212&action=edit
patch to remove VMware MSI/MSI-X quirk
--
You are receiving this mail because:
You are the as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
bhav...@vmware.com changed:
What|Removed |Added
Blocks||178795
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203874
Bug ID: 203874
Summary: MSI/MSI-X interrupts don't work in VMware virtual
machines
Product: Base System
Version: 11.0-CURRENT
Hardware: amd64
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203873
Sean Bruno changed:
What|Removed |Added
Status|New |In Progress
CC|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203873
Bug ID: 203873
Summary: [patch] make gzip(1) embedded-friendly and more
compatible with GNU gzip
Product: Base System
Version: 10.2-STABLE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203649
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd...@freebsd.org |freebsd-bugs@FreeBSD.org
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203649
Mark Linimon changed:
What|Removed |Added
Keywords||patch
Assignee|freebsd-bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203649
--- Comment #1 from scdbac...@gmx.net ---
--- Source analysis:
I meanwhile learned that err() is also available in userspace and
indeed exits its process.
So it is not a potential SIGSEGV but just a surplus test.
--
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203820
--- Comment #1 from martin ilavsky ---
# kgdb kernel.debug /var/crash/vmcore.0
(kgdb) list *0x821f542b
0x821f542b is in vmx_disable (cpufunc.h:423).
418 }
419
420 static __inline void
421 load_cr4(u_long data)
42
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203630
--- Comment #13 from Eddy ---
(In reply to Wei Hu from comment #12)
After some tests, "disable_csum_20151016.patch" doesn't solve the issue for me.
The last r285236 patch worked.
Do I have to first apply the r285236 patch and then the
dis
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203867
Bug ID: 203867
Summary: usr/src/usr.bin/limits/limits.c:507: bad if test ?
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203276
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|kmo...@freebsd.org
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203276
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
CC||n...@freebsd.org
---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203864
Garrett Cooper,425-314-3911 changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203864
--- Comment #1 from Peter Wemm ---
FWIW; the machine couldn't reboot either. It required a break to ddb and 'call
cpu_reset'.
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203864
Bug ID: 203864
Summary: ZFS deadlock between zfs send, zfs rename and ctrl-C
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
43 matches
Mail list logo
