On Tuesday 17 November 2009, Justin P. Mattock wrote: > Rafael J. Wysocki 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.31. Please verify if it still should be listed and let me know > > (either way). > > > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14487 > > Subject : PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0 > > Submitter : Justin P. Mattock<justinmattock@xxxxxxxxx> > > Date : 2009-10-23 16:45 (25 days old) > > References : http://lkml.org/lkml/2009/10/23/252 > > > > > > > > > This one has me a bit dazed i.g. after looking into the issue > I did find a workaround(keep in mind it's not pretty), > by commenting out set_fixmap_nocache and > init_ohci1394_reset_and_init_dma. > (by doing so I was able to load both machines and > execute early debugging in case a problem occurs). > > Now as to what might be happening, after going through as > much as I can comprehend the only thing in mind was > reading fixmap.h the comments are stating that vsyscalls > only covers 32bit, and that there needs to be another set > for 64, leading me to believe that this is what I might be hitting. > (my system is pure64, taking in no 32bit at all). > > At this point I think I need somebody to give me some info on this, > and if the 64bit issue mentioned above is the case, then we can probably > close this and leave it up to the x86_64 builders to create a 64bit > call for this whenever they get to it.(main thing is I'm able to > run dma early in case of an emergency). Thanks for the update. 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
