Re: Suspend Issues or Soft Kernel Locks and no wireless; which is worse?

2011-08-10 Thread Greg Woods
On Tue, 2011-08-09 at 23:24 -0400, Eric Griffith wrote:
  KDE Power Management is set that if
 I close my laptop lid, it should go into sleep mode. When I close the
 lid, I give it a few seconds to enter sleep, and then I open it back
 up. I'm met with a black screen

Just to make sure we check the obvious and the stupid first: I also
thought suspend was not working on my laptop, but I now find that if I
press CTRL-ALT-F1 to switch to the main console after opening the lid,
the password prompt screen appears, at which point I can type my
password and the desktop appears.

--Greg


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


Re: Suspend Issues or Soft Kernel Locks and no wireless; which is worse?

2011-08-10 Thread Eric Griffith
On Wed, Aug 10, 2011 at 10:00 AM, Greg Woods wo...@ucar.edu wrote:
 On Tue, 2011-08-09 at 23:24 -0400, Eric Griffith wrote:
  KDE Power Management is set that if
 I close my laptop lid, it should go into sleep mode. When I close the
 lid, I give it a few seconds to enter sleep, and then I open it back
 up. I'm met with a black screen

 Just to make sure we check the obvious and the stupid first: I also
 thought suspend was not working on my laptop, but I now find that if I
 press CTRL-ALT-F1 to switch to the main console after opening the lid,
 the password prompt screen appears, at which point I can type my
 password and the desktop appears.

 --Greg



Yeah that doesn't work haha, I tried it before. Kernel / X is totally
unresponsive to any keyboard / mouse events except for the power
button, which goes straight to the mobo anyway lol. The guys on the
KDE mailing list seemed to think it might be a kernel module for one
of my devices but we we couldn't even figure out where to start since
it could be any one of them, and suspend.log seems to think
everything's fine
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


Suspend Issues or Soft Kernel Locks and no wireless; which is worse?

2011-08-09 Thread Eric Griffith
Alright so basically...suspend's not working right; bomb of information below

Laptop Model: ASUS N73JQ-X2
Kernel: 2.6.40-4.fc15.i686
Desktop Enviro: KDE 4.6.5

The last time Suspend worked with no issues was Linux Mint 10 which
had, I think, kernel 2.6.35 (with ubuntu mods).

Alright, here's what's happening: KDE Power Management is set that if
I close my laptop lid, it should go into sleep mode. When I close the
lid, I give it a few seconds to enter sleep, and then I open it back
up. I'm met with a black screen, with a blinking cursor in the top
left. Fedora (15) is non-responsive to keyboard and mouse events
(SysRQ is enabled and doesn't work, so thats out the window), only
solution is to power it down and power it back up.  Little googling
around and I'm met with a post by an owner of an ASUS N71, one
generation back. With a custom sleep script for ehci-hcd that worked
for them. Figure I'll give it a shot. Throw the script into
/etc/pm/sleep.d/, give it the necessary permissions. Reboot to make
sure it loads it, and then try sleep again.

It works!

...kinda.

Closed the lid, gave it a few seconds. Opened the lid back up, black
screen, and moved the mouse, my desktop appears a second later. I see
that knetworkmanager says I have no network; no problem, sleep always
kills the network interface before bringing it back up. Wait a second
wireless to come backits not coming back. Mouse over
knetworkmanager in the systray: ethernet + wireless = 'unmanaged.'
*blink blink* Bug report pops up! Not for knetworkmanager... CPU #0 is
having soft kernel locks, and a lot of them. More and more bug reports
kept coming in, non stop until I powered down the laptop. Looking at
Fedora's automatic bug reporting, it says CPU#0 locked up for
23seconds, followed by the name of the custom sleep script I just
added. I'm pasting the sleep script below, if anyone is familiar with
suspend / sleep and can look it over, maybe give me a few hints on
what to do

Below is the backtrace for the kernel lockups, I do have more
information related to the lockup, but since Fedora keeps a bug report
inside 20+ different files each detailing 1 and only 1 thing, I'm not
sure which is relevant and which isn't.  Also below is the script, and
pm-suspend.log

Backtrace first:


BUG: soft lockup - CPU#0 stuck for 23s! [20_custom-ehci_:3920]
Modules linked in: ebtable_nat ebtables ipt_MASQUERADE iptable_nat
nf_nat xt_CHECKSUM iptable_mangle bridge sunrpc 8021q garp stp llc
cpufreq_ondemand acpi_cpufreq mperf ip6t_REJECT nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables rfcomm nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack bnep btusb snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device snd_pcm snd_timer snd soundcore arc4 ath9k mac80211
ath9k_common ath9k_hw ath cfg80211 bluetooth snd_page_alloc
asus_laptop sparse_keymap rfkill virtio_net kvm_intel kvm fglrx(P)
iTCO_wdt xhci_hcd iTCO_vendor_support microcode i7core_edac uvcvideo
edac_core videodev joydev atl1c media serio_raw uas usb_storage video
radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded:
scsi_wait_scan]
Modules linked in: ebtable_nat ebtables ipt_MASQUERADE iptable_nat
nf_nat xt_CHECKSUM iptable_mangle bridge sunrpc 8021q garp stp llc
cpufreq_ondemand acpi_cpufreq mperf ip6t_REJECT nf_conntrack_ipv6
nf_defrag_ipv6 ip6table_filter ip6_tables rfcomm nf_conntrack_ipv4
nf_defrag_ipv4 xt_state nf_conntrack bnep btusb snd_hda_codec_hdmi
snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq
snd_seq_device snd_pcm snd_timer snd soundcore arc4 ath9k mac80211
ath9k_common ath9k_hw ath cfg80211 bluetooth snd_page_alloc
asus_laptop sparse_keymap rfkill virtio_net kvm_intel kvm fglrx(P)
iTCO_wdt xhci_hcd iTCO_vendor_support microcode i7core_edac uvcvideo
edac_core videodev joydev atl1c media serio_raw uas usb_storage video
radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded:
scsi_wait_scan]
Pid: 3920, comm: 20_custom-ehci_ Tainted: P
2.6.40-4.fc15.i686 #1 ASUSTeK Computer Inc. N71Jq/N71Jq
EIP: 0060:[c0604a29] EFLAGS: 0203 CPU: 0
EIP is at dma_pte_free_pagetable+0xcf/0x1a0
EAX: 300f EBX: 0004 ECX: 0800 EDX: 0005
ESI: 2810 EDI: f3ada428 EBP: efe49e68 ESP: efe49e38
 DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Process 20_custom-ehci_ (pid: 3920, ti=f400e000 task=f2853280 task.ti=efe48000)
Stack:
 efe49e58 0800 0004 07ff f389c100  f3ada000 
 0004 0024 f389c100 f401f060 efe49e94 c0604fd9  
 f389c10c 0292  f401f000 f389c100 0006 f401f060 efe49ea8
Call Trace:
 [c0604fd9] domain_exit+0xc5/0x18c
 [c0605d79] device_notifier+0x58/0x5f
 [c081748f] notifier_call_chain+0x2b/0x4d
 [c045813e] __blocking_notifier_call_chain+0x40/0x52
 [c045816f] blocking_notifier_call_chain+0x1f/0x21
 [c067fda2] __device_release_driver+0x98/0x9c
 [c067fdc3] device_release_driver+0x1d/0x28
 [c067f2cb]