From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philip Blundell To: Manfred Hollstein Cc: law@cygnus.com, rms@gnu.org, Manfred.Hollstein@ks.sel.alcatel.de, oliva@dcc.unicamp.br, gcc2@cygnus.com, egcs@cygnus.com Subject: Re: New problems with gcc-2.8.0 based code - NOW FIXED! Date: Tue, 30 Dec 1997 11:33:00 -0000 Message-id: References: <199712301444.PAA00543@saturn.s-direktnet.de> X-SW-Source: 1997-12/msg01247.html > Dec 30 13:58:50 saturn kernel: Call Trace: [] [] [14c>] [] Can you run this through the ksymoops decoder to get a meaningful backtrace (with function names)? >And so on - a lot of kernel Oops's follow. I really don't know, who's >to blame?!?! Looking at Linux's `mm/slab.c' where the `kmem_free:..." >messages result from, doesn't really help, as there is _NO_ loop! BUT, More likely it's the function that calls the SLAB code that is to blame. If you find out what that is and compile it with -S -funroll-all-loops, that might be the way forward. >Does anybody know an e-mail address whom we can forward these >questions? linux-kernel@vger.rutgers.edu is probably your best bet. p.