Re: Linux 2.4.3-ac12

2001-04-23 Thread Byeong-ryeol Kim 

On Mon, 23 Apr 2001, Byeong-ryeol Kim wrote:

> On Sun, 22 Apr 2001, Alan Cox wrote:
>
> > > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > > symbol rwsem_up_write_wake
> > > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > > symbol rwsem_down_write_failed
> > >
> > > Same thing with tdfx.o...
> >
> > "Works for me" as ever. What configuration options are you using. This sounds
> > like some of the code is built with each kind of semaphore.
> 
>
> I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
> rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
> 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
> are the same.
> I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
> which seemed to be applied in gcc-2.95.4 CVS tree).


I retried to compile 2.4.3-ac12 with Red Hat's 2.96-81(that of 7.1) without
the patch previously applied.
This time, I noticed strange thing.(I guess, it would not be a compiler
problem).
While doing 'depmod -ae -F /boot/System.map-2.4.3-ac12 2.4.3-ac12'
there was no error as far as rwsem_* is concerned, but when doing simply
'depmod -ae', the result was the same as before.( the same kernel
configuration, modutils is original 2.4.5-1 fetched from kernel site).

1) 'depmod -ae -F /boot/system.map-2.4.3-ac12 2.4.3-ac12'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size

2) 'depmod -ae'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size


>
> #
> # Automatically generated make config: don't edit
> #
> CONFIG_X86=y
> CONFIG_ISA=y
> # CONFIG_SBUS is not set
> CONFIG_UID16=y
>
> #
> # Code maturity level options
> #
> CONFIG_EXPERIMENTAL=y
>
> #
> # Loadable module support
> #
> CONFIG_MODULES=y
> CONFIG_MODVERSIONS=y
> CONFIG_KMOD=y
>
> #
> # Processor type and features
> #
> # CONFIG_M386 is not set
> # CONFIG_M486 is not set
> # CONFIG_M586 is not set
> # CONFIG_M586TSC is not set
> # CONFIG_M586MMX is not set
> # CONFIG_M686 is not set
> # CONFIG_MPENTIUMIII is not set
> # CONFIG_MPENTIUM4 is not set
> CONFIG_MK6=y
> # CONFIG_MK7 is not set
> # CONFIG_MCRUSOE is not set
> # CONFIG_MWINCHIPC6 is not set
> # CONFIG_MWINCHIP2 is not set
> # CONFIG_MWINCHIP3D is not set
> # CONFIG_MCYRIXIII is not set
> CONFIG_X86_WP_WORKS_OK=y
>

Re: Linux 2.4.3-ac12

2001-04-23 Thread Byeong-ryeol Kim 

On Sun, 22 Apr 2001, Alan Cox wrote:

> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> >
> > Same thing with tdfx.o...
>
> "Works for me" as ever. What configuration options are you using. This sounds
> like some of the code is built with each kind of semaphore.


I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
are the same.
I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
which seemed to be applied in gcc-2.95.4 CVS tree).
BTW, I applied the follwing patch posted to this list:

--- 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:03 2001
+++ 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:43 2001
@@ -0,0 +1,13 @@
+#ifndef __I386_COMPILER_H
+#define __I386_COMPILER_H 1
+
+/* Somewhere in the middle of the GCC 2.96 development cycle, we implemented
+   a mechanism by which the user can annotate likely branch directions and
+   expect the blocks to be reordered appropriately.  Define __builtin_expect
+   to nothing for earlier compilers.  */
+
+#if __GNUC__ == 2 && __GNUC_MINOR__ < 96
+#define __builtin_expect(x, expected_value) (x)
+#endif
+
+#endif /* __I386_COMPILER_H */


--- 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:38 2001
+++ 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:57 2001
@@ -38,6 +38,7 @@

 #include 
 #include 
+#include 
 #include 
 #include 



depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size


#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_CMPXCHG=y

Re: Linux 2.4.3-ac12

2001-04-23 Thread Geert Uytterhoeven 

On 22 Apr 2001, Jes Sorensen wrote:
> > "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
> Alan> The recommended compilers for non x86 are different too - eg you
> Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
> Alan> on.
> 
> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.

