> > [... snip ...]
> > > Is there something I'm perhaps missing regarding loader.conf and/or
> rc.conf ?
>
I may be wrong, but it looks like a "framebuffer problem" that is most
often associated with amdgpu, but may help your i915 intel graphics too.
Just try adding this to /boot/loader.conf :
On Mon, May 25, 2020 at 08:13:16PM +, you (marco) sent the following to
[freebsd-current] :
>
> I took 3 pictures of the system dropping to the debugger for r360723.
> 1st 2 pictures are right before the panic and the final the panic screen
> itself.
> It seems the panic occurs right before
On Mon, May 25, 2020 at 10:28:39AM -0500, you (Kyle Evans) sent the following
to [freebsd-current] :
> On Mon, May 25, 2020 at 3:51 AM marco
> wrote:
> >
> > [... snip ...]
> > Is there something I'm perhaps missing regarding loader.conf and/or rc.conf
> > ?
> > It could just be these 2
On Mon, May 25, 2020 at 2:22 PM Jamie Landeg-Jones wrote:
>
> From the "Why did you do that?" department:
>
> I stumbled across a panic in 12.1-stable and 13-current. If you
> attempt to create a tunnel, which would have the same name as
> an already existing tunnel "alias" hardlink, you get a
>From the "Why did you do that?" department:
I stumbled across a panic in 12.1-stable and 13-current. If you
attempt to create a tunnel, which would have the same name as
an already existing tunnel "alias" hardlink, you get a panic.
E.G:
# ifconfig tun create name tun1
# ifcondif tun create
On Mon, May 25, 2020 at 11:51 AM Li-Wen Hsu wrote:
> (Please send the followup to freebsd-testing@ and note Reply-To is set.)
>
> FreeBSD CI Weekly Report 2020-05-24
> ===
>
> Here is a summary of the FreeBSD Continuous Integration results for the
> period
> from
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-05-24
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-05-18 to 2020-05-24.
During this period, we have:
* 2064
On Mon, May 25, 2020 at 3:51 AM marco
wrote:
>
> [... snip ...]
> Is there something I'm perhaps missing regarding loader.conf and/or rc.conf ?
> It could just be these 2 specific revisions and will try another revision but
> perhaps I need to do something setting the zfs bootcode again using
On 5/11/20 3:16 PM, Pete Wright wrote:
hello,
i have a lenovo thinkpad P43s that exhibits lockups under CURRENT but
behaves fine when running STABLE. i've tried to find a fully
reproducible situation to get this system to lockup but haven't found
anything yet. i am starting to suspect
returning FreeBSD user here, using bectl for the 1st time on a thinkpad x230
with 16GB of RAM.
bectl list -aDs
BE/Dataset/Snapshot Active Mountpoint Space Created
r359556
zroot/ROOT/r359556 NR / 12.2G 2020-04-03
20:05
Hello all,
First of all sorry for forgetting to send a report last week.
A lot happened in two weeks.
We are now 98% synced with Linux 5.2 and I've taggued a release
yesterday (https://github.com/freebsd/drm-kmod/releases/tag/drm_v5.2_8)
and this is now in ports in graphics/drm-devel-kmod
I see that on my laptop both efirtc and atrtc get attached.
The latter is via an ACPI attachment:
efirtc0:
efirtc0: registered as a time-of-day clock, resolution 1.00s
atrtc0: port 0x70-0x71 on acpi0
atrtc0: registered as a time-of-day clock, resolution 1.00s
I am not sure if this is
12 matches
Mail list logo
