On Wed, Oct 13, 2010 at 6:46 AM, Adam Williamson <awilliam@xxxxxxxxxx> wrote:
I'm pretty confident that I've tried every f13 kernel that's been through koji. If I haven't, I've come close.
I've also tried all the 'released' f14 kernels along with a couple of others (I'm still to try the two kernel suggestions above, I'm downloading Kyle's now and will rebuild the kernel if needed).
Early in F13's move to 2.6.34 there was another bug that caused issues with suspending the system. This was resolved, which revealed problems with resuming from a suspend (which seems to have worked properly).
So, it's hard to tell if this bug was in the first 2.6.34 kernel for f13 or not.
I'm aware of this which is why I'm trying to supply as much information as possible to the kernel developers to try and rectify this problem I have. It may be that isn't not actually the kernel, but some other related part of the software stack, but I wouldn't know where to start looking.
R.
On Tue, 2010-10-12 at 21:39 +1100, Rodd Clarkson wrote:One more triaging step I'd recommend is to try an upstream kernel of the
> I've downloaded the Ubuntu 10.10 LiveCD which uses kernel 2.6.35 and
> suspend and resume works fine in Ubuntu too.
>
> What difference in the Fedora kernels could be causing this problem?
same vintage. If that works, you know that some change Fedora adds is
breaking it. If it doesn't work, you know that Ubuntu and SUSE both have
a patch that Fedora doesn't which fixes it.
(I suspect this may come down to graphics code; Fedora generally carries
rather newer upstream versions of intel, nouveau and radeon than other
distros, and these can introduce regressions).
I'm pretty confident that I've tried every f13 kernel that's been through koji. If I haven't, I've come close.
I've also tried all the 'released' f14 kernels along with a couple of others (I'm still to try the two kernel suggestions above, I'm downloading Kyle's now and will rebuild the kernel if needed).
Early in F13's move to 2.6.34 there was another bug that caused issues with suspending the system. This was resolved, which revealed problems with resuming from a suspend (which seems to have worked properly).
So, it's hard to tell if this bug was in the first 2.6.34 kernel for f13 or not.
It's not strange, suspend/resume is critical to most laptop users. It's
> I know it seems strange to some, but suspend and resume are one of the
> most important features for me on my laptop. I can (and have) put up
> with (a lot) less than optimal video, no sound and even wireless
> network issues, but without a functioning suspend and resume it's
> quite arduous having to wait for a system to shutdown and reboot.
> Each to their own I guess, but I'd really like this to work and it
> appears that it does work on other distros which makes me wonder what
> Fedora isn't doing right.
just pretty hard to diagnose and fix.
I'm aware of this which is why I'm trying to supply as much information as possible to the kernel developers to try and rectify this problem I have. It may be that isn't not actually the kernel, but some other related part of the software stack, but I wouldn't know where to start looking.
R.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
