You are not logged in.
Well as far as I can tell this doesn't happen in 2.6.33-rc3, just had a lockup again on 2.6.32.3 after screen suspended itself, BUG Soft Lockup etc...
What is the general time frame for a new version of the kernel to hit Arch/core? It's around a month, right?
Offline
Yes a month after a final release, but can be sooner, it hits the testing pretty fast though
Offline
On my system with out KMS xorg just gives me a black screen, so if I try 2.6.32 I can either have a black screen right after grub (with i915 in my mkinitcpio modules array) right after udev (without i915 in my mkinitcpio) or at xorg/slim (without kms).
To add further details I am running openbox with cairo-compmgr, but the same thing occurs with XFCE4 (just switched over to openbox).
Cheers
Offline
@combuster is the BUG, soft lockup u got was similar to mine ? I have reported mine here http://bugzilla.kernel.org/show_bug.cgi?id=15015
Just wanted to know if its the same issue.
Thanks
Jithin
Offline
Yes, it's the same issue but without that big crash dump, just getting those CPU Soft Lockups for 61sec lines in a timely fashion (every minute ) until I power off the laptop.
Offline
DELL laptop owners should try this:
open /boot/grub/menu.lst with your editor of choice, as root, and find:
# (0) Arch Linux
title Arch Linux
root (hd0,0)
kernel /vmlinuz26 root=/dev/disk/by-uuid/e9e3ecc2-2c13-4251-9151-84ef7971d78c ro noapic
initrd /kernel26.imgJust add the part in bold, that fixed it for me at least. The non-bold part changes from installation to installation, but it's the first entry after all the comments.
Good luck,
D
I own a Dell XPS m1330 running kernel 2.6.32 and this did not work for me.
heathbar
Offline
Ever since I disabled the do not start screen saver automatically. I have not faced a black screen.
Thanks
Jithin
Offline
Ever since I disabled the do not start screen saver automatically. I have not faced a black screen.
That statement confused me. In the desktop settings under KDE, I have an option that says "start automatically" and it's currently disabled. Did you check or uncheck that box?
Offline
I unchecked the start automatically box.
Thanks
Jithin
Offline
I unchecked the start automatically box.
Thanks. Mine is unchecked by default and I still have the problem.
Offline
Just disable suspend or turning off screen after certain amount of time in power management options.
I can confirm that 2.6.33-rc3/4 doesn't have this bug, so apparently they fixed it, would like to know the exact patch that did it though
Offline
I would like to know that too.
Offline
same here on dell inspiron 1525 intel + kms.
I try to use new intel driver ( 2.10.0) + kernel .33rc4 = same issue!!
Offline
For me the problem seems to have been fixed in the latest kernel update. Did anyone else get the pleasent surprise or was it just a stroke of luck on my part. Or perhaps something else did the trick, not really sure what that would be though.
currently runing 2.6.32.5-1
//Habmala
Offline
For me the problem seems to have been fixed in the latest kernel update. Did anyone else get the pleasent surprise or was it just a stroke of luck on my part. Or perhaps something else did the trick, not really sure what that would be though.
currently runing 2.6.32.5-1
//Habmala
I haven't even had a chance to test it after the update. I am hoping that's what fixed it though.
Offline
Same here. But considering that it appears quite randomly, I would like to wait for a couple of days to see if it's actually fixed.
Thanks
Jithin
Offline
For me it's been sort of blinking when I open the lid, and then it seemd random whether it would end on black or the my desktop .
But it stopped blinking now, so I'm confident. But as you say, giving it a day or two might not be bad.
//Habmala
Offline
Well I just now had another blank screen. First one in days and with kernel 2.6.32-5
I have reported a bug here
http://bugzilla.kernel.org/show_bug.cgi?id=15015
Last edited by jithin1987 (2010-01-26 04:07:18)
Thanks
Jithin
Offline
Oh, sorry to hear that.
It seems to me that (at least for me) the problem has improved, but I guess it's not yet solved then. I'll post back if I too get any more blank screens, 'til then I guess we can all just hope, for future fixes or atleast some realiability. : /
//Habmala
Offline
I am having another issue as of the latest kernel update. For some reason, WICD isn't working well at all. Wireless connects fine, but it used to connect before I logged in, but it doesn't connect until after. In addition (and even stranger) WICD refuses to use my wired connection, though it does sometimes work after I reboot.
Offline
Your issue might not be related to this issue . That sounds more like some configuration issue.
Anyways I don't use WICD, sorry can't be of any help in this regard.
Thanks
Jithin
Offline
Your issue might not be related to this issue . That sounds more like some configuration issue.
Anyways I don't use WICD, sorry can't be of any help in this regard.
You might be right. The configuration hasn't changed though, only the kernel. I don't remember WICD being updated in a while.
Offline
Now that KMS for intel is forced, this problem has reared it's ugly head again for me.
I guess I'll have to try kernel 2.6.33rc8 like on my desktop :-(
Offline
Upgraded to kernel 2.6.32.8-1 and I'm still experiencing the same problem with the new intel 2.10 driver + forced KMS.
Offline
confirmed that the issue is fixed as of 2.6.33-rc8. No more screen flickering and the black screen of death after suspend and such.
Offline