[ltp] Fedora 11, resume unreliable on X40

Christos Papadopoulos linux-thinkpad@linux-thinkpad.org
Thu, 23 Jul 2009 16:21:33 -0600


Thanks for the pointer, but this did not work for me.  I may have a
different problem, however. In my case the laptop comes back, but with
a very dark display. Sometimes I can see the faint prompt and can type
commands, meaning the OS is alive. The laptop will also suspend and
resume again, but the dark screen persists.

Seems like a problem with the display intensity, or the display not
being turned back on.

Christos.


On Wed, Jul 22, 2009 at 11:21:22AM +0200, Matthias Runge wrote:
> Suspend/resume is a known bug on Fedora 11. This seems to be kernel 
> related.
> Fedora Wiki has a workaround.
> https://fedoraproject.org/wiki/Common_F11_bugs#suspend-oops
> 
> Matthias
> 
> On 30/06/09 22:29, Christos Papadopoulos wrote:
> >I think we now have success.
> >
> >In case anyone is still reading, yet another followup to my own
> >comment.  Disabling hi-res timers by adding highres=off to grub.conf
> >seems to fix the problem. I have gone through several successful
> >suspend/resume cycles, certainly more than any other time before the
> >change. (Thinkpad X40 with Intel graphics card)
> >
> >Christos.
> >
> >On Sat, Jun 27, 2009 at 06:01:39AM -0600, Christos Papadopoulos wrote:
> >>Well, I spoke too soon. While resume works, it is not reliable.
> >>The machine crashes every third time or so coming back from resume.
> >>
> >>The message Fedora wants to report is below.
> >>
> >>Any suggestions anyone?
> >>
> >>Christos.
> >>
> >>
> >>Kernel failure message 1:
> >>------------[ cut here ]------------
> >>WARNING: at kernel/hrtimer.c:625 hres_timers_resume+0x34/0x4a() (Not 
> >>tainted)
> >>Hardware name: 2382RFU
> >>hres_timers_resume() called with IRQs enabled!Modules linked in: 
> >>michael_mic arc4 ecb lib80211_crypt_tkip aes_i586 aes_generic 
> >>lib80211_crypt_ccmp fuse rfcomm bridge stp llc bnep sco l2cap sunrpc 
> >>ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 
> >>cpufreq_ondemand acpi_cpufreq dm_multipath uinput snd_intel8x0 
> >>snd_intel8x0m snd_ac97_codec ac97_bus snd_pcm iTCO_wdt ipw2200 
> >>thinkpad_acpi sdhci_pci iTCO_vendor_support snd_timer yenta_socket sdhci 
> >>snd i2c_i801 libipw rsrc_nonstatic hwmon lib80211 btusb bluetooth e1000 
> >>mmc_core joydev soundcore snd_page_alloc nsc_ircc irda crc_ccitt pcspkr 
> >>ata_generic pata_acpi i915 drm i2c_algo_bit i2c_core video output [last 
> >>unloaded: microcode]
> >>Pid: 3761, comm: pm-suspend Not tainted 2.6.29.5-191.fc11.i586 #1
> >>Call Trace:
> >>[<c042ebc6>] warn_slowpath+0x7c/0xa4
> >>[<c0443042>] ? ktime_get_ts+0x4f/0x53
> >>[<c0414063>] ? lapic_next_event+0x18/0x1c
> >>[<c0448cd3>] ? clockevents_program_event+0xe6/0xf5
> >>[<c0449b5d>] ? tick_dev_program_event+0x47/0xb4
> >>[<c0449c2a>] ? tick_program_event+0x26/0x2e
> >>[<c044917d>] ? tick_notify+0x2e5/0x2f4
> >>[<c0709b07>] ? notifier_call_chain+0x26/0x48
> >>[<c04429a2>] hres_timers_resume+0x34/0x4a
> >>[<c0446d39>] timekeeping_resume+0x130/0x137
> >>[<c05ddad5>] __sysdev_resume+0x19/0x3d
> >>[<c05ddb1f>] sysdev_resume+0x26/0x59
> >>[<c04518c9>] suspend_devices_and_enter+0x112/0x186
> >>[<c0451aa0>] enter_state+0x13c/0x197
> >>[<c0451b94>] state_store+0x99/0xae
> >>[<c0451afb>] ? state_store+0x0/0xae
> >>[<c055a9f5>] kobj_attr_store+0x16/0x22
> >>[<c04de44e>] sysfs_write_file+0xca/0xf5
> >>[<c04de384>] ? sysfs_write_file+0x0/0xf5
> >>[<c04a09a0>] vfs_write+0x95/0xf4
> >>[<c04a0abb>] sys_write+0x4c/0x70
> >>[<c0403f72>] syscall_call+0x7/0xb
> >>---[ end trace 9f6d2b8ff1500853 ]---
> >>
> >>
> >>Kernel failure message 2:
> >>BUG: sleeping function called from invalid context at 
> >>kernel/workqueue.c:440
> >>in_atomic(): 0, irqs_disabled(): 1, pid: 3761, name: pm-suspend
> >>Pid: 3761, comm: pm-suspend Not tainted 2.6.29.5-191.fc11.i586 #1
> >>Call Trace:
> >>
> >>
> >>
> >>On Tue, Jun 23, 2009 at 02:34:30PM -0600, Christos Papadopoulos wrote:
> >>>Following up to my own post: the solution was to disable modesetting in
> >>>the kernel.
> >>>
> >>>In /boot/grub/grub.conf:
> >>>
> >>>kernel /vmlinuz-2.6.29.4-167.fc11.i586 ro root=/dev/VolGroup00/LogVol00 
> >>>rhgb quiet hpet=force nomodeset
> >>>
> >>>BTW, the sd slot works fine on my X40. Looks like F11 might be usable
> >>>for me after all.
> >>>
> >>>Christos.
> >>>
> >>>On Tue, Jun 23, 2009 at 09:07:21AM -0600, Christos Papadopoulos wrote:
> >>>>Well, I should have checked before upgrading to Fedora 11.  Fedora 10
> >>>>worked so well on my X40 that created a false sense of reliability.
> >>>>
> >>>>As it stands now, resume leaves me with a blank screen, and apparently
> >>>>the external VGA and SD slots are not working properly (according to
> >>>>thinkwiki).
> >>>>
> >>>>Before I begin the long process of debugging, does anyone have any
> >>>>pointers? suspend/resume is critical for me.
> >>>>
> >>>>Christos.
> >>>>--
> >>>>The linux-thinkpad mailing list home page is at:
> >>>>http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
> >>>--
> >>>The linux-thinkpad mailing list home page is at:
> >>>http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
> >>--
> >>The linux-thinkpad mailing list home page is at:
> >>http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad
> 
> -- 
> The linux-thinkpad mailing list home page is at:
> http://mailman.linux-thinkpad.org/mailman/listinfo/linux-thinkpad