Re: [Bug #12792] 2.6.29-rc6-git4 boot failure
I narrowed it down to 2.6.28-git2(Boots) while 2.6.28-git4(fails to boot). I could not boot test 2.6.28-git3 as i ran into kernel compilation issues. Here is the error message i got when i tried compiling 2.6.28-git3. LD vmlinux.o ld: dynreloc miscount for kernel/built-in.o, section .opd ld: can not edit opd Bad value I think the above one was some tool chain related issue. I don't know how to git bisect using these two releases (2.6.28-git2/2.6.28-git4). I guess that is not possible since there are no commit tags for these releases. But i could be wrong. Is there anything else that i could try out to find a solution for this ? The machine in question is a Power Mac G5 running Ubuntu Hardy with a PPC970, altivec supported CPU(2). For the record i can still recreate this issue with 2.6.29-rc8-git6. Strange I have such a powermac here and haven't seen that problem... let me dig a bit. Cheers, Ben. -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [alsa-devel] Bugs on aspire one A150
At Sun, 22 Mar 2009 13:55:17 +0100, Andreas Mohr wrote: Hi, On Fri, Mar 20, 2009 at 09:33:19PM +0100, Takashi Iwai wrote: At Fri, 20 Mar 2009 19:56:40 +0100, Andreas Mohr wrote: Hi, On Wed, Mar 18, 2009 at 10:19:53AM +0100, Takashi Iwai wrote: What is the output with -v option? Sorry for the delay! $ arecord -fdat -c1 -v test.wav; aplay test.wav Recording WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono ALSA - PulseAudio PCM I/O Plugin Its setup is: stream : CAPTURE access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 1 rate : 48000 exact rate : 48000 (48000/1) msbits : 16 buffer_size : 24000 period_size : 6000 period_time : 125000 tstamp_mode : NONE period_step : 1 avail_min: 6000 period_event : 0 start_threshold : 1 stop_threshold : 24000 silence_threshold: 0 silence_size : 0 boundary : 1572864000 ^CAborted by signal Interrupt... Playing WAVE 'test.wav' : Signed 16 bit Little Endian, Rate 48000 Hz, Mono a...@andinet:/tmp$ Hmm. Note the pulseaudio stuff above... Yes, that's the very reason. If you don't PA and avoid the default configuration override (e.g. defined in /etc/asound.conf) my patch should work. Sorry, but how would I achieve don't PA? I've tried some Ubuntu suggestions (e.g. http://ubuntuforums.org/showthread.php?t=852518 ; didn't work, it's Jaunty here), I'm no Ubuntu user, so no idea. Takashi -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling
On 10/27/08, Eric Anholt e...@anholt.net wrote: On Mon, 2008-10-27 at 14:27 +, Alan Jenkins wrote: What does this mean, should I do anything about it? Is tiling nice to have? It sounds like GEM broke something - though maybe it just added a more verbose error report. System: EeePC 701 Kernel: v2.6.28-rc1-5-g23cf24c Chipset: Intel mobile 915G-something Regretably necessary kernel boot option: noapic [1.438441] Linux agpgart interface v0.103 [1.438441] agpgart-intel :00:00.0: Intel 915GM Chipset [1.438441] agpgart-intel :00:00.0: detected 7932K stolen memory [1.443353] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xd000 [1.443353] [drm] Initialized drm 1.1.0 20060810 [1.443353] pci :00:02.0: PCI INT A - Link[LNKA] - GSI 5 (level, low) - IRQ 5 [1.443353] pci :00:02.0: setting latency timer to 64 [1.443353] [drm:i915_gem_detect_bit_6_swizzle] *ERROR* Couldn't read from MCHBAR. Disabling tiling. This means that something went wrong with our detection of the CPU-versus-GPU tiling swizzling mode, and object tiling under GEM will be disabled as a result. I should get access to an eee 7xx on Thursday to see what's up with it -- it's supposed to be just a normal 915gm as far as I know. Any news about this tiling error? It's already been reported as a bug in Ubuntu Jaunty, in the belief that it reduces video performance [1], and is also mentioned on a similar bug in Fedora [2]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=444328#c37 [2] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/329266 Thanks Alan -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 2.6.28-rc1: [drm:i915] *ERROR* ... Disabling tiling
On 3/23/09, Alan Jenkins sourcejedi.l...@googlemail.com wrote: On 10/27/08, Eric Anholt e...@anholt.net wrote: On Mon, 2008-10-27 at 14:27 +, Alan Jenkins wrote: What does this mean, should I do anything about it? Is tiling nice to have? It sounds like GEM broke something - though maybe it just added a more verbose error report. System: EeePC 701 Kernel: v2.6.28-rc1-5-g23cf24c Chipset: Intel mobile 915G-something Regretably necessary kernel boot option: noapic [1.438441] Linux agpgart interface v0.103 [1.438441] agpgart-intel :00:00.0: Intel 915GM Chipset [1.438441] agpgart-intel :00:00.0: detected 7932K stolen memory [1.443353] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xd000 [1.443353] [drm] Initialized drm 1.1.0 20060810 [1.443353] pci :00:02.0: PCI INT A - Link[LNKA] - GSI 5 (level, low) - IRQ 5 [1.443353] pci :00:02.0: setting latency timer to 64 [1.443353] [drm:i915_gem_detect_bit_6_swizzle] *ERROR* Couldn't read from MCHBAR. Disabling tiling. This means that something went wrong with our detection of the CPU-versus-GPU tiling swizzling mode, and object tiling under GEM will be disabled as a result. I should get access to an eee 7xx on Thursday to see what's up with it -- it's supposed to be just a normal 915gm as far as I know. Any news about this tiling error? It's already been reported as a bug in Ubuntu Jaunty, in the belief that it reduces video performance [1], and is also mentioned on a similar bug in Fedora [2]. [1] https://bugzilla.redhat.com/show_bug.cgi?id=444328#c37 [2] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/329266 Ah, I should also mention that I still see the error on the latest RC, 2.6.29-rc8. Alan -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Bug #12872] pwc mmap always fails with EAGAIN
Rename the pagerange_is_ram() to pat_pagerange_is_ram() and add the track legacy 1MB region as non RAM condition. But the lowest 640K are most definitely RAM. -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Bug #12872] pwc mmap always fails with EAGAIN
On Mon, 23 Mar 2009 10:49:45 + Alan Cox a...@lxorguk.ukuu.org.uk wrote: Rename the pagerange_is_ram() to pat_pagerange_is_ram() and add the track legacy 1MB region as non RAM condition. But the lowest 640K are most definitely RAM. not all of it ;) ram is defined as the kernel memory allocator knows about it and would hand it out in this context; BIOS owned areas are not ram in this context. -- Arjan van de VenIntel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: 2.6.29-rc8-git5: Reported regressions from 2.6.28
On Mon, 23 Mar 2009, Wu Fengguang wrote: I think this was tracked back to the effective halving of dirty_ratio by 1cf6e7d83 (mm: task dirty accounting fix) and doubling the ratio fixed the iozone regression. Yes, exactly. The patch for fixing this regression is trivial. I was planning on applying that patch only after 2.6.29 is out, and then if there are no surprising side effects and nobody complains, we'd then back-port it into stable. Linus -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [Bug #12818] iwlagn broken after suspend to RAM (iwlagn: MAC is in deep sleep!)
Rafael J. Wysocki wrote: This message has been generated automatically as a part of a report of regressions introduced between 2.6.27 and 2.6.28. The following bug entry is on the current list of known regressions introduced between 2.6.27 and 2.6.28. Please verify if it still should be listed and let me know (either way). It still does not work with 2.6.29-rc8. Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12818 Subject : iwlagn broken after suspend to RAM (iwlagn: MAC is in deep sleep!) Submitter : Stefan Seyfried se...@suse.de Date : 2009-03-04 08:32 (18 days old) -- Stefan Seyfried RD Team Mobile Devices| Any ideas, John? SUSE LINUX Products GmbH, Nürnberg | Well, surrounding them's out. This footer brought to you by insane German lawmakers: SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line unsubscribe kernel-testers in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
