o.k. finally finished with the bisect: reverting this gets things going on 2.6.33-rc5
789d03f584484af85dbdc64935270c8e45f36ef7 is the first bad commit commit 789d03f584484af85dbdc64935270c8e45f36ef7 Author: Jan Beulich <[email protected]> Date: Tue Jun 30 11:52:23 2009 +0100 x86: Fix fixmap ordering The merge of the 32- and 64-bit fixmap headers made a latent bug on x86-64 a real one: with the right config settings it is possible for FIX_OHCI1394_BASE to overlap the FIX_BTMAP_* range. Signed-off-by: Jan Beulich <[email protected]> Cc: <[email protected]> # for 2.6.30.x LKML-Reference: <[email protected]> Signed-off-by: Ingo Molnar <[email protected]> The only thing I can think of at this point is maybe the CFLAGS I used to build this system. (as for the x86_32 working and x86_64 failing not sure); I'm curious to see if anybody else is hitting this? Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe kernel-testers" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
