Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-27 Thread Andreas Franck
Hello Mike, hello Linus, Some minutes ago, I wrote: > I think I have found the reason for our bugs. It seems GCC really > miscompiles buffer.c:bdflush_init without frame pointers. I'll try harder > now to understand what excactly is going on, but it seems it is smashing > its local stack space by

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-25 Thread Paul Laufer
On Mon, Dec 25, 2000 at 08:40:50PM + or thereabouts, Thorsten Kranzkowski wrote: > On Mon, Dec 25, 2000 at 06:09:35AM +0100, Mike Galbraith wrote: > > I wouldn't (not going to here;) spend a lot of time on it. The compiler > > has problems. It won't build glibc-2.2, and chokes horribly on ip

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-25 Thread Thorsten Kranzkowski
On Mon, Dec 25, 2000 at 06:09:35AM +0100, Mike Galbraith wrote: > I wouldn't (not going to here;) spend a lot of time on it. The compiler > has problems. It won't build glibc-2.2, and chokes horribly on ipchains. > > int ipt_register_table(struct ipt_table *table) > { > int ret; > s

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-25 Thread Mike Galbraith
On Mon, 25 Dec 2000, Andreas Franck wrote: > Hello Mike, hello linux-kernel hackers, > > Mike Galbraith wrote: > > I wouldn't (not going to here;) spend a lot of time on it. The compiler > > has problems. It won't build glibc-2.2, and chokes horribly on ipchains. > > Maybe, but you were lucky

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-25 Thread Mike Galbraith
On Mon, 25 Dec 2000, Andreas Franck wrote: > Hello Mike, hello linux-kernel hackers, > > Mike Galbraith wrote: > > I wouldn't (not going to here;) spend a lot of time on it. The compiler > > has problems. It won't build glibc-2.2, and chokes horribly on ipchains. > > Maybe, but after having s

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-25 Thread Andreas Franck
Hello Mike, hello linux-kernel hackers, Mike Galbraith wrote: > I wouldn't (not going to here;) spend a lot of time on it. The compiler > has problems. It won't build glibc-2.2, and chokes horribly on ipchains. Maybe, but after having spent several hours debugging now, I think it was worth it

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-25 Thread Andreas Franck
Hello Mike, hello linux-kernel hackers, Mike Galbraith wrote: > I wouldn't (not going to here;) spend a lot of time on it. The compiler > has problems. It won't build glibc-2.2, and chokes horribly on ipchains. Maybe, but you were lucky getting an ICE, and not silently failing code :-) After

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-24 Thread Mike Galbraith
On Sun, 24 Dec 2000, Andreas Franck wrote: > Hello Mike, hello linux-kernel hackers, > > Mike Galbraith wrote: > > > Yes, hmm indeed. Try these two things. > > > > 1. make DECLARE_MUTEX_LOCKED(sem) in bdflush_init() static. > > 2. compile with frame pointers. (normal case for IKD) > > > > M

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-24 Thread Andreas Franck
Hello Mike, hello linux-kernel hackers, Mike Galbraith wrote: > Yes, hmm indeed. Try these two things. > > 1. make DECLARE_MUTEX_LOCKED(sem) in bdflush_init() static. > 2. compile with frame pointers. (normal case for IKD) > > My IKD tree works with either option, but not with neither. I ha

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-24 Thread Mike Galbraith
On Sat, 23 Dec 2000, Andreas Franck wrote: > Hi Mike, hello linux-kernel audience, > > > I had the same, with the last few snapshots I tried, but 20001218 seems > > to work ok. > > dmesg|head -1 > > Linux version 2.4.0-test13ikd (root@el-kaboom) (gcc version gcc-2.97 > > 20001218 (experimental))

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-23 Thread Andreas Franck
The story continues, citing myself: > Hmm, would have been nice, but it crashes here with 20001222, nevertheless. > For which CPU do you have your kernel configured? It might be a CPU > specific issue, I'll try to compile for Pentium I and 486, now, and report > my results. It does not seem CP

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-23 Thread Andreas Franck
Hi Mike, hello linux-kernel audience, > I had the same, with the last few snapshots I tried, but 20001218 seems > to work ok. > dmesg|head -1 > Linux version 2.4.0-test13ikd (root@el-kaboom) (gcc version gcc-2.97 > 20001218 (experimental)) #18 Sat Dec 23 17:43:29 CET 2000 Hmm, would have been ni

Re: Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-23 Thread Mike Galbraith
On Sat, 23 Dec 2000, Andreas Franck wrote: > Hello, > > I hope I am not doing something particularly stupid here, but as Linus > encouraged curious people to try compiling the kernel with the > latest gcc snapshots, I have tried - as several weeks before, but again > in vain. > > Since I have t

Fatal Oops on boot with 2.4.0testX and recent GCC snapshots

2000-12-23 Thread Andreas Franck
Hello, I hope I am not doing something particularly stupid here, but as Linus encouraged curious people to try compiling the kernel with the latest gcc snapshots, I have tried - as several weeks before, but again in vain. Since I have tried, the same following error on early boot (just after "St