Warner Losh wrote:
Which driver does your system use?
em0: mem 0x5430-0x5431 at
device 31.6 on pci0
em0: Using 1024 TX descriptors and 1024 RX descriptors
em0: Using an MSI interrupt
em0: netmap queues/slots: TX 1/1024, RX 1/1024
On Tue, Feb 11, 2020 at 11:49 PM wrote:
Getting
Which driver does your system use?
Warner
On Tue, Feb 11, 2020 at 11:49 PM wrote:
> Getting the following panic after updating to r357793 (expect typos,
> hand copied):
>
> panic: Assertion in_epoch(net_epoch_preempt) failed at
> /usr/src/sys/net/iflib.c:2762
>
> db_trace_self_wrapper()
>
Getting the following panic after updating to r357793 (expect typos,
hand copied):
panic: Assertion in_epoch(net_epoch_preempt) failed at
/usr/src/sys/net/iflib.c:2762
db_trace_self_wrapper()
vpanic()
panic()
iflib_rxeof()
_task_fn_rx()
gtaskqueue_run_locked()
gtaskqueue_thread_loop()
from Andrey Fesenko:
> bsdinstall script, work in 2019
PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs / }
#!/bin/sh -x
# Make diskname independante
gpart modify -l freebsd-boot -i 1 ada0
gpart modify -l efi -i 2 ada0
gpart modify -l root -i 3 ada0
# Make EFI
bsdinstall script, work in 2019
PARTITIONS="$DISKSLICE GPT { 512K freebsd-boot, 1M efi, auto freebsd-ufs / }
#!/bin/sh -x
# Make diskname independante
gpart modify -l freebsd-boot -i 1 ada0
gpart modify -l efi -i 2 ada0
gpart modify -l root -i 3 ada0
# Make EFI happy
mount_msdosfs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
after svn commit r357771 all CURRENT boxes with nvidia boards fail to compile
the driver:
Somebody seeing this, too?
[...]
===> src/nvidia-modeset (all)
machine -> /usr/src/sys/amd64/include
x86 -> /usr/src/sys/x86/include
touch
Hi Andreas,
No, nothing new on this front. I don't have any of this hardware nor
do I work for Intel, and nothing I see in the code or published spec
would result in hangs. I don't have more cycles to spend on this
driver. So I suggest using 'hint.hwpstate_intel.0.disabled="1"' as a
workaround
Hello,
any new leads on this? As of what is in git on 2020-02-05, my computer
still hangs on kernel boot on "hwpstate_intel0: on cpu0"
I guess it would have been easier to debug a panic. Setting
debug.hwpstate_verbose=1 doesn't really give any difference in output.
Best regards
Andreas
On
(Please send the followup to freebsd-testing@ and note Reply-To is set.)
FreeBSD CI Weekly Report 2020-02-09
===
Here is a summary of the FreeBSD Continuous Integration results for the period
from 2020-02-03 to 2020-02-09.
During this period, we have:
* 2010
On Mon, Feb 10, 2020 at 6:53 AM David Wolfskill wrote:
>
> Looks as if the same thing affected both my laptop and my build machine
> -- each updated from r357688 (built yesterday & smoke-tested without
> incident). While I got some screenshots for the laptop, I have a serial
> console for the
10 matches
Mail list logo
