Bug 58568

Summary: [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
Product: DRI Reporter: Paul Menzel <paulepanter>
Component: DRM/RadeonAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED NOTABUG QA Contact:
Severity: normal    
Priority: medium CC: paulepanter
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:

Description Paul Menzel 2012-12-20 11:50:59 UTC
Since installing Linux 3.7.1, it happened twice that the firmware was not loaded.

[   16.874010] calling  radeon_init+0x0/0x1000 [radeon] @ 585
[   16.874017] [drm] radeon kernel modesetting enabled.
[   16.874410] [drm] initializing kernel modesetting (RS780 0x1002:0x9610 0x1849:0x9610).
[   16.874447] [drm] register mmio base: 0xFDFF0000
[   16.874449] [drm] register mmio size: 65536
[   16.874490] radeon 0000:01:05.0: BAR 6: can't assign [??? 0x00000000 flags 0x0] (bogus alignment)
[   16.874518] [drm:radeon_get_bios] *ERROR* Unable to locate a BIOS ROM
[   16.874565] radeon 0000:01:05.0: Fatal error during GPU init
[   16.874604] [drm] radeon: finishing device.
[   16.874606] [TTM] Memory type 2 has not been initialized
[   16.875830] radeon: probe of 0000:01:05.0 failed with error -22
[   16.875936] initcall radeon_init+0x0/0x1000 [radeon] returned 0 after 1811 usec

I did not experience that with Linux 3.7. User space is Debian Sid/unstable and it did not change between the update as far as I see.

When restarting it seems to work alright.

Though I do not see any suspicious commits for Linux 3.7.1.

$ git log --format=oneline v3.7..v3.7.1
cc8605070a58f12b79c62f369a0446d89a7ca337 Linux 3.7.1
53730b4c10781998bb872fce768f578ab4e09aec Staging: bcm: Add two products and remove an existing product.
5ebf81ae05c971619ab8a71504b47a4bc30efbb2 rcu: Fix batch-limit size problem
2083ca13781c4e88049b530c954dd48b3f30ddf2 USB: EHCI: bugfix: urb->hcpriv should not be NULL
9eb7f6942b507dc7f94ae380e025cd610d2de269 perf test: fix a build error on builtin-test
45d6c5dd9615c481066d3377ad35edc681393fac cdc-acm: implement TIOCSSERIAL to avoid blocking close(2)
f99b4b46d8e4a98fc1c4386a78f5a94296b6ebb0 ring-buffer: Fix race between integrity check and readers
7c3432b14e30e1aebb7a19ea52a05928b383b272 ring-buffer: Fix NULL pointer if rb_set_head_page() fails
5bab98768136ee54b82ef6dd7fc0ec1c41ef8431 ftrace: Clear bits properly in reset_iter_read()
5338f92b421c257ff09d0ef65fde4447eccb0c95 xhci: Extend Fresco Logic MSI quirk.
efda03ca0a93fb485723ae3178b75e59af362474 USB: OHCI: workaround for hardware bug: retired TDs not added to the Done Queue
efcda31e6023a8593ba93c556fe134023b77ba56 ACPI / video: Add "Asus UL30VT" to ACPI video detect blacklist
77dfd2e6c6d83aa806e56e297b8c9cc122a3b0e4 ACPI / video: ignore BIOS initial backlight value for HP Folio 13-2000
9c3f6f654da8dc484dabaa4c8805f70d64d7b000 ACPI / PNP: Do not crash due to stale pointer use during system resume
87f8b7c1928dac3cd0df0d1e6682edb29c8c5c78 ACPI / PM: Add Sony Vaio VPCEB1S1E to nonvs blacklist.
90e760ae6415d828b729700c2da254a2266ffdb1 ACPI / battery: Correct battery capacity values on Thinkpads
ef984b4cd5baa2f202adcc77e03ff2953cc71df9 USB: mark uas driver as BROKEN
bf9694fb59594c92d791bc728b5aa13dab06a15a USB: cp210x: add Virtenio Preon32 device id
bf9a2254ff6fd799df438f5b392c3e884fd03177 usb: ftdi_sio: fixup BeagleBone A5+ quirk
0b23bbd5a7070e0ba00de1d742c1f3269413ea9c USB: ftdi_sio: Add support for Newport AGILIS motor drivers
a634f92ce1b353f2f3ddd9b331a943414fd50f31 USB: option: blacklist network interface on Huawei E173
673531802c45aaccb2dec0c6ed2fe6013d155d50 USB: add new zte 3g-dongle's pid to option.c
a305b4e87b0e4dca16ec8856bf5d1d44ddbd4763 x86: hpet: Fix masking of MSI interrupts
dc96e8023d0803688f1e56a9f52f7213bb2a8204 ezusb: add dependency to USB
83c9bff26b4445bfaebbe9317d4ad73f69c68fe6 telephony: ijx: buffer overflow in ixj_write_cid()
ec92de46a243f6d014c8c42276b4b0cd72c4c9c5 x86,AMD: Power driver support for AMD's family 16h processors
5a11e1dcbc8b64bc76dde2a8c96646bab5e41d6a clk: ux500: fix bit error
13a4fcec5484b83b61926d5304d86349e5530027 mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls
Comment 1 Alex Deucher 2012-12-20 13:34:45 UTC
Make sure pci quirks are enabled in your kernel config.  Can you bisect?
Comment 2 Paul Menzel 2012-12-21 15:19:53 UTC
(In reply to comment #1)
> Make sure pci quirks are enabled in your kernel config.  Can you bisect?

That was it. I had those disabled! Sorry for the noise.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.