Are you 100% sure you compiled it with CONFIG_NO_BOOTMEM enabled?
I did not test 2.6.35 yet but I did not see anything related to this bug
commited since the discussion so I am very surprised the problem disappeared by
itself...
Will be on vacation very soon, so not sure I will have time to test 2.6.35
before leaving.
Damien
--