https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=190660
Guangyuan Yang changed:
What|Removed |Added
Status|Open|In Progress
Assignee|fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221029
--- Comment #103 from Don Lewis ---
For my next experiment, I built my usual set of packages using the same set of
jails that I use on my other build box:
10.4 i386
lang/go build failure (malloc corruption)
11.1 i386
lang/go bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Jure K. changed:
What|Removed |Added
CC||jure.kozamer...@komna.com
--- Comment #1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #18 from Mikael D ---
(In reply to Jure K. from comment #17)
It was mentioned above that this causes a kernel panic:
"Switching off ACPI during boot causes a kernel panic with a message"
--
You are receiving this mail becaus
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #19 from Jan Bramkamp ---
Disabling ACPI is no longer an acceptable workaround for modern system because
it disables a lot more than just power management for laptops.
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
Jörn Lentes changed:
What|Removed |Added
CC||joern.len...@web.de
--- Comment #20
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #21 from Jan Bramkamp ---
The system does boot, but the only console hangs as soon as the kernel takes
over from the UEFI firmware. I installed mine with mfsBSD and once FreeBSD is
installed (including network configuration and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221350
--- Comment #22 from Mikael D ---
(In reply to Jan Bramkamp from comment #21)
Hopefully it can be fixed before we run into any boot/hardware issues that
require the console before SSH has loaded.
--
You are receiving this mail because:
Y
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #261 from SF ---
The difference between low budget moterboards and enthusiast-boards are the
switching frequency and better power-supply in general, the cheap bords only
have a low frequency and manually settings doesnt get you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #262 from SF ---
Will building of ghc stop if there is any error? I just put into an loop.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #263 from Lars Viklund ---
Let me go on a tangent with my experience since April of Ryzen:
I've had both kinds of AMD problem with my Ryzen 1700 across two ASUS
motherboards, the PRIME B350M-A and the PRIME X370-PRO.
It may he
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #264 from SF ---
No, read my recent posts. Thats the error i have with my machine, screen
turning off and only some stuff inside the pc running. I call it simply a
crash, whats happening during running the system is sometimes sh
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222880
Bug ID: 222880
Summary: freebsd-update should explain how to update ports
after updating to a new release
Product: Base System
Version: CURRENT
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #265 from Lars Viklund ---
(In reply to SF from comment #264)
Dear SF,
I've read every single comment in this bug, and as I say (if you read my
thread) I've tried adjusting settings both according to AMD's advice and yours.
The
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=74127
--- Comment #3 from Kyle Evans ---
(In reply to Pedro F. Giffuni from comment #2)
I double-checked this one- for documentation sake, the example in this PR
results in the following file:
if {![info exists Log(compressProg)]} {
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #266 from SF ---
Nvm, i quitted this bug a while ago because you people are weakminded out of my
view. The solution i told you is exactly the solution for all kinds of problems
people suffering so far, as i told you before iam h
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222858
--- Comment #1 from Dimitry Andric ---
As long as libomp is in ports, you will have to manually add
-I${LOCALBASE}/include to CFLAGS, and -L${LOCALBASE}/lib to LDFLAGS. This is
how it has always been with ports.
There are some preliminary
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #267 from Mark Millard ---
(In reply to SF from comment #262)
> Will building of ghc stop if there is any error? I just put into an loop.
A ghc build will stop with something like a bus error
when it fails.
So if your loop st
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
Bug ID: 222881
Summary: on armv7, clang reports __ARM_ARCH = 6 and defines
__ARM_ARCH_6KZ__
Product: Base System
Version: CURRENT
Hardware: Any
OS: An
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #268 from Mark Millard ---
Just an FYI example about the hangups:
I'm aware of one example of someone with a
Ryzen 7 that was not having any of the hangup
problems until a BIOS update problem caused
a motherboard replacement (w
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #269 from SF ---
Isn't it exactly what i sayed? The motherboard is causing this.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
--- Comment #1 from Dimitry Andric ---
(In reply to Sylvain Garrigues from comment #0)
> As seen in clang -dM -E - < /dev/null
Can you run this command with -v, and paste the output? I would like to know
which -target or -triple option is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
--- Comment #2 from Sylvain Garrigues ---
FreeBSD clang version 5.0.0 (branches/release_50 311219) (based on LLVM
5.0.0svn)
Target: armv6-unknown-freebsd12.0-gnueabihf
Thread model: posix
InstalledDir: /usr/bin
"/usr/bin/clang" -cc1 -tripl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
--- Comment #3 from Dimitry Andric ---
For example, on my amd64 box, I get the following:
$ clang -target armv7-freebsd -dM -E -x c /dev/null|grep -i arm|sort
#define __ARMEL__ 1
#define __ARM_32BIT_STATE 1
#define __ARM_ACLE 200
#define _
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
--- Comment #4 from Dimitry Andric ---
(In reply to Sylvain Garrigues from comment #2)
> FreeBSD clang version 5.0.0 (branches/release_50 311219) (based on LLVM
> 5.0.0svn)
> Target: armv6-unknown-freebsd12.0-gnueabihf
Right, there is the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
--- Comment #5 from Dimitry Andric ---
Hmm, now I look in Makefile.inc1, I see that the only targets are arm, armeb
and armv6. How did you get clang to target armv7 in the first place?
--
You are receiving this mail because:
You are the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
--- Comment #6 from Sylvain Garrigues ---
I take my bug back, I tested on the wrong system. My bad, sorry dim and imp.
On my armv7 system, I do get:
# clang -dM -E - -v < /dev/null
FreeBSD clang version 5.0.0 (tags/RELEASE_500/final 31255
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222881
Sylvain Garrigues changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #270 from Mark Millard ---
(In reply to SF from comment #269)
> Isn't it exactly what i sayed? The motherboard is causing this.
Assuming that is a reply to my comment 268:
It was just example evidence with a simple context
wi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
Heinz N. Gies changed:
What|Removed |Added
CC||he...@project-fifo.net
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220125
Mark Millard changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
--
You are rec
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #271 from SF ---
I doubt you did truely ready any of my posts. All details are in there leading
to the conclusion that the powersupply of at least all low-budget mainboards up
to x370 chipset for ryzen-systems is faulty.
--
Yo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222785
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222797
Mark Linimon changed:
What|Removed |Added
Component|misc|Individual Port(s)
Summa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222800
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|emulat...@freebsd.org
--
You are r
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222837
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222842
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-...@freebsd.org
--
You are
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222858
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-toolchain@FreeBSD.o
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222874
Mark Linimon changed:
What|Removed |Added
Keywords||regression
--
You are receiving th
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221990
--- Comment #2 from Kevin Bowling ---
Can you comment out the MPASS while we investigate? delta is only part of
INVARIANTS so we might have just drifted the calculation. Otherwise the
mp_ring code might have a subtle concurrency issue hin
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #272 from rozhuk...@gmail.com ---
(In reply to Lars Viklund from comment #263)
I was have near issue with black screen/reboot after disk activity on asrock
taichi even with BristolRidge CPU. (Gamming X and AB350M Pro4 was not
af
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207811
Mark Linimon changed:
What|Removed |Added
Keywords||patch
--
You are receiving this ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221804
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-g...@freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222704
Mark Linimon changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|freebsd-virtualization@Free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891
Bug ID: 222891
Summary: /usr/bin/tar exits with INTERNAL ERROR: Function
'archive_read_disk_open'
Product: Base System
Version: 11.1-STABLE
Hardware: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891
Conrad Meyer changed:
What|Removed |Added
CC||c...@freebsd.org
--- Comment #1 fro
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891
Conrad Meyer changed:
What|Removed |Added
Status|New |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891
papow...@astart.com changed:
What|Removed |Added
CC||papow...@astart.com
--- Comme
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222891
Conrad Meyer changed:
What|Removed |Added
Resolution|Not Enough Information |---
Status|Closed
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222874
--- Comment #1 from o...@j.email.ne.jp ---
My last successful version was 324186.
I started seeing problems Friday and my version is 324421.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207811
Alex Kozlov changed:
What|Removed |Added
CC||a...@freebsd.org
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222892
Bug ID: 222892
Summary: gcc compilation errors with mlx4_en and mlx5
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
Status: New
Severit
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222892
Ngie Cooper changed:
What|Removed |Added
Assignee|freebsd-bugs@FreeBSD.org|hsela...@freebsd.org
53 matches
Mail list logo
