Bug 237686 - graphics/drm-fbsd12.0-kmod panic on 12.0-RELEASE-p3 with Radeon R5 230
Summary: graphics/drm-fbsd12.0-kmod panic on 12.0-RELEASE-p3 with Radeon R5 230
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-x11 (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-01 12:21 UTC by Torfinn Ingolfsen
Modified: 2019-07-29 12:36 UTC (History)
4 users (show)

See Also:

Attachments
/var/crash/core.txt.0 (235.26 KB, text/plain)
2019-05-01 12:21 UTC, Torfinn Ingolfsen 		no flags Details
/var/crash/core.txt.1 (242.37 KB, text/plain)
2019-05-01 12:23 UTC, Torfinn Ingolfsen 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Torfinn Ingolfsen 2019-05-01 12:21:40 UTC 
Created attachment 204141 [details]
/var/crash/core.txt.0

A machine with a Radeon R5 230 (which is a rebrand of Radeon HD 6450 AFAIUI) panics after a few hours  if running Xorg and with Firefox open. No specific activity on the user needed. Before the Radeon R5 230 I had a nVidia card in it (old) and the machine ran for several weeks with that, so I think the machine hardware is good.

The machine runs
root@kg-core2# uname -a
FreeBSD kg-core2.kg4.no 12.0-RELEASE-p3 FreeBSD 12.0-RELEASE-p3 GENERIC  amd64
root@kg-core2# freebsd-version -ku
12.0-RELEASE-p3
12.0-RELEASE-p3
updated via freebsd-update

Packages installed via pkg, no ports on this machine.
root@kg-core2# pkg info drm*
drm-fbsd12.0-kmod-4.16.g20190424
drm-kmod-g20181126

panic from /var/log/messages
Apr 30 20:01:28 kg-core2 syslogd: last message repeated 1 times
Apr 30 20:01:28 kg-core2 kernel: Fatal trap 12: page fault while in kernel mode
Apr 30 20:01:28 kg-core2 kernel: cpuid = 6; apic id = 08
Apr 30 20:01:28 kg-core2 kernel: fault virtual address  = 0x7ea
Apr 30 20:01:28 kg-core2 kernel: fault code             = supervisor read data, page not present
Apr 30 20:01:28 kg-core2 kernel: instruction pointer    = 0x20:0xffffffff828d69bc
Apr 30 20:01:28 kg-core2 kernel: stack pointer          = 0x28:0xfffffe009d564200
Apr 30 20:01:28 kg-core2 kernel: frame pointer          = 0x28:0xfffffe009d564230
Apr 30 20:01:28 kg-core2 kernel: code segment           = base rx0, limit 0xfffff, type 0x1b
Apr 30 20:01:28 kg-core2 kernel:                        = DPL 0, pres 1, long 1, def32 0, gran 1
Apr 30 20:01:28 kg-core2 kernel: processor eflags       = interrupt enabled, resume, IOPL = 3
Apr 30 20:01:28 kg-core2 kernel: current process                = 1126 (X:rcs0)
Apr 30 20:01:28 kg-core2 kernel: trap number            = 12
Apr 30 20:01:28 kg-core2 kernel: panic: page fault
Apr 30 20:01:28 kg-core2 kernel: cpuid = 6
Apr 30 20:01:28 kg-core2 kernel: time = 1556647242
Apr 30 20:01:28 kg-core2 kernel: KDB: stack backtrace:
Apr 30 20:01:28 kg-core2 kernel: #0 0xffffffff80be7977 at kdb_backtrace+0x67
Apr 30 20:01:28 kg-core2 kernel: #1 0xffffffff80b9b563 at vpanic+0x1a3
Apr 30 20:01:28 kg-core2 kernel: #2 0xffffffff80b9b3b3 at panic+0x43
Apr 30 20:01:28 kg-core2 kernel: #3 0xffffffff8107496f at trap_fatal+0x35f
Apr 30 20:01:28 kg-core2 kernel: #4 0xffffffff810749c9 at trap_pfault+0x49
Apr 30 20:01:28 kg-core2 kernel: #5 0xffffffff81073fee at trap+0x29e
Apr 30 20:01:28 kg-core2 kernel: #6 0xffffffff8104f435 at calltrap+0x8
Apr 30 20:01:28 kg-core2 kernel: #7 0xffffffff828b16ba at radeon_cs_ioctl+0xa4a
Apr 30 20:01:28 kg-core2 kernel: #8 0xffffffff829acca6 at drm_ioctl_kernel+0xf6
Apr 30 20:01:28 kg-core2 kernel: #9 0xffffffff829acf41 at drm_ioctl+0x281
Apr 30 20:01:28 kg-core2 kernel: #10 0xffffffff829eebd4 at linux_file_ioctl+0x204
Apr 30 20:01:28 kg-core2 kernel: #11 0xffffffff80c04f3d at kern_ioctl+0x26d
Apr 30 20:01:28 kg-core2 kernel: #12 0xffffffff80c04c5e at sys_ioctl+0x15e
Apr 30 20:01:28 kg-core2 kernel: #13 0xffffffff81075449 at amd64_syscall+0x369
Apr 30 20:01:28 kg-core2 kernel: #14 0xffffffff8104fd1d at fast_syscall_common+0x101
Apr 30 20:01:28 kg-core2 kernel: Uptime: 21h32m35s
Apr 30 20:01:28 kg-core2 kernel: ---<<BOOT>>---
Comment 1 Torfinn Ingolfsen 2019-05-01 12:22:56 UTC 
The panic is repeatable
May  1 02:34:52 kg-core2 kernel: Fatal trap 12: page fault while in kernel mode
May  1 02:34:52 kg-core2 kernel: cpuid = 4; apic id = 04
May  1 02:34:52 kg-core2 kernel: fault virtual address  = 0x88e
May  1 02:34:52 kg-core2 kernel: fault code             = supervisor read data, page not present
May  1 02:34:52 kg-core2 kernel: instruction pointer    = 0x20:0xffffffff828d69bc
May  1 02:34:52 kg-core2 kernel: stack pointer          = 0x28:0xfffffe009d55d200
May  1 02:34:52 kg-core2 kernel: frame pointer          = 0x28:0xfffffe009d55d230
May  1 02:34:52 kg-core2 kernel: code segment           = base rx0, limit 0xfffff, type 0x1b
May  1 02:34:52 kg-core2 kernel:                        = DPL 0, pres 1, long 1, def32 0, gran 1
May  1 02:34:52 kg-core2 kernel: processor eflags       = interrupt enabled, resume, IOPL = 3
May  1 02:34:52 kg-core2 kernel: current process                = 1457 (X:rcs0)
May  1 02:34:52 kg-core2 kernel: trap number            = 12
May  1 02:34:52 kg-core2 kernel: panic: page fault
May  1 02:34:52 kg-core2 kernel: cpuid = 4
May  1 02:34:52 kg-core2 kernel: time = 1556670846
May  1 02:34:52 kg-core2 kernel: KDB: stack backtrace:
May  1 02:34:52 kg-core2 kernel: #0 0xffffffff80be7977 at kdb_backtrace+0x67
May  1 02:34:52 kg-core2 kernel: #1 0xffffffff80b9b563 at vpanic+0x1a3
May  1 02:34:52 kg-core2 kernel: #2 0xffffffff80b9b3b3 at panic+0x43
May  1 02:34:52 kg-core2 kernel: #3 0xffffffff8107496f at trap_fatal+0x35f
May  1 02:34:52 kg-core2 kernel: #4 0xffffffff810749c9 at trap_pfault+0x49
May  1 02:34:52 kg-core2 kernel: #5 0xffffffff81073fee at trap+0x29e
May  1 02:34:52 kg-core2 kernel: #6 0xffffffff8104f435 at calltrap+0x8
May  1 02:34:52 kg-core2 kernel: #7 0xffffffff828b16ba at radeon_cs_ioctl+0xa4a
May  1 02:34:52 kg-core2 kernel: #8 0xffffffff829acca6 at drm_ioctl_kernel+0xf6
May  1 02:34:52 kg-core2 kernel: #9 0xffffffff829acf41 at drm_ioctl+0x281
May  1 02:34:52 kg-core2 kernel: #10 0xffffffff829eebd4 at linux_file_ioctl+0x204
May  1 02:34:52 kg-core2 kernel: #11 0xffffffff80c04f3d at kern_ioctl+0x26d
May  1 02:34:52 kg-core2 kernel: #12 0xffffffff80c04c5e at sys_ioctl+0x15e
May  1 02:34:52 kg-core2 kernel: #13 0xffffffff81075449 at amd64_syscall+0x369
May  1 02:34:52 kg-core2 kernel: #14 0xffffffff8104fd1d at fast_syscall_common+0x101
May  1 02:34:52 kg-core2 kernel: Uptime: 6h32m52s
May  1 02:34:52 kg-core2 kernel: ---<<BOOT>>---
Comment 2 Torfinn Ingolfsen 2019-05-01 12:23:49 UTC 
Created attachment 204142 [details]
/var/crash/core.txt.1
Comment 3 Torfinn Ingolfsen 2019-05-01 12:29:06 UTC 
The setup / configuration for graphics is
root@kg-core2# grep radeon /etc/rc.conf
# try radeonkms instead
kld_list="/boot/modules/radeonkms.ko"
root@kg-core2# grep syscons /boot/loader.conf
hw.syscons.disable=1

Oh, and I tried the amdgpu module instead of radeonkms, but it doesn't have the correct resolution, it shows up in 1280x1024 instead of 1920x1080.
Comment 4 mambur 2019-06-03 08:56:16 UTC 
I have a similar problem. I use two screens (DVI + VGA). When using kde5, there is a panic kernel.

# uname -a
FreeBSD mambur.ug.local 12.0-STABLE FreeBSD 12.0-STABLE r348111 M11 amd64

# grep kld /etc/rc.conf
kld_list = "/ boot / modules / radeonkms.ko"
Comment 5 Niclas Zeising freebsd_committer freebsd_triage 2019-07-10 08:54:45 UTC 
Hi!
Is this still an issue?
If so, can you please report it as an issue on our github, https://github.com/FreeBSDDesktop/kms-drm , and link it here.
Thanks!
Comment 6 Niclas Zeising freebsd_committer freebsd_triage 2019-07-29 12:36:51 UTC 
Freedback timeout.