building
graphics/drm-devel-kmod in poudriere with matching sources and
kernel.
Probably due to 8b83d7e0ee54416b0ee58bd85f9c0ae7fb3357a1
--
Evilham
tching drm-devel-kmod package (built with matching
source on matching kernel).
The hw being: AMD Ryzen 7 PRO 2700U w/ Radeon Vega Mobile Gfx
--
Evilham
SD-CURRENT; it
seems like this question might be a better fit for
freebsd-questions@, since it is related to systems in general.
Cheers,
--
Evilham
lpful:
I was unable to build the kernel with an up to date
drm-current-kmod, but as soon as I switched to drm-devel-kmod, I
was able to.
The running kernel was uname -K: 1300133.
Thanks everyone for having added their input here.
--
Evilham
___
freebsd-
or
not that is to be considered a bug and needs a PR.
--
Evilham
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Matthew's changes into curent branch
% git merge mattmacy/projects/openzfs_vendor
# Get OpenZFS's code
% git clone https://github.com/zfsonfreebsd/ZoF.git -b
projects/openzfs_vendor sys/contrib/openzfs
# Build, install as usual, maybe use a checkpoint ;-)
--
Evilham
On dl., gen. 20 2020, Hans Petter Selasky wrote:
^^^ my best guess is this is ACPI related :-(
ACPI has own debugging flags and options.
--HPS
Thank you, now reading handbook/acpi-overview.html in order to try
to get more info.
--
Evilham
failed, USB_ERR_TIMEOUT
usbd_setup_device_desc: getting device descriptor at addr 1
failed, USB_ERR_TIMEOUT
--
Evilham
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail
and
may be deleted before FreeBSD 13.0.
Jan 14 06:33:50 kernel: WARNING: Device "fb" is Giant locked and
may be deleted before FreeBSD 13.0.
I am guessing number 4 has to do with recent changes, and
shouldn't really affect the system if the devices are deleted? Is
there a way I
een using a locally built drm-kmod without patches (off
commit ee53eae) for a couple days with the latest HEAD.
Maybe the port just hasn't been rebuilt on FreeBSD infra yet?
In any case, and at your own risk you can give that a go.
--
Evilham
___
freebs
ck
Maybe for your relief: it looks like that build is working for me
:-), so no unintended non-NFS consequences here.
# uname -KiprsU
FreeBSD 13.0-CURRENT amd64 GENERIC-NODEBUG 1300066 1300066
Hopefully I can test NFS 4.2 soon.
Thank you for working on this!
it will not run xorg.
Have you seen the recent threads about this?
Particularly this with some steps that worked-for-me (tm):
https://lists.freebsd.org/pipermail/freebsd-current/2019-October/074660.html
--
Evilham
___
freebsd-current@freebsd.org mailing
goto retry;
cdev_pager_free_page(devobj, page);
}
11. Built the port in poudriere
12. Installed drm-devel-kmod
13. Reboot and profit
Thank you again for looking into this!
--
Evilham
___
freebsd-current@freebsd.org mailing list
htt
: I usually compile GENERIC-NODEBUG, if that results in the
dump being useless (sadly I can't tell), I can disable all the
performance goodies and compile GENERIC :-).
--
Evilham
Fatal trap 12: page fault while in kernel mode
cpuid = 2; apic id = 02
fault virtual address = 0xf8
fault code
: page fault while in kernel mode
*something, something*
fault mode = supervisor read data, page not present
Will try to get more details and a proper dump when I have some
time off (hopefully later today), just thought I'd warn before.
--
Evilham
On dg., set. 01 2019, Evilham wrote:
On dg., set. 01 2019, Guido Falsi wrote:
Hi,
I'm experiencing a recurring panic I can trigger repeatably.
I was going to send a similar email a few hours ago to the
current
ML but decided to debug some more before that.
FWIW: I am not 100% sure I
panic, I am missing a
cable ATM to get a full dump, but I do think they sound very
similar.
--
Evilham
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "fr
I think that must go in /boot/loader.conf or just for one boot you
can add it from the boot loader as a custom option with "set
hw..." then "boot".
--
Evilham
___
freebsd-current@freebsd.org mailing list
https://lists.freebs
ZFS in a geli-encrypted partition in a
GPT disk, I recall some manual fiddling but those were likely
because I needed sth particular.
--
Evilham
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscr
On ds., jul. 20 2019, Evilham wrote:
Serious issue:
I was just debugging this right now, more infos with a proper
bug
report will come, but I think the system encounters a deadlock
sometimes with the drm-kmod / amdgpu which results in a kernel
panic.
It is a serious issue, but it allows me
Hey,
thanks for the feedback and your work, didn't think this would be
interesting for anyone but the laptop owners.
On ds., jul. 20 2019, Greg V. wrote:
On July 20, 2019 1:54:47 AM GMT+03:00, Evilham
wrote:
it even suspends and resumes back to X
Wow, that's great news! Desktop Ryzen
y that I'm posting images instead of plain text. I have no
idea how to
do kernel dumps during the bootload of a live image. I would be
happy to
post more information if required, let me know how I can do it.
No worries, it took me forever to find the bug that had the
sysctl.
I ho
22 matches
Mail list logo