Late 2.3.x proved to be very unstable for user applications (daily cron always
segfaulted somewhere), until I upgraded from 2.7.2.3 to 2.95.2 from Debian.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-23 Thread Geert Uytterhoeven 

On 22 Apr 2001, Jes Sorensen wrote:
  Alan == Alan Cox [EMAIL PROTECTED] writes:
 Alan The recommended compilers for non x86 are different too - eg you
 Alan need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
 Alan on.
 
 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

Late 2.3.x proved to be very unstable for user applications (daily cron always
segfaulted somewhere), until I upgraded from 2.7.2.3 to 2.95.2 from Debian.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds

-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-23 Thread Byeong-ryeol Kim 

On Sun, 22 Apr 2001, Alan Cox wrote:

   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
 
  Same thing with tdfx.o...

 Works for me as ever. What configuration options are you using. This sounds
 like some of the code is built with each kind of semaphore.


I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
are the same.
I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
which seemed to be applied in gcc-2.95.4 CVS tree).
BTW, I applied the follwing patch posted to this list:

--- 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:03 2001
+++ 2.4.3-ac12/include/asm-i386/compiler.h  Sat Apr 21 22:56:43 2001
@@ -0,0 +1,13 @@
+#ifndef __I386_COMPILER_H
+#define __I386_COMPILER_H 1
+
+/* Somewhere in the middle of the GCC 2.96 development cycle, we implemented
+   a mechanism by which the user can annotate likely branch directions and
+   expect the blocks to be reordered appropriately.  Define __builtin_expect
+   to nothing for earlier compilers.  */
+
+#if __GNUC__ == 2  __GNUC_MINOR__  96
+#define __builtin_expect(x, expected_value) (x)
+#endif
+
+#endif /* __I386_COMPILER_H */


--- 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:38 2001
+++ 2.4.3-ac12/include/asm-i386/semaphore.h Sat Apr 21 22:55:57 2001
@@ -38,6 +38,7 @@

 #include asm/system.h
 #include asm/atomic.h
+#include asm/compiler.h
 #include linux/wait.h
 #include linux/rwsem.h



depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size


#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_ISA=y
# CONFIG_SBUS is not set
CONFIG_UID16=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# Processor type and features
#
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUM4 is not set
CONFIG_MK6=y
# CONFIG_MK7 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_WP_WORKS_OK=y

Re: Linux 2.4.3-ac12

2001-04-23 Thread Byeong-ryeol Kim 

On Mon, 23 Apr 2001, Byeong-ryeol Kim wrote:

 On Sun, 22 Apr 2001, Alan Cox wrote:

Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_up_write_wake
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_down_write_failed
  
   Same thing with tdfx.o...
 
  Works for me as ever. What configuration options are you using. This sounds
  like some of the code is built with each kind of semaphore.
 

 I use 2 PCs at home. One is unnamed desktop - AMD K6-II+, ASUS P/I-P55T2P4
 rev. 3.10, 128 MB EDO RAM, etc.), the other is IBM ThinkPad 600X(Pentium III
 500, 192 MB PC100 RAM, etc.). But, the result of depmod under 2.4.3-ac12
 are the same.
 I use gcc-2.95.3 release + recommended patch about atexit from libc-alpha list
 which seemed to be applied in gcc-2.95.4 CVS tree).


I retried to compile 2.4.3-ac12 with Red Hat's 2.96-81(that of 7.1) without
the patch previously applied.
This time, I noticed strange thing.(I guess, it would not be a compiler
problem).
While doing 'depmod -ae -F /boot/System.map-2.4.3-ac12 2.4.3-ac12'
there was no error as far as rwsem_* is concerned, but when doing simply
'depmod -ae', the result was the same as before.( the same kernel
configuration, modutils is original 2.4.5-1 fetched from kernel site).

1) 'depmod -ae -F /boot/system.map-2.4.3-ac12 2.4.3-ac12'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size

2) 'depmod -ae'

depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/arch/i386/kernel/microcode.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/gamma.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/i810.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/mga.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/r128.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/tdfx.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/net/aironet4500_card.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_base.o
depmod: rwsem_up_read_wake
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_crtc2.o
depmod: rwsem_up_write_wake
depmod: rwsem_up_read_wake
depmod: rwsem_down_write_failed
depmod: rwsem_down_read_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_g450.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in 
/lib/modules/2.4.3-ac12/kernel/drivers/video/matrox/matroxfb_maven.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/binfmt_aout.o
depmod: rwsem_up_write_wake
depmod: rwsem_down_write_failed
depmod: *** Unresolved symbols in /lib/modules/2.4.3-ac12/kernel/fs/cmsfs/cms.o
depmod: get_hardsect_size



 #
 # Automatically generated make config: don't edit
 #
 CONFIG_X86=y
 CONFIG_ISA=y
 # CONFIG_SBUS is not set
 CONFIG_UID16=y

 #
 # Code maturity level options
 #
 CONFIG_EXPERIMENTAL=y

 #
 # Loadable module support
 #
 CONFIG_MODULES=y
 CONFIG_MODVERSIONS=y
 CONFIG_KMOD=y

 #
 # Processor type and features
 #
 # CONFIG_M386 is not set
 # CONFIG_M486 is not set
 # CONFIG_M586 is not set
 # CONFIG_M586TSC is not set
 # CONFIG_M586MMX is not set
 # CONFIG_M686 is not set
 # CONFIG_MPENTIUMIII is not set
 # CONFIG_MPENTIUM4 is not set
 CONFIG_MK6=y
 # CONFIG_MK7 is not set
 # CONFIG_MCRUSOE is not set
 # CONFIG_MWINCHIPC6 is not set
 # CONFIG_MWINCHIP2 is not set
 # CONFIG_MWINCHIP3D is not set
 # CONFIG_MCYRIXIII is not set
 CONFIG_X86_WP_WORKS_OK=y
 CONFIG_X86_INVLPG=y
 CONFIG_X86_CMPXCHG=y
 CONFIG_X86_XADD=y
 CONFIG_X86_BSWAP=y

Re: Linux 2.4.3-ac12

2001-04-22 Thread John Cavan 

Alan Cox wrote:
> 
> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> >
> > Same thing with tdfx.o...
> 
> "Works for me" as ever. What configuration options are you using. This sounds
> like some of the code is built with each kind of semaphore.

