Skip to contentSkip to conversation

BUG in free_block (tainted)

DISCUSSION Simon Arlott 5 participants 8 messages Aug 18, 2008 – Aug 22, 2008

lore
Share & tools
lore
#1 lore raw

Hi Simon,

Quoted 5 lines · Simon Arlott

http://img169.imageshack.us/img169/1170/1005548cp9.jpg

2.6.27-rc3 09873-gb08c7f5

(Tainted with fglrx, but X hadn't been run...)

Looks like SLAB corruption so fglrx could have caused this even if you just loaded the module. Do you have CONFIG_DEBUG_SLAB enabled? If not, you might want to try to reproduce this with it. Of course, reproducing the oops without fglrx would be most helpful. :-)

Pekka

#2 lore raw
Quoted 5 lines · Pekka Enberg

Hi Simon,

Quoted 2 lines · Simon Arlott

http://img169.imageshack.us/img169/1170/1005548cp9.jpg

Quoted 8 lines
Quoted 3 lines

2.6.27-rc3 09873-gb08c7f5

(Tainted with fglrx, but X hadn't been run...)

Looks like SLAB corruption so fglrx could have caused this even if you just loaded the module. Do you have CONFIG_DEBUG_SLAB enabled? If not, you might want to try to reproduce this with it. Of course, reproducing the oops without fglrx would be most helpful. :-)

In that case please disregard this completely. It's not yet happened again.

fglrx completely breaks slab in fantastic ways... I could show you my /proc/slabinfo... the start of it is badly corrupted - but only if X has been started (attached).

I might try enabling CONFIG_DEBUG_SLAB, perhaps it can detect that bug...

Signature · 1 line
Simon Arlott
#3 lore raw

Hi Simon,

Quoted 5 lines · Simon Arlott
Quoted 5 lines
Quoted 5 lines

http://img169.imageshack.us/img169/1170/1005548cp9.jpg

2.6.27-rc3 09873-gb08c7f5

(Tainted with fglrx, but X hadn't been run...)

Quoted 4 lines · Pekka Enberg
Quoted 4 lines

Looks like SLAB corruption so fglrx could have caused this even if you just loaded the module. Do you have CONFIG_DEBUG_SLAB enabled? If not, you might want to try to reproduce this with it. Of course, reproducing the oops without fglrx would be most helpful. :-)

Quoted 7 lines · Simon Arlott

In that case please disregard this completely. It's not yet happened again.

fglrx completely breaks slab in fantastic ways... I could show you my /proc/slabinfo... the start of it is badly corrupted - but only if X has been started (attached).

I might try enabling CONFIG_DEBUG_SLAB, perhaps it can detect that bug...

Aww, apparently the fglrx driver creates tons of SLAB caches with really funky names for no good reason... Oh well, one more reason to stay away from that crap and help out the nouveau folks instead ;-).

Pekka

#4 lore raw

Pekka Enberg wrote:
perhaps it can detect that bug...

Quoted 4 lines

Aww, apparently the fglrx driver creates tons of SLAB caches with really funky names for no good reason... Oh well, one more reason to stay away from that crap and help out the nouveau folks instead ;-).

Could you give SLUB a try? Diagnostics are better. Lets see what it spits out.

#5 lore raw
In reply to Pekka Enberg
Quoted 3 lines · Pekka Enberg

Aww, apparently the fglrx driver creates tons of SLAB caches with really funky names for no good reason... Oh well, one more reason to stay away from that crap and help out the nouveau folks instead ;-).

fglrx is the AMD/ATI binary evilness - the open source efforts are the radeon and radeonhd drivers. AMD/ATI are actually providing documentation and paying developers to work on the drivers.

I'm not sure what the nvidia binary wonkyness is called, but its respective open source effort is the nouveau - who must solely reply on reverse engineering as nvidia isn't providing anything.

Anyway - your point still stands - binary stuff should not be used.

#6 lore raw

Hi Peter,

Quoted 3 lines · Pekka Enberg
Quoted 3 lines

Aww, apparently the fglrx driver creates tons of SLAB caches with really funky names for no good reason... Oh well, one more reason to stay away from that crap and help out the nouveau folks instead ;-).

Quoted 3 lines · Peter Zijlstra

fglrx is the AMD/ATI binary evilness - the open source efforts are the radeon and radeonhd drivers. AMD/ATI are actually providing documentation and paying developers to work on the drivers.

Oh, right. I guess I didn't even consider anyone would still be using the binary-only ATI crap now that we have proper open source drivers available.... ;-)

Pekka

#7 lore raw
Quoted 4 lines · Pekka Enberg

Oh, right. I guess I didn't even consider anyone would still be using the binary-only ATI crap now that we have proper open source drivers available.... ;-)

I never tried fglrx, but judging from my experiences with the onboard 690G on the board I bought at the beginning of this year (with the two open source X11 drivers for it) the word "proper" is not appropriate when you want a working system.

And I'm not talking about stuff like Xv or even 3D - all I'm asking for is that DVI works flawlessly (and without sporadic GPU lookups).

Note that this is not meant against the developers of the open source drivers - that's simply one of the many areas where recent hardware does not work flawlessly under Linux and developing drivers that work flawlessly takes some time.

Quoted 1 line

Pekka

cu
Adrian

Signature · 4 lines
       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed