Mesa 8.0.4 glGetIntegerv produced GL_INVALID_ENUM on certain pname's

While testing against Mesa (Soft + Intel) 8.0.4, GL 3.0 context,
I see the following error codes when querying states via glGetIntegerv
as made visible via MESA_DEBUG=true:

Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_COLOR_ATTACHMENTS)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_SAMPLES)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_PIXEL_PACK_BUFFER_BINDING)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_PIXEL_UNPACK_BUFFER_BINDING)

Ofc .. context is current.

Funny thing is, these errors don't appear w/ the Mesa ES2 'backend'.

Does anybody know about those ?

~Sven

I used Mesa only with Gallium3D under Debian Squeeze and I had no such problems with TUER.