Mine is attached. I always run "make menuconfig", reconfirm my
selections (which haven't changed in ages), save it, and then run "make
dep" before building. I should note that I'm using a version of the DRI
from CVS from early April, but it has been perfectly happy until now. I
also tried it with the code in the kernel tree, same problem.

John
 config

Re: Linux 2.4.3-ac12

2001-04-22 Thread Mr. James W. Laferriere 


Hello Alan ,  To whom is this attributed ?  Tia ,  JimL

On Sun, 22 Apr 2001, Alan Cox wrote:
> o Hopefully fix bugtraq reported netfilter ftp
>   flaw
   ++
   | James   W.   Laferriere | System  Techniques | Give me VMS |
   | NetworkEngineer | 25416  22nd So |  Give me Linux  |
   | [EMAIL PROTECTED] | DesMoines WA 98198 |   only  on  AXP |
   ++

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread J . A . Magallon 


On 04.22 Dieter Nützel wrote:
> > My belief however is that several million people have gcc 2.96-69+, about 50
> > are likely to have random cvs snapshots and none of them are going to build
> > kernels with them anyway, as they wont work __builtin_expect or otherwise.
> >
> > Alan
> 
> I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
> And I think most people (here in Europe :-) are running 2.95.2 at the moment.
> But, yes the previously patches fixed it.
> 

That's going to change in a few weeks, I suspect. Dunno about SuSE, but just
released Mandrake 8.0 and RedHat 7.1 ship gcc-2.96.

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.3-ac12 #1 SMP Sun Apr 22 10:27:22 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12 unresolved symbol rwsem...

2001-04-22 Thread J Sloan 

Alan Cox wrote:

> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> >
> > Same thing with tdfx.o...
>
> "Works for me" as ever. What configuration options are you using. This sounds
> like some of the code is built with each kind of semaphore.

I'm getting the same thing here - Red Hat 7.1, amd K6/2
450 with a voodoo 3 -

After successful build and booting of 2.4.3-ac12, I found
I had no 3D acceleration, and saw error msgs similar to
those above, concerning tdfx.o.

As always, building agp and tdfx as modules.

jjs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Manuel McLure 


On 2001.04.22 11:48 Alan Cox wrote:
> > > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_up_write_wake
> > > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > > symbol rwsem_down_write_failed
> > 
> > Same thing with tdfx.o...
> 
> "Works for me" as ever. What configuration options are you using. This
> sounds
> like some of the code is built with each kind of semaphore.

.config attached - note that I build a lot more than I actually need. I
took a .config from the Red Hat 7 2.4 kernel RPM and have just been keeping
it up to date with "make oldconfig". I suppose some day I should go through
and select only the stuff I want...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<[EMAIL PROTECTED]> | and significant law, no man may kill a cat.
 | -- H.P. Lovecraft
 .config

Re: Linux 2.4.3-ac12

2001-04-22 Thread Alan Cox 

> > Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > symbol rwsem_up_write_wake
> > /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> > symbol rwsem_down_write_failed
> 
> Same thing with tdfx.o...

"Works for me" as ever. What configuration options are you using. This sounds
like some of the code is built with each kind of semaphore.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Alan Cox 

> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.

I suspect you would find that some of the problems with the initialisers
in structures were common to 2.7.2 across all platforms, but I may be wrong

> Maybe it's time to move that check to the arch include dir instead?

I have no problem there

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Jes Sorensen 

> "Roman" == Roman Zippel <[EMAIL PROTECTED]> writes:

Roman> Hi, Jes Sorensen wrote:

>> In principle you just need 2.7.2.3 for m68k, but someone decided to
>> raise the bar for all architectures by putting a check in a common
>> header file.

Roman> IIRC 2.7.2.3 has problems with labeled initializers for
Roman> structures, which makes 2.7.2.3 unusable for all archs under
Roman> 2.4.

True, so our bar is egcs-1.1.2, but thats still a bit from 2.96+

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Roman Zippel 

Hi,

Jes Sorensen wrote:

> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.

IIRC 2.7.2.3 has problems with labeled initializers for structures,
which makes 2.7.2.3 unusable for all archs under 2.4.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Manuel McLure 


On 2001.04.22 09:25 John Cavan wrote:
> Alan Cox wrote:
> > 2.4.3-ac12
> > o   Further semaphore fixes (David Howells)
> 
> Getting unresolved symbols in some modules (notably, for me, microcode.o
> and radeon.o)...
> 
> Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
> /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> symbol rwsem_up_write_wake
> /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
> symbol rwsem_down_write_failed

Same thing with tdfx.o...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
<[EMAIL PROTECTED]> | and significant law, no man may kill a cat.
 | -- H.P. Lovecraft

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Dieter Nützel 

> My belief however is that several million people have gcc 2.96-69+, about 50
> are likely to have random cvs snapshots and none of them are going to build
> kernels with them anyway, as they wont work __builtin_expect or otherwise.
>
> Alan

I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
And I think most people (here in Europe :-) are running 2.95.2 at the moment.
But, yes the previously patches fixed it.

Thanks,
Dieter
-- 
Dieter Nützel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Kölln-Straße 30
D-22527 Hamburg, Germany

email: [EMAIL PROTECTED]
@home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Mohammad A. Haque 

In case everyone missed my original patch =P

http://marc.theaimsgroup.com/?l=linux-kernel=98791931115515=2


Jes Sorensen wrote:
> 
> > "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:
> 
> Alan> The recommended compilers for non x86 are different too - eg you
> Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
> Alan> on.
> 
> In principle you just need 2.7.2.3 for m68k, but someone decided to
> raise the bar for all architectures by putting a check in a common
> header file.
> 
> Maybe it's time to move that check to the arch include dir instead?
> 
> Jes
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 

=
Mohammad A. Haque  http://www.haque.net/ 
   [EMAIL PROTECTED]

  "Alcohol and calculus don't mix. Project Lead
   Don't drink and derive." --Unknown  http://wm.themes.org/
   [EMAIL PROTECTED]
=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread John Cavan 

Alan Cox wrote:
> 2.4.3-ac12
> o   Further semaphore fixes (David Howells)

Getting unresolved symbols in some modules (notably, for me, microcode.o
and radeon.o)...

Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_up_write_wake
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_down_write_failed

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Jes Sorensen 

> "Alan" == Alan Cox <[EMAIL PROTECTED]> writes:

Alan> The recommended compilers for non x86 are different too - eg you
Alan> need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
Alan> on.

In principle you just need 2.7.2.3 for m68k, but someone decided to
raise the bar for all architectures by putting a check in a common
header file.

Maybe it's time to move that check to the arch include dir instead?

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Jesper Juhl 

f5ibh wrote:

> Alan,
> 
> 
>>> /usr/src/linux-2.4.3-ac12/lib/lib.a(rwsem.o): In function
>>> `rwsem_up_write_wake':rwsem.o(.text+0x3c6): undefined reference to
>>> `__builtin_expect'
>> 
>> Add a
>> 
>> #define __builtin_expect
> 
> 
> I had the same problem here, adding #define __builtin_expect in ../lib/rwsem.c
> solved the problem.
> 
> gcc is :
> 
> [jean-luc@debian-f5ibh] ~ # gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
> gcc version 2.95.3 20010315 (Debian release)
> 

Just a 'me too'. I had the same problem, and the #define fixed it nicely...

bash-2.03# gcc -v
Reading specs from /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/specs
gcc version 2.95.3 20010315 (release)


-- Jesper Juhl - [EMAIL PROTECTED]

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Alan Cox 

> Are you being deliberately obtuse?  2.97+ snapshots do all support 
> builtin_expect, which is what we were discussing.

I think we are having different conversations here.

The only valid inputs to the question are

Recommended
---
egcs-1.1.2  (miscompiles strstr  <2.4.4pre)
gcc 2.95.*  (miscompiles strstr  <2.4.4pre)

Recommended (for -ac at least)
--
rh-gcc 2.96-69+ (DAC960 fails due to gcc ABI change)
rh-gcc 2.96-78+

For the Brave
-
gcc 3.0 snapshots

There are no gcc 2.97 snapshots that compile the kernel correctly because
they have the broken bitfield packing ABI change. 

So if your belief is that we should insist on gcc 3.0 for __builtin_expect
then we should simply remove use of it completely. For 2.5.x it will be worth
making heavy use of once gcc 3.0 is out.

My belief however is that several million people have gcc 2.96-69+, about 50
are likely to have random cvs snapshots and none of them are going to build
kernels with them anyway, as they wont work __builtin_expect or otherwise.

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread f5ibh 


Alan,

>> /usr/src/linux-2.4.3-ac12/lib/lib.a(rwsem.o): In function
>> `rwsem_up_write_wake':rwsem.o(.text+0x3c6): undefined reference to
>> `__builtin_expect'
>
>Add a
>
>#define __builtin_expect

I had the same problem here, adding #define __builtin_expect in ../lib/rwsem.c
solved the problem.

gcc is :

[jean-luc@debian-f5ibh] ~ # gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
gcc version 2.95.3 20010315 (Debian release)

---
Regards

Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Philip Blundell 

>There are no gcc 2.97 snapshots that compile the kernel correctly because
>they have the broken bitfield packing ABI change. 

Oh right.  I didn't know about that particular nicety.

>My belief however is that several million people have gcc 2.96-69+, about 50
>are likely to have random cvs snapshots and none of them are going to build
>kernels with them anyway, as they wont work __builtin_expect or otherwise.

Fair enough.

p.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Philip Blundell 

There are no gcc 2.97 snapshots that compile the kernel correctly because
they have the broken bitfield packing ABI change. 

Oh right.  I didn't know about that particular nicety.

My belief however is that several million people have gcc 2.96-69+, about 50
are likely to have random cvs snapshots and none of them are going to build
kernels with them anyway, as they wont work __builtin_expect or otherwise.

Fair enough.

p.



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread f5ibh 


Alan,

 /usr/src/linux-2.4.3-ac12/lib/lib.a(rwsem.o): In function
 `rwsem_up_write_wake':rwsem.o(.text+0x3c6): undefined reference to
 `__builtin_expect'

Add a

#define __builtin_expect

I had the same problem here, adding #define __builtin_expect in ../lib/rwsem.c
solved the problem.

gcc is :

[jean-luc@debian-f5ibh] ~ # gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.3/specs
gcc version 2.95.3 20010315 (Debian release)

---
Regards

Jean-Luc
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Jes Sorensen 

 "Alan" == Alan Cox [EMAIL PROTECTED] writes:

Alan The recommended compilers for non x86 are different too - eg you
Alan need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
Alan on.

In principle you just need 2.7.2.3 for m68k, but someone decided to
raise the bar for all architectures by putting a check in a common
header file.

Maybe it's time to move that check to the arch include dir instead?

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread John Cavan 

Alan Cox wrote:
 2.4.3-ac12
 o   Further semaphore fixes (David Howells)

Getting unresolved symbols in some modules (notably, for me, microcode.o
and radeon.o)...

Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_up_write_wake
/lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
symbol rwsem_down_write_failed

John
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Mohammad A. Haque 

In case everyone missed my original patch =P

http://marc.theaimsgroup.com/?l=linux-kernelm=98791931115515w=2


Jes Sorensen wrote:
 
  "Alan" == Alan Cox [EMAIL PROTECTED] writes:
 
 Alan The recommended compilers for non x86 are different too - eg you
 Alan need 2.96 gcc for IA64, you need 2.95 not egcs for mips and so
 Alan on.
 
 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.
 
 Maybe it's time to move that check to the arch include dir instead?
 
 Jes
 -
 To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
 the body of a message to [EMAIL PROTECTED]
 More majordomo info at  http://vger.kernel.org/majordomo-info.html
 Please read the FAQ at  http://www.tux.org/lkml/

-- 

=
Mohammad A. Haque  http://www.haque.net/ 
   [EMAIL PROTECTED]

  "Alcohol and calculus don't mix. Project Lead
   Don't drink and derive." --Unknown  http://wm.themes.org/
   [EMAIL PROTECTED]
=
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Dieter Nützel 

 My belief however is that several million people have gcc 2.96-69+, about 50
 are likely to have random cvs snapshots and none of them are going to build
 kernels with them anyway, as they wont work __builtin_expect or otherwise.

 Alan

I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
And I think most people (here in Europe :-) are running 2.95.2 at the moment.
But, yes the previously patches fixed it.

Thanks,
Dieter
-- 
Dieter Ntzel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
Cognitive Systems Group
Vogt-Klln-Strae 30
D-22527 Hamburg, Germany

email: [EMAIL PROTECTED]
@home: [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Manuel McLure 


On 2001.04.22 09:25 John Cavan wrote:
 Alan Cox wrote:
  2.4.3-ac12
  o   Further semaphore fixes (David Howells)
 
 Getting unresolved symbols in some modules (notably, for me, microcode.o
 and radeon.o)...
 
 Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
 /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
 symbol rwsem_up_write_wake
 /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
 symbol rwsem_down_write_failed

Same thing with tdfx.o...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
[EMAIL PROTECTED] | and significant law, no man may kill a cat.
http://www.mclure.org | -- H.P. Lovecraft

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Roman Zippel 

Hi,

Jes Sorensen wrote:

 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

IIRC 2.7.2.3 has problems with labeled initializers for structures,
which makes 2.7.2.3 unusable for all archs under 2.4.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Jes Sorensen 

 "Roman" == Roman Zippel [EMAIL PROTECTED] writes:

Roman Hi, Jes Sorensen wrote:

 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

Roman IIRC 2.7.2.3 has problems with labeled initializers for
Roman structures, which makes 2.7.2.3 unusable for all archs under
Roman 2.4.

True, so our bar is egcs-1.1.2, but thats still a bit from 2.96+

Jes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Alan Cox 

 In principle you just need 2.7.2.3 for m68k, but someone decided to
 raise the bar for all architectures by putting a check in a common
 header file.

I suspect you would find that some of the problems with the initialisers
in structures were common to 2.7.2 across all platforms, but I may be wrong

 Maybe it's time to move that check to the arch include dir instead?

I have no problem there

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Alan Cox 

  Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
  /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
  symbol rwsem_up_write_wake
  /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
  symbol rwsem_down_write_failed
 
 Same thing with tdfx.o...

"Works for me" as ever. What configuration options are you using. This sounds
like some of the code is built with each kind of semaphore.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Manuel McLure 


On 2001.04.22 11:48 Alan Cox wrote:
   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
  
  Same thing with tdfx.o...
 
 "Works for me" as ever. What configuration options are you using. This
 sounds
 like some of the code is built with each kind of semaphore.

.config attached - note that I build a lot more than I actually need. I
took a .config from the Red Hat 7 2.4 kernel RPM and have just been keeping
it up to date with "make oldconfig". I suppose some day I should go through
and select only the stuff I want...

-- 
Manuel A. McLure KE6TAW | ...for in Ulthar, according to an ancient
[EMAIL PROTECTED] | and significant law, no man may kill a cat.
http://www.mclure.org | -- H.P. Lovecraft
 .config

Re: Linux 2.4.3-ac12 unresolved symbol rwsem...

2001-04-22 Thread J Sloan 

Alan Cox wrote:

   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
 
  Same thing with tdfx.o...

 "Works for me" as ever. What configuration options are you using. This sounds
 like some of the code is built with each kind of semaphore.

I'm getting the same thing here - Red Hat 7.1, amd K6/2
450 with a voodoo 3 -

After successful build and booting of 2.4.3-ac12, I found
I had no 3D acceleration, and saw error msgs similar to
those above, concerning tdfx.o.

As always, building agp and tdfx as modules.

jjs

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread J . A . Magallon 


On 04.22 Dieter Ntzel wrote:
  My belief however is that several million people have gcc 2.96-69+, about 50
  are likely to have random cvs snapshots and none of them are going to build
  kernels with them anyway, as they wont work __builtin_expect or otherwise.
 
  Alan
 
 I will not add fuel to the fire, but isn't 2.4.XX the "stable" version?
 And I think most people (here in Europe :-) are running 2.95.2 at the moment.
 But, yes the previously patches fixed it.
 

That's going to change in a few weeks, I suspect. Dunno about SuSE, but just
released Mandrake 8.0 and RedHat 7.1 ship gcc-2.96.

-- 
J.A. Magallon  #  Let the source
mailto:[EMAIL PROTECTED]  #  be with you, Luke... 

Linux werewolf 2.4.3-ac12 #1 SMP Sun Apr 22 10:27:22 CEST 2001 i686

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread Mr. James W. Laferriere 


Hello Alan ,  To whom is this attributed ?  Tia ,  JimL

On Sun, 22 Apr 2001, Alan Cox wrote:
 o Hopefully fix bugtraq reported netfilter ftp
   flaw
   ++
   | James   W.   Laferriere | System  Techniques | Give me VMS |
   | NetworkEngineer | 25416  22nd So |  Give me Linux  |
   | [EMAIL PROTECTED] | DesMoines WA 98198 |   only  on  AXP |
   ++

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: Linux 2.4.3-ac12

2001-04-22 Thread John Cavan 

Alan Cox wrote:
 
   Using /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_up_write_wake
   /lib/modules/2.4.3-ac12/kernel/drivers/char/drm/radeon.o: unresolved
   symbol rwsem_down_write_failed
 
  Same thing with tdfx.o...
 
 "Works for me" as ever. What configuration options are you using. This sounds
 like some of the code is built with each kind of semaphore.

Mine is attached. I always run "make menuconfig", reconfirm my
selections (which haven't changed in ages), save it, and then run "make
dep" before building. I should note that I'm using a version of the DRI
from CVS from early April, but it has been perfectly happy until now. I
also tried it with the code in the kernel tree, same problem.

John
 config