On Wed, Oct 13, 2010 at 12:37:42PM +1100, Rodd Clarkson wrote:
> Sorry to email you off list, but I've noticed a number of other small issues
> with this kernel that I'm not sure are worth reporting on as it's an f15
> kernel and I'm using f14.
It's ok, though I'd prefer you just use the fedora-kernel-list for
questions like this. (I added you to the allowed-senders list incase you
didn't want to subscribe.)
> Examples include:
> The trackpad is 'sticky', with the action being jerky, but it's fine with a
> different pointing device (a logitech wireless mouse, for example).
> Sound is glitchy.
> Are these bugs worth filing against this kernel, or should I ignore them?
There's no real meaty patches to either of these in F-14 or rawhide, so
I'm not sure. I'll ask Peter about the input stuff, but I suspect that's
close between F-14 and rawhide as well, so it's probably a legitimate
bug in 2.6.36...
W dniu 12 października 2010 12:39 użytkownik Rodd Clarkson
> 2010/9/28 Michał Piotrowski <mkkp4x4(a)gmail.com>
>> W dniu 27 września 2010 23:13 użytkownik Michał Piotrowski
>> <mkkp4x4(a)gmail.com> napisał:
>> > 2010/9/27 Rodd Clarkson <rodd(a)clarkson.id.au>:
>> >> I've been having troubles getting 2.6.34.x kernels on f13 and 2.6.35.x
>> >> kernels on f14 to resume from suspend.
>> >> https://bugzilla.redhat.com/show_bug.cgi?id=628897
>> >> To try and resolve this I've been trying out other recent distros to
>> >> see if
>> >> they have similar kernels and whether I have the same problem resuming.
>> >> Recent ubuntu is still only using 2.6.32 but openSUSE 11.3 has a 2.6.34
>> >> kernel and I can suspend and resume from it using the live CD. How can
>> >> I
>> >> compare this kernel to ones in f13/f14 to see why it works in one and
>> >> not in
>> >> the other?
>> > You can download source package and check whether there are any
>> > patches that fixes suspend.
>> I grepped the source and I have not found anything obvious.
> 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?
It might be a patch added by one of Fedora kernel developers. CC'ing
> 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.
> test mailing list
> To unsubscribe:
I've been testing out the newly Open Sourced Broadcom driver that's in
the staging-next tree. Seems reliable, aside from suspend/resume (I
posted one patch for handling radio is disabled on init hard crash).
Sure, it'll hopefully land in staging and be in the rawhide kernel in
due course, but given that I'm lazy and bought the netbook in question
specifically to run rawhide(!), would there be huge objections to a
patch sooner that pulled in this driver until it's there officially?
Sure, it's experimental, but it's self-contained and this is rawhide.
Let me know if this would be just a silly/bad idea.
CC'ing kernel list
2010/10/4 Anne & Lynn Wheeler <lynn(a)garlic.com>:
> EXT4 filesystem directory with 100,000+ small files, 4-core intel
> processor, batch process that runs parallel on all four processors
> ... adding/deleting several hundred files.
Let me guess - fsfuzzer? :)
> No problem on F13 but fairly consistently happens since recent
> "preupgrade" to F14. If I serialize the processing, problem
> doesn't occur.
> Initial symptom is that batch process doesn't complete and gkrellm
> shows one of the processors at 100% cpu in the kernel. Eventually
> whole system locks up and requires reboot (with manual reset switch).
> Directory will then frequently show numerous newly added files
> as zero bytes (i.e. metadata had been logged, but actual data
> never written to disk).
> test mailing list
> To unsubscribe: