Messages in this thread | | | Subject | Re: [PATCH] radeonfb: (#2) Implement proper workarounds for PLL accesses | From | Andreas Schwab <> | Date | Fri, 08 Apr 2005 01:58:03 +0200 |
| |
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> Yes, that's very extreme, I suspect somebody is banging on set_par or > something like that.
fb_setcolreg is it.
kernel: radeonfb_set_par kernel: radeon_write_pll_regs: radeon_pll_errata_after_data kernel: radeon_write_pll_regs: radeon_pll_errata_after_data kernel: radeon_write_mode: radeon_pll_errata_after_data kernel: radeonfb_engine_reset: radeon_pll_errata_after_data last message repeated 2 times kernel: radeonfb_setcolreg: radeon_pll_errata_after_data last message repeated 767 times kernel: radeonfb_set_par kernel: radeon_write_pll_regs: radeon_pll_errata_after_data kernel: radeon_write_pll_regs: radeon_pll_errata_after_data kernel: radeon_write_mode: radeon_pll_errata_after_data kernel: radeonfb_engine_reset: radeon_pll_errata_after_data last message repeated 2 times kernel: radeonfb_setcolreg: radeon_pll_errata_after_data last message repeated 911 times
kernel: radeonfb_set_par kernel: radeon_write_pll_regs: radeon_pll_errata_after_data kernel: radeon_write_pll_regs: radeon_pll_errata_after_data kernel: radeon_write_mode: radeon_pll_errata_after_data kernel: radeonfb_engine_reset: radeon_pll_errata_after_data last message repeated 2 times kernel: radeonfb_setcolreg: radeon_pll_errata_after_data last message repeated 193 times kernel: agpgart: Putting AGP V2 device at 0000:00:0b.0 into 1x mode kernel: agpgart: Putting AGP V2 device at 0000:00:10.0 into 1x mode kernel: radeonfb_setcolreg: radeon_pll_errata_after_data last message repeated 191 times
Andreas.
-- Andreas Schwab, SuSE Labs, schwab@suse.de SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different." - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |