Re: r259580 breaks radeonkms

On 2014-08-06 02:35, Roger Pau Monné wrote:
> On 06/08/14 02:37, Nathan Whitehorn wrote:
>> Kernels with r269580 will panic when loading the radeonkms driver in
>> pmap_page_set_memattr(). This probably indicates a bug in radeonkms, 
>> but
>> the system is unusable in the meantime.
>> -Nathan
> 
> I seem to be able to load radeonkms just fine after r269580:

It's possible that it is related to actually using it, rather than 
loading the module. I was only testing them together. I'm using vt and 
the panic (page fault in kernel mode) occurs when TTM tries to set 
memory attributes on some page while starting X. Before the panic, I see 
all the normal Radeon module messages as you do, so the module seems to 
have actually loaded correctly.  The KMS console also seems to be 
functional enough to display the panic message, so I suspect it's X that 
triggers it.
-Nathan

> # kldload radeonkms
> info: [drm] Initialized drm 1.1.0 20060810
> drmn0: <ATI FireMV 2260> on vgapci0
> vgapci0: attempting to allocate 1 MSI vectors (1 supported)
> msi: routing MSI IRQ 276 to local APIC 0 vector 48
> vgapci0: using IRQ 276 for MSI
> info: [drm] MSI enabled 1 message(s)
> info: [drm] RADEON_IS_PCIE
> info: [drm] initializing kernel modesetting (RV620 0x1002:0x95CF 
> 0x1002:0x2143).
> info: [drm] register mmio base: 0xF7DF0000
> info: [drm] register mmio size: 65536
> info: [drm] radeon_atrm_get_bios: ===> Try ATRM...
> info: [drm] radeon_atrm_get_bios: pci_find_class() found: 0:2:0:0,
> vendor=1002, device=95cf
> info: [drm] radeon_atrm_get_bios: Get ACPI device handle
> info: [drm] radeon_acpi_vfct_bios: ===> Try VFCT...
> info: [drm] radeon_acpi_vfct_bios: Get "VFCT" ACPI table
> info: [drm] radeon_acpi_vfct_bios: Failed to get "VFCT" table: 
> AE_NOT_FOUND
> info: [drm] igp_read_bios_from_vram: ===> Try IGP's VRAM...
> info: [drm] igp_read_bios_from_vram: VRAM base address: 0xe0000000
> info: [drm] igp_read_bios_from_vram: Map address: 0xfffff800e0000000
> (262144 bytes)
> info: [drm] igp_read_bios_from_vram: Incorrect BIOS signature: 0x200F
> info: [drm] radeon_read_bios: ===> Try PCI Expansion ROM...
> info: [drm] radeon_read_bios: Map address: 0xfffff800000c0000 (131072 
> bytes)
> info: [drm] ATOM BIOS: 113
> drmn0: info: VRAM: 256M 0x0000000000000000 - 0x000000000FFFFFFF (256M 
> used)
> drmn0: info: GTT: 512M 0x0000000010000000 - 0x000000002FFFFFFF
> info: [drm] Detected VRAM RAM=256M, BAR=256M
> info: [drm] RAM width 64bits DDR
> [TTM] Zone  kernel: Available graphics memory: 3129302 kiB
> [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
> [TTM] Initializing pool allocator
> info: [drm] radeon: 256M of VRAM memory ready
> info: [drm] radeon: 512M of GTT memory ready.
> info: [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
> info: [drm] Driver supports precise vblank timestamp query.
> info: [drm] radeon: irq initialized.
> info: [drm] GART: num cpu pages 131072, num gpu pages 131072
> info: [drm] probing gen 2 caps for device 8086:340a = 2/0
> info: [drm] enabling PCIE gen 2 link speeds, disable with 
> radeon.pcie_gen2=0
> info: [drm] Loading RV620 Microcode
> firmware: 'radeonkmsfw_RV620_pfp' version 0: 2304 bytes loaded at
> 0xffffffff8214b0d0
> firmware: 'radeonkmsfw_RV620_me' version 0: 21504 bytes loaded at
> 0xffffffff8214d0d0
> firmware: 'radeonkmsfw_R600_rlc' version 0: 3072 bytes loaded at
> 0xffffffff821530d0
> info: [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
> drmn0: info: WB enabled
> drmn0: info: fence driver on ring 0 use gpu addr 0x0000000010000c00
> and cpu addr 0x0xfffff80058ab6c00
> drmn0: info: fence driver on ring 3 use gpu addr 0x0000000010000c0c
> and cpu addr 0x0xfffff80058ab6c0c
> info: [drm] ring test on 0 succeeded in 0 usecs
> info: [drm] ring test on 3 succeeded in 1 usecs
> info: [drm] ib test on ring 0 succeeded in 0 usecs
> info: [drm] ib test on ring 3 succeeded in 0 usecs
> info: [drm] radeon_device_init: Taking over the fictitious range
> 0xe0000000-0xf0000000
> iicbus0: <Philips I2C bus> on iicbb0 addr 0xff
> iic0: <I2C generic I/O> on iicbus0
> iicbus1: <Philips I2C bus> on iicbb1 addr 0x0
> iic1: <I2C generic I/O> on iicbus1
> iicbus2: <Philips I2C bus> on iicbb2 addr 0x0
> iic2: <I2C generic I/O> on iicbus2
> iicbus3: <Philips I2C bus> on iicbb3 addr 0x0
> iic3: <I2C generic I/O> on iicbus3
> iicbus4: <Philips I2C bus> on iicbb4 addr 0x0
> iic4: <I2C generic I/O> on iicbus4
> info: [drm] Radeon Display Connectors
> info: [drm] Connector 0:
> info: [drm]   DP-1
> info: [drm]   HPD2
> info: [drm]   DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 
> 0x7e6c
> info: [drm]   Encoders:
> info: [drm]     DFP1: INTERNAL_UNIPHY
> info: [drm] Connector 1:
> info: [drm]   DP-2
> info: [drm]   HPD4
> info: [drm]   DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 
> 0x7e2c
> info: [drm]   Encoders:
> info: [drm]     DFP2: INTERNAL_UNIPHY
> info: [drm] Internal thermal controller with fan control
> info: [drm] radeon: power management initialized
> info: [drm] fb mappable at 0xE0142000
> info: [drm] vram apper at 0xE0000000
> info: [drm] size 7299072
> info: [drm] fb depth is 24
> info: [drm]    pitch is 6912
> fbd0 on drmn0
> info: [drm] Initialized radeon 2.29.0 20080528
> 
> Although this is a headless server and still using sc. Can you post
> the output when loading the module?
> 
> Roger.
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe_at_freebsd.org"