https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196760
Allan Jude changed:
What|Removed |Added
CC||arsen...@fahr-zur-hoelle.or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195568
Allan Jude changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195568
--- Comment #9 from wekers ---
Well i following the steps that allan said by link above:
$ env UNAME_r=10.0-RELEASE freebsd-update upgrade -r 10.1-RELEASE
--
The
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195568
--- Comment #8 from wekers ---
Allan i have run file, the return was:
---
/usr/share/misc/magic, 93: Warning: Printf format `l' is not valid for type
`lelong' in d
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825
Michelle Sullivan changed:
What|Removed |Added
Component|bin |kern
Severity|Affect
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192825
--- Comment #1 from Michelle Sullivan ---
Lots more cores in the same place (URL) and in the i386 directory. Issue
appears to be limited to i386 platform with ZFS/ARC when physical memory
exhaustion occurs.
Panics are very very common whe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195568
--- Comment #7 from Allan Jude ---
(In reply to wekers from comment #6)
Do 'file /bin/chmod'
It will tell you what version your userland is (sounds like 10.0).
The instructions for fixing the system can be found here (written by the user
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195568
--- Comment #6 from wekers ---
I don't know, but when did the upgrade and try run 'freebsd-update install'
again
--
No updates needed to update system to 10.1-RELEASE-p5.
$ freebsd-update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197578
--- Comment #5 from klamo...@vianet.ca ---
Added that to loader.conf and restarted the server.
Still the same problem.
Oddly enough the other bundled tools that come with the base system such as
sha1, sha256, sha512 and rmd160 do not have
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197578
--- Comment #4 from Glen Barber ---
Will you try adding 'vfs.unmapped_buf_allowed=0' to /boot/loader.conf, and
rebooting the system? There were reports of having vfs.unmapped_buf_allowed
enabled resulting in similar behavior in hypervisors
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197578
--- Comment #3 from klamo...@vianet.ca ---
Created attachment 152917
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=152917&action=edit
debug output
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197578
--- Comment #2 from Glen Barber ---
Can you please provide the following output?
pciconf -lv
sysctl kern
sysctl vfs
sysctl dev
sysctl hw
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197578
--- Comment #1 from klamo...@vianet.ca ---
Extended md5 debugging:
# md5 -xt /boot/kernel/kernel
MD5 test suite:
MD5 ("") = d41d8cd98f00b204e9800998ecf8427e - verified correct
MD5 ("a") = 0cc175b9c0f1b6a831c399e269772661 - verified correct
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197578
Bug ID: 197578
Summary: md5 returns random values each time; breaking
freebsd-update
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS: An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197336
--- Comment #1 from Will Dormann ---
Also related:
rm -rf find_test_q65puW
will only delete 32765 subdirectories. The others will give a "permission
denied" error.
--
You are receiving this mail because:
You are the assignee for the bug
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197567
Bug ID: 197567
Summary: chflags -f argument ignored when no file found to be
modified
Product: Base System
Version: 10.1-RELEASE
Hardware: amd64
OS: A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197566
Bug ID: 197566
Summary: Wrong comparsion in pflogd
Product: Base System
Version: 11.0-CURRENT
Hardware: Any
OS: Any
Status: New
Severity: Affects On
17 matches
Mail list logo
