[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#499231: Kernel Panic on boot



>On Sep 17, 2008, at 4:02 AM, Rick Thomas wrote:

>> I have another system running Sid.  I haven't done a dist-upgrade  
>> on it yet.  So I'll see what happens there.

> I did the dist-upgrade on my other G4 running Sid, and the oops  
> doesn't happen.
>
> Looking at the syslog extracts, it seems that the failing machine  
> oops-es when it's trying to initialize its Radeon video driver.  The  
> machine that doesn't oops has an ATI Rage video card.  The traceback  
> also mentions radeon.  So that's probably where the problem lies.
>
> Do others with Radeon cards have this problem?

Yes.  My kernel is OOPsing during boot sequence after an upgrade as
well.  And I do have a Radeon card.

06:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA controller])
        Subsystem: PC Partner Limited Radeon X300 (PCIE)
        Flags: bus master, fast devsel, latency 0, IRQ 12
        Memory at d0000000 (32-bit, prefetchable) [size=128M]
        I/O ports at a000 [size=256]
        Memory at e5000000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at e4000000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Express Endpoint, MSI 00
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [100] Advanced Error Reporting <?>
        Kernel modules: radeonfb

06:00.1 Display controller: ATI Technologies Inc RV370 [Radeon X300SE]
        Subsystem: PC Partner Limited Radeon X300SE
        Flags: bus master, fast devsel, latency 0
        Memory at e5010000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] Express Endpoint, MSI 00

I had to reinstall from a Lenny netinst CD to get the machine to boot again.

Please let me know if there's anything I can do to help test/debug.







Reply to: