On Wednesday 04 February 2009, Justin Mattock wrote: > On Wed, Feb 4, 2009 at 4:46 PM, Ingo Molnar <mingo@xxxxxxx> wrote: > > > > * Justin Mattock <justinmattock@xxxxxxxxx> wrote: > > > >> On Wed, Feb 4, 2009 at 2:24 AM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > >> > This message has been generated automatically as a part of a report > >> > of recent regressions. > >> > > >> > The following bug entry is on the current list of known regressions > >> > from 2.6.28. Please verify if it still should be listed and let me know > >> > (either way). > >> > > >> > > >> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=12505 > >> > Subject : 2.6.29-rc1 Firefox crashing on page load > >> > Submitter : Justin Madru <jdm64@xxxxxxxxx> > >> > Date : 2009-01-16 20:56 (20 days old) > >> > First-Bad-Commit: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=4217458dafaa57d8e26a46f5d05ab8c53cf64191 > >> > References : http://marc.info/?l=linux-kernel&m=123213941914274&w=4 > >> > Handled-By : Justin P. Mattock <justinmattock@xxxxxxxxx> > >> > > >> > > >> > > >> > >> Well the hardest for this, was to reproduce > >> the error.(never did). I guess it can be taken > >> of if there was a patch for the fix, and the patch > >> made it into the main tree. but if this is a firefox > >> issue, then a report needs to be filed with them. > >> so overall my answer is "I don't know." > >> :^) > > > > the error is spurious because gcc randomly stomps on user register state so > > the effects can be rather random and unpredictable. > > > > The fix: > > > > 552b8aa: Revert "x86: signal: change type of paramter for sys_rt_sigreturn()" > > > > was included in -rc2 already, so please test latest -git whether you can see > > any such troubles. > > > > Ingo > > > > Sure I'll test it. > I'm just in the process of compiling libc. > which looks like I'll be here for a while. I've closed the bug as hopefully fixed. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
