Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 405776 [details] pm-suspend.log Description of problem: I've noticed recently I've been getting lockups of the keyboard and mouse on resume. Everything else seems to start fine, but the mouse doesn't move and the keyboard doesn't respond (including the caps-lock). It doesn't happen every resume, and more often and not, resume works without issue. Everything else seems to work, including the network coming out (or it appears to). Next time I will attempt to SSH the machine. I'm using current f13, and it's been happening for about 3 weeks. lpsci shows: $ lspci 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12) 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12) 00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06) 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06) 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06) 00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06) 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06) 00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06) 00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6) 00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06) 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller (rev 06) 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06) 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06) 02:00.0 VGA compatible controller: ATI Technologies Inc Device 9488 02:00.1 Audio device: ATI Technologies Inc RV710/730 04:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) 07:00.0 SD Host controller: Ricoh Co Ltd Device e822 (rev 01) 07:00.1 System peripheral: Ricoh Co Ltd Device e230 (rev 01) 07:00.2 System peripheral: Ricoh Co Ltd Device e852 (rev 01) 07:00.3 FireWire (IEEE 1394): Ricoh Co Ltd Device e832 (rev 01) 09:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe (rev 10) ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02) ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02) ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
Do you know the exact name of that graphics card?
I'm not sure of the answer to the question, but here's the output of lspci -vvn for the VGA device. $ sudo lspci -s 02:00.0 -vvn 02:00.0 0300: 1002:9488 (prog-if 00 [VGA controller]) Subsystem: 1028:0419 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR+ <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 31 Region 0: Memory at d0000000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at 2000 [size=256] Region 2: Memory at cfef0000 (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at cfe00000 [disabled] [size=128K] Capabilities: [50] Power Management version 3 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [58] Express (v2) Legacy Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <4us, L1 unlimited ExtTag+ AttnBtn- AttnInd- PwrInd- RBE+ FLReset- DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x16, ASPM L0s L1, Latency L0 <64ns, L1 <1us ClockPM- Surprise- LLActRep- BwNot- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Not Supported, TimeoutDis- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis-, Selectable De-emphasis: -6dB Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0a00c Data: 41a1 Capabilities: [100 v1] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Kernel driver in use: radeon Kernel modules: radeon
Oh, and I tried to ssh the box after my last lockup and there was no network. It's a very hard lockup.
the /var/log/Xorg.0.log file says: [ 43.161] (--) RADEON(0): Chipset: "ATI Mobility Radeon HD 4670" (ChipID = 0x9488) I'll attach Xorg.0.log in case it's useful.
Created attachment 413101 [details] Xorg.0.log
Okay, I've switched off compiz since the 11th and while it's not happening as regularly, it is still happening, so I think things in compiz help trigger this, but compiz isn't the only thing causing it. What can I do to try and debug this? Can I run some sort of debugging on something? I'm happy to try, if you're happy to tell me what to try and possibly how to try.
Hmmm, I'm going to close this bug as I think it may have been hardware related. I've had two new motherboards in my laptop in the past month. The first replacement made this problem far more common (and my system unusable with any OS i tried - f12, f13 and win7) and the second seems to have resulted in no problems since. At a guess, Dell might have some QA issues with the 1647 motherboards.