Re: More amd64 drmkms radeon

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

A DRMKMS kernel from 15th works as suggested above - switches to
1280x1024 and is fine after (Xorg panics earlier; with the latest
build from yesterday it even wedged the machine completely).

On the other hand yesterday's kernel panics as follows:
----
drm: register mmio size: 65536
pci_io_find: expected type i/o, found mem
DRM error in radeon_get_bios: Unable to locate a BIOS ROM
drm: Using generic clock info
radeon0: info: GTT: 256M 0xE0000000 - 0xEFFFFFFF
drm: Generation 2 PCI interface, using max accessible memory
radeon0: info: VRAM: 128M 0x00000000D8000000 - 0x00000000DFFFFFFF (128M used)
drm: Detected VRAM RAM=80M, BAR=128M
drm: RAM width 128bits DDR
Zone  kernel: Available graphics memory: 1065574 kiB
drm: radeon: 128M of VRAM memory ready
drm: radeon: 256M of GTT memory ready.
drm: radeon: 1 quad pipes, 1 Z pipes initialized.
radeon0: info: WB disabled
radeon0: info: fence driver on ring 0 use gpu addr 0x00000000e0000000
and cpu addr 0x0xffff800037393000
drm: Supports vblank timestamp caching Rev 2 (21.10.2013).
drm: Driver supports precise vblank timestamp query.
DRM debug in drm_irq_install: irq=268570634
radeon0: interrupting at ioapic0 pin 16 (radeon)
drm: radeon: irq initialized.
DRM debug in r100_cp_init_microcode:
drm: Loading R300 Microcode
drm kern error: radeon_cp: Failed to load firmware "radeon/R300_cp.bin"
DRM error in r100_cp_init: Failed to load firmware!
radeon0: error: failed initializing CP (-2).
radeon0: error: Disabling GPU acceleration
drm: radeon: cp finalized
panic: kernel diagnostic assertion "ttm->caching_state == tt_cached"
failed: file "../../../../external/bsd/drm2/dist/drm/ttm/ttm_tt.c",
line 423
fatal breakpoint trap in supervisor mode
trap type 1 code 0 rip ffffffff8028bcfd cs 8 rflags 246 cr2 0 ilevel 0
rsp fffffe8045b27bb8
curlwp 0xfffffe8045b3d1a0 pid 0.57 lowest kstack 0xfffffe8045b242c0
Stopped in pid 0.57 (system) at netbsd:breakpoint+0x5:  leave
db{0}> bt
breakpoint() at netbsd:breakpoint+0x5
vpanic() at netbsd:vpanic+0x13c
kern_assert() at netbsd:kern_assert+0x4f
ttm_tt_swapout() at netbsd:ttm_tt_swapout+0x123
ttm_bus_dma_unpopulate() at netbsd:ttm_bus_dma_unpopulate+0x35
ttm_tt_destroy() at netbsd:ttm_tt_destroy+0x42
ttm_bo_cleanup_memtype_use() at netbsd:ttm_bo_cleanup_memtype_use+0x3a
ttm_bo_release() at netbsd:ttm_bo_release+0x36d
radeon_bo_unref() at netbsd:radeon_bo_unref+0x3f
radeon_wb_fini() at netbsd:radeon_wb_fini+0xe3
r300_init() at netbsd:r300_init+0x148
radeon_device_init() at netbsd:radeon_device_init+0x4d7
radeon_driver_load_kms() at netbsd:radeon_driver_load_kms+0x6e
drm_dev_register() at netbsd:drm_dev_register+0x87
drm_pci_attach() at netbsd:drm_pci_attach+0x28a
radeon_attach_real() at netbsd:radeon_attach_real+0x68
config_mountroot_thread() at netbsd:config_mountroot_thread+0x2c

On 18 August 2014 20:06, Patrick Welche <prlw1%cam.ac.uk@localhost> wrote:
> On Fri, Aug 15, 2014 at 04:47:42PM +0100, Patrick Welche wrote:
>> On Fri, Aug 15, 2014 at 04:09:03PM +0100, Robert Swindells wrote:
>> >
>> > What does it do now ?
>>
>> Now it panics (and rebuilt the X server with symbols just in case):
>
> It (radeon) no longer panics!
>
> P

Chavdar

(BTW I finally sat down and configured serial console on this machine;
took me all of two minutes - would have saved me all those screenshots
taken with a phone camera then manually input... or even
text-recognized...).


-- 
----