| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 4 Feb 2010 16:39:40 +1000 From: Dave Airlie <airlied@...il.com> To: Ingo Molnar <mingo@...e.hu> Cc: Dave Airlie <airlied@...ux.ie>, torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org, dri-devel@...ts.sf.net Subject: Re: [crash, PATCH] Revert "drm/radeon/kms: move radeon KMS on/off switch out of staging." >> On Wed, Feb 3, 2010 at 1:46 AM, Ingo Molnar <mingo@...e.hu> wrote: >> > >> > * Dave Airlie <airlied@...il.com> wrote: >> > >> >> On Tue, Feb 2, 2010 at 6:17 PM, Ingo Molnar <mingo@...e.hu> wrote: >> >> > >> >> > * Dave Airlie <airlied@...ux.ie> wrote: >> >> > >> >> >> > Hi Linus, >> >> >> > >> >> >> > Please pull the 'drm-linus' branch from >> >> >> > ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-linus >> >> >> > >> >> >> >> >> >> I've also added an oops fix I seem to lose off my radar to this tree. >> >> >> >> >> >> commit 17aafccab4352b422aa01fa6ebf82daff693a5b3 >> >> >> Author: Michel D??nzer <daenzer@...are.com> >> >> >> Date: ? Fri Jan 22 09:20:00 2010 +0100 >> >> >> >> >> >> ? ? drm/radeon/kms: Fix oops after radeon_cs_parser_init() failure. >> >> > >> >> >> >> Wierd this suggests something else is wrong on that machine can you get me >> >> the whole dmesg? I'm guessing some iommu or swiotlb issue. >> > >> > This box has no known hardware or software problems, just this week it booted >> > in excess of 1000 kernels so i'd exclude that angle for now. >> > >> > I have bisected the crash back to the DRM tree and the crash went away with >> > the Kconfig revert i applied - and it got fixed by Jerome's patch. I posted >> > my config and i posted the relevant boot log as well. Find below the full >> > bootlog as well with vanilla -git (ab65832) and the config. (i dont think it >> > matters) >> > >> >> I've asked Jerome to fix the oops, but really anyone with an old .config >> >> won't get hit by this, and we've booted this on quite a lot of machines at >> >> this point. >> > >> > I dont see the commit in yesterday's linux-next. It has very fresh >> > timestamps: >> > >> > ?commit f71d0187987e691516cd10c2702f002c0e2f0edc >> > ?Author: ? ? Dave Airlie <airlied@...hat.com> >> > ?AuthorDate: Mon Feb 1 11:35:47 2010 +1000 >> > ?Commit: ? ? Dave Airlie <airlied@...hat.com> >> > ?CommitDate: Mon Feb 1 11:35:47 2010 +1000 >> > >> > What kind of widespread testing could this commit have gotten in the less >> > than 24 hours before it hit mainline? >> > >> >> Its shipping in a major distro by default, its planned to be shipped in an >> even more major distro. Its been boot tested on 1000s of machines by 1000s >> of ppl. > > Well but that's not the precise tree you sent to Linus, is it? It pretty much is. If I could blame your crash on any of the recent patches I would but its something new and unfun. Most of the fixes in the Linus tree are directly from fixes to Fedora/Ubuntu bug reports. even after reviewing the dmesg I can't see why its failing on that system, If you could build 2.6.32 on that machine with the staging flag enabled and see if it works it would at least tell us if it is something in recent times or just something thats always been there. Unless some other option in make allyesconfig is conflicting and we've never hit it before. Fedora is close to allyesconfig but not pathalogical like allyesconfig is. Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists