Re: kernel2.4 is not working
"not working"? can You post there exactly crash info? Best regards, Alexander mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -- Let's start the war, said Meggy -- - Original Message - From: "Blesson Paul" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, June 27, 2001 6:08 PM Subject: kernel2.4 is not working > hi all > Presnently I am using 2.2.16. Now I downloaded the 2.4.5 > kernel source code. Now I compiled it. I didn't changed anything in the > menuconfig. Still it not working. Why it it so >by >Blesson > - > 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/ > - 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: GCC3.0 Produce REALLY slower code!
There is not so much code in asm, so it's easy to patch code the most reasonable method is to write parsing program for that Best regards, Alexander mailto:[EMAIL PROTECTED] -- Let's start the war, said Meggy -- - Original Message - From: "Hacksaw" <[EMAIL PROTECTED]> To: "Alexander V. Bilichenko" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, June 26, 2001 3:30 AM Subject: Re: GCC3.0 Produce REALLY slower code! > >Here is link to Intel C compiler, that provide really faster code. > > > >http://developer.intel.com/software/products/compilers/linuxbeta.htm > > A quote from the site: > > * Not all of the GNU C language extensions, including the GNU inline assembly > format, are currently supported and, due to this, one cannot build the Linux > kernel with the beta release of the Intel compilers and the initial product > release. > > - 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: GCC3.0 Produce REALLY slower code!
Here is link to Intel C compiler, that provide really faster code. http://developer.intel.com/software/products/compilers/linuxbeta.htm - Original Message - From: "Tomasz Kłoczko" <[EMAIL PROTECTED]> To: "Alexander V. Bilichenko" <[EMAIL PROTECTED]> Sent: Monday, June 25, 2001 3:40 PM Subject: Re: GCC3.0 Produce REALLY slower code! > On Mon, 25 Jun 2001, Alexander V. Bilichenko wrote: > > > Although I just wanna say that there is no reason trying compile kernel with > > new shiny GCC 3.0 ;-). The result will be in kernel slowdown. > > > > Maybe, we can try to use Intel C compiler for some important ;-) (beta > > version work with linux). > > Is there avalaible any free/evaluation version this compiler ? > > kloczek > -- > --- > *Ludzie nie mają problemów, tylko sobie sami je stwarzają* > --- > Tomasz Kłoczko, sys adm @zie.pg.gda.pl|*e-mail: [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: GCC3.0 Produce REALLY slower code!
Although I just wanna say that there is no reason trying compile kernel with new shiny GCC 3.0 ;-). The result will be in kernel slowdown. Maybe, we can try to use Intel C compiler for some important ;-) (beta version work with linux). Best regards, Alexander mailto:[EMAIL PROTECTED] -- Let start the war, said Meggy -- - Original Message - From: "Matthias Andree" <[EMAIL PROTECTED]> To: "Alexander V. Bilichenko" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, June 25, 2001 1:16 PM Subject: Re: GCC3.0 Produce REALLY slower code! > On Mon, 25 Jun 2001, Alexander V. Bilichenko wrote: > > > Hello All! > > Some tests that I have recently check out. > > kernel compiled with 3.0 (2.4.5) function call: 100 iteration. 3% slower > > than 2.95. > > test example - hash table add/remove - 4% slower (compiled both > > with -O2 -march=i686). > > Why have this version been released? > > Because it comes with various other improvements, among them better > error detection, better C++ support, integrated GCJ (but regretfully > still without Ada 95), to name a few reasons. > > 3% to 4% loss in a first release of a new major release is not a big > deal, although I found similar results on leafnode's texpire. > However, 3% do not warrant me spending my time complaining. Maybe some > optimization is missing, maybe other operations than the ones you > checked are faster. So there. > > You might run an entire benchmark suite and report back, tough. :-) > - > 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/ > - 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: AMD thunderbird oops
Athlon TB CPUs >= 1000mhz potentially not stable at all because of great heat-production, without correct hardware maintence - try to check whether Your cpu overheating or cpu cooler make mighty vibration. Best regards, Alexander mailto:[EMAIL PROTECTED] - Original Message - From: "Alan Cox" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, June 25, 2001 10:55 AM Subject: Re: AMD thunderbird oops > > I just upgradede my system to an 1200Mhz AMD Athlon Thundirbird (266Mhz FSB) processor / 512Meg of RAM, and an Asus kt7a motherboard. > > > > It is oppsing left and right. I recompiled the kernel with Athelon as the CPU but keep getting these oopses.. > > > > I also get these same problems while trying to install RH 7.1 > > > > Anyone know is this a supported processor / MB and has anyone had these problems? > > Random oopses normally indicate faulty board cpu or ram (and the fault may > even just be overheating or dimms not in the sockets cleanly). I doubt its > the board design or model that is the problem, you probably jut have a faulty > component somewhere if its oopsing randomly even during installs and stuff > > memtest86, and heatsink compound may be your best friends > > - > 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/ > - 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/
GCC3.0 Produce REALLY slower code!
Hello All! Some tests that I have recently check out. kernel compiled with 3.0 (2.4.5) function call: 100 iteration. 3% slower than 2.95. test example - hash table add/remove - 4% slower (compiled both with -O2 -march=i686). Why have this version been released? Best regards, Alexander mailto:[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/
GCC3.0: Again
Again:
make[3]: Entering directory `/usr/src/linux/net/core'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-tri
graphs -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack
-boundary=2 -march=i686-c -o datagram.o datagram.c
{standard input}: Assembler messages:
{standard input}:747: Error: Junk `adcl $0x' after register
{standard input}:804: Error: Junk `adcl $0x' after register
make[3]: *** [datagram.o] Error 1
make[3]: Leaving directory `/usr/src/linux/net/core'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux/net/core'
make[1]: *** [_subdir_core] Error 2
make[1]: Leaving directory `/usr/src/linux/net'
make: *** [_dir_net] Error 2
Best regards,
Alexander mailto:[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/
GCC3.0 support: Kernel 2.4.5 compilation troubles
Hello all! trying to compile kernel I got following: make bzImage make[2]: Entering directory `/usr/src/linux/arch/i386/lib' /usr/src/linux/scripts/mkdep -D__KERNEL__ -I/usr/src/linux/include -Wall -Ws trict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mprefe rred-stack-boundary=2 -march=i686 -- checksum.S dec_and_lock.c delay.c getuser.S iodebug.c memcpy.c mmx.c old-checksum.c putuser.S strstr.c usercopy.c > .depend make[2]: Leaving directory `/usr/src/linux/arch/i386/lib' make[1]: Leaving directory `/usr/src/linux' gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fom it-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -ma rch=i686 -c -o init/main.o init/main.c In file included from /usr/src/linux/include/net/checksum.h:33, from /usr/src/linux/include/linux/raid/md.h:34, from init/main.c:24: /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:72:30: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:105:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:105:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:105:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:121:13: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:121:13: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:121:13: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:121:13: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:121:13: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated /usr/src/linux/include/asm/checksum.h:161:17: warning: multi-line string literals are deprecated gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fom it-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -ma rch=i686 -DUTS_MACHINE='"i386"' -c -o init/version.o init/version.c make CFLAGS="-D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2 -march=i686 " -C kernel make[1]: Enteri
Re: no ntfs support
Recompile new kernel (2.4.4 +) but write support for NTFS 5.0 is still down. - Original Message - From: "Blesson Paul" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 24, 2001 8:55 AM Subject: no ntfs support > Hi all > Thanks for the reply David. I have done the full > installation of redhat6.2. But there is no support for mounting for ntfs file > system. When ever we write mount -t ntfs /dev. it shows "ntfs not > supported by kernel". But when I went through the kernel source codes, there > is source code for ntfs. How to add the ntfs file driver to my kernel. Should > it need the full recompilation of the kernel codes > > Thanks in advance >by > Blesson > > > Get free email and a permanent address at http://www.netaddress.com/?N=1 > - > 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/ > - 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: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
I have the same bug in latest driver. And disabling MMIO didn't help... - Original Message - From: "Ignacio Monge" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, May 06, 2001 9:51 PM Subject: Re: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a > En Sun, 6 May 2001 13:03:03 -0400 > Ignacio Monge <[EMAIL PROTECTED]> escribió: > > > > > I've compiled 2.4.3mdk-25 source with Athlon optimizations, and the > > problem still happens. > > > > eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF > > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:4294967221 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > Interrupt:11 Base address:0x9000 > > > > Look at the HWaddr. With default kernel (not compiled), I haven't this > > problem and my ethernet card goes well and the HWaddr is: ·"HWaddr > > 00:E0:29:9A:CB:62 ". And I'm sure after reboot I *MUST* restore all the > > values of my BIOS setup. Believe me, I know. :( > > > > > > Here is the output of dmesg when loading the 81389too module: > > > > Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927 > > eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0x9000, > > ff:ff:ff:ff:ff:ff, IRQ 11 > > eth0: Identified 8139 chip type 'RTL-8139C' > > eth0: Setting 100mbps half-duplex based on auto-negotiated partner > > ability > > . > > > > "Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927"? > > What is this? Is this the cause of the bug? > > > > Now the lspci -vv: > > > > 00:0c.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX > > (rev 10) > > Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > > Stepping- SERR- FastB2B- > > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > > > SERR- > Latency: 32 (8000ns min, 16000ns max) > > Interrupt: pin A routed to IRQ 11 > > Region 0: I/O ports at 9000 [size=256] > > Region 1: Memory at da80 (32-bit, non-prefetchable) [size=256] > > Expansion ROM at [disabled] [size=64K] > > Capabilities: [50] Power Management version 2 > > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA > > PME(D0+,D1+,D2+,D3hot+,D3cold+) > > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > > > > I hope these lines can help. > > > ADDON: > > Dmesg: > [... > NETDEV WATCHDOG: eth0: transmit timed out > eth0: Tx queue start entry 4 dirty entry 0. > eth0: Tx descriptor 0 is . (queue head) > eth0: Tx descriptor 1 is . > eth0: Tx descriptor 2 is . > eth0: Tx descriptor 3 is . > eth0: Setting 100mbps half-duplex based on auto-negotiated partner ability > . > probable hardware bug: clock timer configuration lost - probably a VIA686a > motherboard. > probable hardware bug: restoring chip configuration. > > ...] > - > 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/ > - 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/
RTL8139 problems
Hello ! While working with RTL8139(C) based board I too often (5-10 min) get smth like this : Tx transmit timeout Dirty Tx entry 001 --- 002 --- 003 --- 004 and than i need to restart interface to bring it really on (because, it still not work after printk() smth Eth0 restarted) Disabling MMIO don't give any results. System: Chaintech 7AJA (VIA KT133, Latest bios) Duron 900 Kernel 2.4.4 (8139too 0.9.16) P.S. if I use old kernel 2.2.X and RTL81XX driver I don't get this error messages Alexander - 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/
