Bug#295750: cannot compile kernel when 2.6.10 is installed

2005-02-17 Thread Florian Effenberger
Package: gcc
Version: 3.3.5-1
I'm not quite sure where to file that, but I guess gcc could be the 
right package.

When I have installed the standard 2.6.8-2-686 kernel, I can compile and 
install a vanilla 2.6.10 kernel without problems. However, when I boot 
this kernel and try to compile a 2.6.10 again, I get dozens of internal 
memory allocation errors (error message translated by myself). When I 
switch back to 2.6.8, it works fine again.

The 2.6.10 kernel has the same configuration as the 2.6.8 supplied by 
Debian has.

What log files should I attach?

--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]


Bug#295750: cannot compile kernel when 2.6.10 is installed

2005-02-17 Thread Falk Hueffner
tags 295750 + unreproducible
thanks

Florian Effenberger [EMAIL PROTECTED] writes:

 I'm not quite sure where to file that, but I guess gcc could be the
 right package.

 When I have installed the standard 2.6.8-2-686 kernel, I can compile
 and install a vanilla 2.6.10 kernel without problems. However, when I
 boot this kernel and try to compile a 2.6.10 again, I get dozens of
 internal memory allocation errors (error message translated by
 myself). When I switch back to 2.6.8, it works fine again.

 The 2.6.10 kernel has the same configuration as the 2.6.8 supplied by
 Debian has.

 What log files should I attach?

Log files are of little help as long as we cannot reproduce the
problem. Most likely, this is a hardware problem, since certainly
hundreds of people have by now tried this combination. I don't think
we can do anything about it.

-- 
Falk


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#295750: cannot compile kernel when 2.6.10 is installed

2005-02-17 Thread Florian Effenberger
Okay, will check that out!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]