I tried re-compiling the kernel (quite a slow process here on the netbook ;)) and these two warnings seemed relevant:
Building modules, stage 2.
MODPOST 2292 modules
WARNING: drivers/video/vesafb.o(.exit.text+0x57): Section mismatch in reference from the function vesafb_remove() to the (unknown reference) .init.data:(unknown)
The function __exit vesafb_remove() references
a (unknown reference) __initdata (unknown).
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
(unknown) so it may be used outside an init section.
WARNING: drivers/video/vesafb.o(.exit.text+0x62): Section mismatch in reference from the function vesafb_remove() to the variable .init.data:vesafb_fix
The function __exit vesafb_remove() references
a variable __initdata vesafb_fix.
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
vesafb_fix so it may be used outside an init section.
Perhaps my issue should be refiled as a different bug since the hardware is not the i915?
I tried re-compiling the kernel (quite a slow process here on the netbook ;)) and these two warnings seemed relevant:
Building modules, stage 2. video/vesafb. o(.exit. text+0x57) : Section mismatch in reference from the function vesafb_remove() to the (unknown reference) .init.data: (unknown)
MODPOST 2292 modules
WARNING: drivers/
The function __exit vesafb_remove() references
a (unknown reference) __initdata (unknown).
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
(unknown) so it may be used outside an init section.
WARNING: drivers/ video/vesafb. o(.exit. text+0x62) : Section mismatch in reference from the function vesafb_remove() to the variable .init.data: vesafb_ fix
The function __exit vesafb_remove() references
a variable __initdata vesafb_fix.
This is often seen when error handling in the exit function
uses functionality in the init path.
The fix is often to remove the __initdata annotation of
vesafb_fix so it may be used outside an init section.
Perhaps my issue should be refiled as a different bug since the hardware is not the i915?