Hi!
I think that documentation should stress more strongly that GNU 3.0.*
series of compilers can not be used for building of the production
kernels.
I have got kernel panic in init ....
This is not a complaint, just an information.
--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <[email protected]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ http://www.mysql.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Mon, 26 Nov 2001, Sinisa Milivojevic wrote:
>
> Hi!
>
> I think that documentation should stress more strongly that GNU 3.0.*
> series of compilers can not be used for building of the production
> kernels.
>
> I have got kernel panic in init ....
>
> This is not a complaint, just an information.
>
I've been using 2.4.15+Al Viro's iput() patch+freeswan 1.92 compiled with
gcc 3.0.2, no panics or unexpected behavior. 2.4.14 was up for about 2
weeks also compile with 3.0.2 no panics or crashes.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iEYEARECAAYFAjwCi6sACgkQwtU6L/A4vVAUqACfRNju4fw3b4Mk4K9FIozo43+M
738AnApAel1b6OEXJ4jlExk/YC+8CMi3
=keuA
-----END PGP SIGNATURE-----
Jens Axboe writes:
> On Mon, Nov 26 2001, Sinisa Milivojevic wrote:
>
> YMMV, I've used it quite successfully for testing. Again, the tool set
> necessary to build kernels is quite adequately documented in Changes.
>
> --
> Jens Axboe
>
it could be due to 8139... sources !!
May be you do not have an Ethernet or have not configured kernel for
it ??
I can try with 2.4.16 and report the exact kernel panic if you want
me to ...
--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <[email protected]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ http://www.mysql.com
On Mon, 26 Nov 2001, Sinisa Milivojevic wrote:
> it could be due to 8139... sources !!
>
> May be you do not have an Ethernet or have not configured kernel for
> it ??
>
> I can try with 2.4.16 and report the exact kernel panic if you want
> me to ...
Linux version 2.4.16 ([email protected]) (gcc version 3.0.2) #3 Mon Nov 26
11:07:33 EST 2001
8139TOO compiled directly into the kernel. No problems to report.
--
Ken Witherow <phantoml AT rochester.rr.com> ICQ: 21840670
Linux 2.4.16 - because I'd like to get there today
to remain free, we must remain free of intrusive government
That really depends on what sort of system you are running it on.
Out of five computers I build kernels for at home here, one of them has
an AMD K6II processor in it and that is the only one that I need to use
gcc 2.95.3 with. The rest I use 3.0.x and they are quite stable. I
just did a round of updates to 2.5.1p, but their prior uptimes were
between 30 and 80 days.
I'm not saying 3.0.2 is perfect, for sure it isn't. I'm saying that in
some situations it can certainly be used.
Every compiler has issues, for some projects I have to use 3.0.2, some I
have to use 2.95.3. You keep notes on what works best and go with it.
David
Sinisa Milivojevic wrote:
>Hi!
>
>I think that documentation should stress more strongly that GNU 3.0.*
>series of compilers can not be used for building of the production
>kernels.
>
>I have got kernel panic in init ....
>
>This is not a complaint, just an information.
>
>
David Ford writes:
> That really depends on what sort of system you are running it on.
>
> Out of five computers I build kernels for at home here, one of them has
> an AMD K6II processor in it and that is the only one that I need to use
> gcc 2.95.3 with. The rest I use 3.0.x and they are quite stable. I
> just did a round of updates to 2.5.1p, but their prior uptimes were
> between 30 and 80 days.
>
> I'm not saying 3.0.2 is perfect, for sure it isn't. I'm saying that in
> some situations it can certainly be used.
>
> Every compiler has issues, for some projects I have to use 3.0.2, some I
> have to use 2.95.3. You keep notes on what works best and go with it.
>
> David
>
I have PIII.
But I also have Ethernet, which seems to be causing problems in
2.4.15.
I will try 2.4.16 this weekend.
--
Regards,
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Sinisa Milivojevic <[email protected]>
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Fulltime Developer
/_/ /_/\_, /___/\___\_\___/ Larnaca, Cyprus
<___/ http://www.mysql.com
On Tue Nov 27 2001, Sinisa Milivojevic wrote:
> > Out of five computers I build kernels for at home here, one of them has
> > an AMD K6II processor in it and that is the only one that I need to use
> > gcc 2.95.3 with. The rest I use 3.0.x and they are quite stable.
I have also two machines using AMD's K6
elfie:~ # cat /proc/cpuinfo
processor : 0
vendor_id : AuthenticAMD
cpu family : 5
model : 9
model name : AMD-K6(tm) 3D+ Processor
stepping : 1
cpu MHz : 400.914
cache size : 256 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr mce cx8 pge mmx syscall 3dnow k6_mtrr
bogomips : 799.53
On one of them I compiled the kernel with
elfie:~ # gcc -v
Reading specs from /usr/local/gcc3/lib/gcc-lib/i586-pc-linux-gnu/3.1/specs
Configured with: /Src/gcc-20011203/configure --prefix=/usr/local/gcc3
Thread model: single
gcc version 3.1 20011203 (experimental)
and there were no problems yet (5 days up).
--
# Heinz Diehl, 68259 Mannheim, Germany