https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220404
--- Comment #2 from Mark Millard ---
(In reply to Mark Millard from comment #1)
FYI: I do understand that the specific aliasing
I list may well be 32-bit powerpc specific. But
other aliasing between the anonymous structs in
that union is j
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220404
--- Comment #1 from Mark Millard ---
(In reply to Mark Millard from comment #0)
Some other supporting code details follow.
static struct socket *
soalloc(struct vnet *vnet)
{
struct socket *so;
so = uma_zalloc(socket_zone
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220404
Mark Millard changed:
What|Removed |Added
Summary|head -r319722 or -r320224 |head -r319722 related
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213903
--- Comment #39 from Mateusz Guzik ---
Can someone who runs into the problem on stable/10 test the following please:
https://people.freebsd.org/~mjg/patches/rwlock-unlock.diff
--
You are receiving this mail because:
You are the assignee f
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220404
Bug ID: 220404
Summary: head -r319722 or -r320224 related changes break
powerpc production-style kernel operation: bad
function pointer
Product: Base System
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220398
Alan Somers changed:
What|Removed |Added
Status|New |Open
Assignee|freebsd-bugs
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220398
Bug ID: 220398
Summary: lio_listio(2) never sends asynchronous notification if
nent==0
Product: Base System
Version: CURRENT
Hardware: Any
OS: Any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #22 from SF ---
Disappointing, after alot of crashes it did run stable for a long while. Now it
keeps crashing over and over again.
Back to the scratchboard...
--
You are receiving this mail because:
You are the assignee for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #21 from SF ---
I think i solved it. It is related to ram, cpu-power-supply and heat.
You must ensure you ram settings arent too fast, it causes your cpu to consume
more power and getting high peaks draining the capacitors. You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220391
Bug ID: 220391
Summary: "gpart resize" = panic
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #20 from SF ---
According to your low-temperature-problem. Did you check if your cpu definitely
runs at full speed? I turned off powerd and did manually set my frequency
within bios to an fixed frequency because it did stay at l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155
--- Comment #16 from Martin Waschbüsch ---
Ed,
unfortunately, both 11.1-BETA3 and 12.0-CURRENT-amd64-20170626-r320360 showed
the same behavior as the current stable 11.0-RELEASE.
--
You are receiving this mail because:
You are the assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #19 from SF ---
To me it is the complete opposite, my system runs too hot. Up to 70°C or higher
under full load.
Changing Voltages to lower values and power-settings to what i described
improved it to me, my system stays far lo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #18 from Nils Beyer ---
SF,
sorry, but what five values do you mean exactly? I'm currently not at work so I
cannot test anything for the rest of the weekend.
But, because you are experiencing improvments by playing around with
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155
--- Comment #15 from Martin Waschbüsch ---
(In reply to Ed Maste from comment #14)
Sure, Ed.
I will do that asap and post results here.
--
You are receiving this mail because:
You are the assignee for the bug.
__
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214242
Ed Maste changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155
--- Comment #14 from Ed Maste ---
(In reply to Martin Waschbüsch from comment #2)
I'm trying to find a convenient way to debug this further, however while I look
into that, are you able to try booting FreeBSD 11.1 and FreeBSD 12 snapshots i
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213155
--- Comment #13 from Ed Maste ---
(In reply to Bennett from comment #11)
Hi Bennett, which two processes did you examine with GDB? It looks like these
are the result of running GDB on the host qemu process?
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #17 from SF ---
Try leaving all setting at Auto except of the first 5 values.
My sound is looping a few milliseconds right before the screen turns black and
nothing happens anymore, the computer still idles around and seems to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220384
Bug ID: 220384
Summary: Loading kernel module i915 after i915kms panics
Product: Base System
Version: 11.0-RELEASE
Hardware: i386
OS: Any
Status: New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #16 from Nils Beyer ---
Sound loops are somewhat new to me - my music that is playing while using the
computer just stops - no sound artifacts at all.
Something else I've noticed are often messages in the poudriere logs like:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220380
Bug ID: 220380
Summary: [ofed] Cannot bind to the same port after
rdma_destroy_id and rdma_create_id
Product: Base System
Version: CURRENT
Hardware: amd64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
--- Comment #15 from SF ---
Specs:
FreeBSD 11.0
XFCE
R7 1700x
Asus PRIME B350-PLUS
Ram G.Skill F4-3600C16D-16GTZR
--
You are receiving this mail because:
You are the assignee for the bug.
___
fr
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219399
SF changed:
What|Removed |Added
CC||shitma...@hotmail.com
--- Comment #14 from SF
24 matches
Mail list logo
