On 2021-02-09 02:20, Emmanuel Vadot wrote:
> Alastair: Can you report a bug there :
> https://github.com/freebsd/drm-kmod/issues
https://github.com/freebsd/drm-kmod/issues/64
___
freebsd-current@freebsd.org mailing list
On 3/9/21 9:31 AM, Alastair Hogge wrote:
On 2021-02-08 21:01, Hans Petter Selasky wrote:
On 2/8/21 1:53 PM, Alastair Hogge wrote:
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
Hi,
Maybe you could do a
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
> Hi,
>
> Maybe you could do a hack and edit the
Sorry, please ignore previous reply, the modified sysctl is still
running,
the output earlier, was from the stock binary.
On 2021-02-09 14:25, Alastair Hogge wrote:
> On 2021-02-08 21:01, Hans Petter Selasky wrote:
>> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>>> Boot to multi-user; login (getty):
On 2021-02-08 21:01, Hans Petter Selasky wrote:
> On 2/8/21 1:53 PM, Alastair Hogge wrote:
>> Boot to multi-user; login (getty):
>> $ doas kldload /boot/modules/amdgpu.ko
>> $ sysctl
>> [panic]
>>
>> ..is a guaranteed way to panic my system.
>
> Hi,
>
> Maybe you could do a hack and edit the
On Mon, 08 Feb 2021 21:05:24 +0300
Greg V wrote:
>
>
> On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
> > On 2021-02-04 17:50, Emmanuel Vadot wrote:
> >
> > [...]
> >
> >> Only happens with drm when you do what ?
> >
> > Boot to multi-user; login (getty):
> > $ doas kldload
On Mon, Feb 8, 2021 at 04:53, Alastair Hogge wrote:
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
On 2/8/21 1:53 PM, Alastair Hogge wrote:
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
Hi,
Maybe you could do a hack and edit the sysctl source code:
1) print the sysctl before it is queried.
2) sleep 1
On 2021-02-04 17:50, Emmanuel Vadot wrote:
[...]
> Only happens with drm when you do what ?
Boot to multi-user; login (getty):
$ doas kldload /boot/modules/amdgpu.ko
$ sysctl
[panic]
..is a guaranteed way to panic my system.
___
On Thu, Feb 04, 2021 at 10:50:29AM +0100, Emmanuel Vadot wrote:
> On Wed, 3 Feb 2021 08:03:24 -0800
> Steve Kargl wrote:
>
> > On Wed, Feb 03, 2021 at 10:42:21AM +0200, Andriy Gapon wrote:
> > > On 03/02/2021 07:08, Steve Kargl wrote:
> > > > Fatal trap 12: page fault while in kernel mode
> > >
On Wed, 3 Feb 2021 08:03:24 -0800
Steve Kargl wrote:
> On Wed, Feb 03, 2021 at 10:42:21AM +0200, Andriy Gapon wrote:
> > On 03/02/2021 07:08, Steve Kargl wrote:
> > > Fatal trap 12: page fault while in kernel mode
> > > cpuid = 0; apic id = 00
> > > fault virtual address = 0xc374
> > >
On Wed, Feb 03, 2021 at 10:42:21AM +0200, Andriy Gapon wrote:
> On 03/02/2021 07:08, Steve Kargl wrote:
> > Fatal trap 12: page fault while in kernel mode
> > cpuid = 0; apic id = 00
> > fault virtual address = 0xc374
> > fault code = supervisor read data, page not present
> >
On 03/02/2021 07:08, Steve Kargl wrote:
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0xc374
> fault code= supervisor read data, page not present
> instruction pointer = 0x20:0xef411f
> stack pointer = 0x28:0x4074e97c
% pkg info | grep kmod
drm-devel-kmod-5.4.62.g20210128 DRM modules for the linuxkpi-basedr
KMS components (development version)
gpu-firmware-kmod-g20201213Firmware modules for the linuxkpi-based
KMS components
mobile dumped core - see /var/crash/vmcore.0
Tue Feb 2 20:56:29 PST 2021
14 matches
Mail list logo
