On 2001-03-27 08:39:32 PST Bob Schreibmaier [EMAIL PROTECTED] write
to comp.os.linux.misc
I just compiled the 2.2.19 kernel with gcc 2.95.3.
Compiles and runs just fine. I recompiled the
iBCS 2.1 module and it compiles just fine, too.
However, when I try to insmod iBCS it complains
about
Can CONFIG_X86_XADD be equated to CONFIG_X86_CMPXCHG?
David
-
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/
hello
i made an kernelupdate 2.2.16 to 2.4.2 and i am using RH 7.0
with the 2.2.16 kernel the usb-visor communication works perfekt.
now with the 2.4.2 kernel my usb does want to connect to my handspring-visor
#dmesg
...
usb.c: registered new driver hub
uhci.c: USB UHCI at I/O 0xd400, IRQ 9
Hi!
The attached patch puts the following functions into the .text.init
section.
aha1542_in
called by aha1542_getconfig, aha1542_query (all initfuncs)
aha1542_mbenable
called by aha1542_query (initfunc)
aha1542_in1
called in aha1542_mbenable (now also an initfunc)
Hi!
The attached patch puts the following function into the .text.init
section.
batch_entropy_init
called by rand_initialize (initfunc)
Patch is against 2.4.4pre1, to be included in the ac-series and in the
standard kernel.
Regards,
Matze
--
Matthias Hanischmailto:[EMAIL
Hello!
Jeff Garzik wrote:
How often does this occur? A lot, or just once or twice?
For example, after getting ~3MB of package information form
ftp.debian.org
I find this in /var/log/syslog:
Apr 11 09:56:26 unknown kernel: eth0: Too much work at interrupt,
IntrStatus=0x0001.
Apr 11 09:57:24
Hi,
I have this chipset in my new notebook (Gericom Webboy). Everything works
fine, but only modem doesn't work because it's software modem. I tried to
search net for drivers, tried to write to SiS (no aswer for two weeks ;(),
etc. - no success.
But, if you have this chipset in notebook you
Hi!
The attached patch puts the following functions into the .text.init
section.
mcheck_init
called by init_intel (initfunc)
init_irq_proc
called by sysctl_init (initfunc)
(already done for ARM, should be done for other archs, too)
start_context_thread
called
I have written a driver for a character set LCD module using parallel port. I want to
display a message when the kernel is initialized.
I added the following to start_kernel() in init/main.c
#include stdio.h
{
int i;
char line = "Loading Kernel";
FILE *ptr;
ptr =
On Tue, 10 Apr 2001, Paul McKenney wrote:
Disabling preemption is a possible solution if the critical section
is
short
- less than 100us - otherwise preemption latencies become a problem.
Seems like a reasonable restriction. Of course, this same limit
applies to locks and interrupt
OS: Mandrake 6.0RE
AMD K6-200 144 M
gcc 2.95.2-ipl3mdk
There is new compile error in 2.4.3. The difference with previous
case, # CONFIG_IPX_INTERN is not set
Compiler error message No 2:
gcc -D__KERNEL__ -I/usr/src/linux/include
Hi
I hope I'm not the n-th person reporting this bug. Dump output and a
short description are attached.
kind regards
Markus
Setup Kernel 2.4.4-pre1, SuSE 7.1
Happened during the startup phase when trying to automount
==
I can use "ps" to see memory usage of daemons and user programs.
I can't find any memory information of kernel with "top" and "ps".
Do you know how to take memory usage information of kernel ?
Thanks for your help.
Regarding this issue, I have a similar problem if I do a free on my system
f) As noted, the account timers (task user/system times) would be much
more accurate with the tick less approach. The cost is added code in
both the system call and the schedule path.
Tentative conclusions:
Currently we feel that the tick less approach is not acceptable due to
(f). We felt
Hi all
A friend of mine asked me how he could restrict which ports a given user
should be allowed to open. He's running a shell server people use for
IRC bots. I don't think this is possible today. Is it possible to build
it without ruining the whole system? Like a kernel module?
Please cc: to
On Tue, Apr 10, 2001 at 07:30:36PM -0700, Miles Lane wrote:
Hi,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LKML
Comments?
Proper place to do this discussion is [EMAIL PROTECTED]
The amount of traffic won't
On Tue, 10 Apr 2001, Rik van Riel wrote:
I'll try to come up with a recalculation change that will make
this thing behave better, while still retaining the short time
slices for multiple normal-priority tasks and the cache footprint
schedule() and friends currently have...
OK, here it is.
It's nice; we have the same notebook... Yes, my real problem is X. Thank you
for your detailed answer.
How could I configure frame-buffer support? Which dist+kernel+X version do
you use?
Hi,
so, now I used RH 6.2 with 2.4.3 kernel on my notebook. X is something
from CVS, don't know what
First it does not work because you do not have access to libc in the
kernel. Secondly your LCD driver is not available at the time of
start_kernel so there is no one to listen to the /dev/lcd.
The quickest hack would be to find your lcd driver and modify it to spit
out the Loading Kernel,
Hi,
- on COMPAQ Proliant 6500 (P11) servers I have an embeded LCD,
is there any kernel patch and/or user tools to use it ?
- lately one of those servers hangs quite often
I've changed hardware parts (mixing from other boxes) and concluded it's
definately software, most probably
Any pointers ? Patches to apply ?
Don't you people hate to followup yourself ..
Anyway it's updated RH70 on 2.4.3 kernel !
--
Mario Mikoevi (Mozgy)
My favourite FUBAR ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
To possbile answer my own question:
if I do a can on /proc/slabinfo I get on the machine with "MISSING" memory:
slabinfo - version: 1.1 (SMP)
--- cut out
inode_cache 920558 930264480 116267 1162831 : 124 6
--- cut out
dentry_cache 557245 638430128 21281 212811
I've recently installed a SDT-9000 tape drive. Running kernel 2.4.x I've
noticed the following (critical) problem:
Apparently the data are corrupted on the way to (from?) tape. I'm sure the
DAT
drive is good (worked good on NT, head clean, new cartridge). It doesn't
report
data errors. I've got
On Tue, 10 Apr 2001, Zdenek Kabelac wrote:
I think it would be wrong if we could not add new very usable features
to the system just because some old hardware doesn't support it.
s/old/crappy/ -- even old hardware can handle vsync IRQs fine. E.g. TVGA
8900C.
--
+ Maciej W. Rozycki,
" " == Jussi Hamalainen [EMAIL PROTECTED] writes:
I do have a question about lockd. How do I get it back if I
need to restart portmap? Running rpc.lockd doesn't seem to have
any effect whatsoever on the listed rpc services and I can't
just reload the module since nfs
These things usually sit off a serial port.
I.E. /dev/lcd is a link to /dev/ttyS0 or whatever.
Anyway the main point is you don't have access to libc.
So how can you access the serial port from the booting
kernel. Well to spit kernel messages out the serial
port you pass the console=ttyS1,19200
Hi!
This is not correct, because we want the power button to be configurable.
The user should be able to redefine the power button's action, perhaps to
only sleep the system. We currently surface button events to acpid, which
then can do the right thing, including a shutdown -h now (which I
386 could use a simpler setup and is non SMP
The idea was to have a `generic' kernel that works on all architectures.
If you drop 386 support much is better already.
Having the 386 non SMP only means you dont have to worry about this. We dont
currently support an SMP kernel that boots
My reasoning is that who uses a 386 is not interested in speed, so a little
bit more slowness is not that bad.
You realize that the alternative for distributions is to drop 386 support
completely?
Rubbish. Mandrake and Red Hat have been shipping multiple kernel images,
multiple gzips and
It's currently done this way, ld-linux.so looks in a special "686" path when
the ELF vector mentions it, otherwise normal path. There is a special 686
version of glibc and linuxthread. Just it's a very complicated and disk
space chewing solution for a simple problem (some distributions are
XFree86 X window updates are slower on 2.4 than 2.2, by a significant amount.
I've observed this comparing 2.2.18 with 2.4.1 and one of the 2.4.pre kernels.
Quite possible since we haven't really tuned it hard yet. Also there are some
problems with VIA chipsets and 2.4 that directly impact
On Wed, 11 Apr 2001, David Howells wrote:
Can CONFIG_X86_XADD be equated to CONFIG_X86_CMPXCHG?
Yes. Modulo very early i486s which used incorrect opcodes for cmpxchg.
They can probably be safely ignored.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
Here's the RW semaphore patch again (rwsem2.diff) with a fallback to spinlocks
if XADD/CMPXCHG aren't available.
I've put the two implementations in separate headers as suggested.
David
diff -uNr linux-2.4.3/arch/i386/config.in linux/arch/i386/config.in
--- linux-2.4.3/arch/i386/config.in
cat calahan.reply.txt
-
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/
On Tuesday 10 April 2001 18:37, you wrote:
Daniel Phillips writes:
The zeroth block of an indexed directory is the index root. Initially
the index has only one block. The following blocks are normal ext2
directory entry blocks. When the directory grows large enough to fill
all the
To possbile answer my own question:
if I do a can on /proc/slabinfo I get on the machine with "MISSING" memory:
slabinfo - version: 1.1 (SMP)
--- cut out
inode_cache 920558 930264 480 116267 116283 1 : 124 6
--- cut out
dentry_cache 557245 638430 128 21281 21281 1 : 252 126
This seems to happen on my system too but I have and IDE tape:
Apr 3 00:00:48 www kernel: ide-tape: hdb - ht0: Seagate STT8000A rev 5.02
Apr 3 00:00:48 www kernel: ide-tape: hdb - ht0: 600KBps, 14*26kB buffer, 5850kB
pipeline, 80ms tDSC, DMA
I have managed to recover the tar archive by
Mario Mikocevic wrote:
Any pointers ? Patches to apply ?
Don't you people hate to followup yourself ..
Anyway it's updated RH70 on 2.4.3 kernel !
You didn't mention what type of 6500 it is? PPro? PII? PIII? How man
processors installed?
We use almost exclusively proliants
On Wed, 11 Apr 2001, info wrote:
OS: Mandrake 6.0RE
AMD K6-200 144 M
gcc 2.95.2-ipl3mdk
# CONFIG_IPX_INTERN is not set
# CONFIG_SYSCTL is not set
CONFIG_HPFS_FS=y
Compiler error message No 4:
this may be a stupid question, but are you doing a 'make clean' after
changing config
Apr 8 23:33:09 horus kernel: hub.c: USB new device connect on bus1/1,
assigned device number 5
Apr 8 23:33:12 horus kernel: usb_control/bulk_msg: timeout
Apr 8 23:33:12 horus kernel: usb.c: USB device not accepting new
address=5 (error=-110)
Funny, I've been getting the same messages (on
óÒÄ, 11 áÐÒ 2001 × ÓÏÏÂÝÅÎÉÉ ÎÁ ÔÅÍÕ "Re: 2.4.3 compile error No 4" ÷Ù ÎÁÐÉÓÁÌÉ:
On Wed, 11 Apr 2001, info wrote:
OS: Mandrake 6.0RE
AMD K6-200 144 M
gcc 2.95.2-ipl3mdk
# CONFIG_IPX_INTERN is not set
# CONFIG_SYSCTL is not set
CONFIG_HPFS_FS=y
Compiler error message No 4:
I'd like you to look over it. It seems newer GCC's (snapshots and the
upcoming 3.0) will be more strict when modifying some values through
assembler-passed pointers - in this case, the passed semaphore structure got
freed too early, causing massive stack corruption on early bootup.
The
This seems to happen on my system too but I have and IDE tape:
Seems uncurrelated. I'm trying this:
# cd ~archive; tar cvzf /dev/tapes/tape0 # using devfs on rewinding dev
(some 600MB of stuff...)
where ~archive is on a SCSI drive (ext2 fs on LVM volume if can help)
# tar tvzf
Hello,
I believe there is a bug in Linux Kernel 4.2. I tried Kernels 2.4.2 and 2.4.0
with my german SuSE-Distribution (7.1).
The problem occurs with my SCSI MO drive. while it works fine with Kernel
2.2.18 on the same machine and distribution, the behaviour with the newer
Kernels is like that:
Hi
Here is my saga continued. I had as mentioned in the preceding post 500mb of
Inode cache entries and about 80mb of dentry_cache entries, accounting for +-
600mb if "missing" memory.
These should be dynamically de-allocatable, so if a program needs the ram it
will be freed as necessary. So
On Wed, 11 Apr 2001, info wrote:
this may be a stupid question, but are you doing a 'make clean' after
changing config parameters?
Maybe it's is a stupid order, but I do this:
1. untar kernel into /usr/src (there was no /linux subdirectory)
2. copy my own config file (named config-k6)
Hi,
Yesterday i tried to start cdda2wav but somehow it didn't do
anything.
It didn't die to kill -9 too. Machine was slow but usable.
vmstat 10 output:
procs memoryswap io
system cpu
r b w swpd free buff cache si sobi
On Wed, 11 Apr 2001, Marcin Kowalski wrote:
I then do a swapoff /dev/sda3 (250mb used), this completely locks the machine
for 50 seconds and pushes the load to 31 when I can log back in. Then
micraculously I am using only 170mb of physical ram. I turn swap back on and
all is well
Can
Hello David and people,
I've just consulted with one of the gcc people we have here, and he says
that
the '"memory"' constraint should do the trick.
Do I take it that that is actually insufficient?
I don't remember exactly, it's been a while, but I think it was not
sufficient when I came
I've been discussing it with some other kernel and GCC people, and they think
that only "memory" is required.
What are the reasons against mentioning sem-count directly as a "=m"
reference? This makes the whole thing less fragile and no more dependent
on the memory layout of the structure.
Further fun...
Now after bouncing the swap and clearing out memory I decided to run the
test.pl script again to suck up some more memory...
Box dies, pretty much for 15 seconds, when it comes back load is at 8.0
kernel syslog messages..::
Apr 11 16:37:13 mkdexii kernel: sym53c896-1-3,0:
"Grover, Andrew" [EMAIL PROTECTED] writes:
This is not correct, because we want the power button to be
configurable. The user should be able to redefine the power
button's action, perhaps to only sleep the system. We currently
surface button events to acpid, which then can do the right
John R Lenton [EMAIL PROTECTED] writes:
[...]
Just today a friend saw my box shutdown via the powerbutton and
wondered if he coudln't set his up to trigger a different event
(actually two: he wanted his sister - the guilty party - zapped, and
a webcam shot of her face to prove it)...
That
Hello David,
I've been discussing it with some other kernel and GCC people, and they
think
that only "memory" is required.
Hmm.. I just looked at my GCC problem report from December, perhaps you're
interested, too:
http://gcc.gnu.org/ml/gcc-bugs/2000-12/msg00554.html
The example in there
Pavel Machek [EMAIL PROTECTED] writes:
Hi!
This is not correct, because we want the power button to be
configurable. The user should be able to redefine the power
button's action, perhaps to only sleep the system. We currently
surface button events to acpid, which then can do the
On Wed, 11 Apr 2001, Andreas Franck wrote:
Hello David,
I've been discussing it with some other kernel and GCC people, and they
think
that only "memory" is required.
Hmm.. I just looked at my GCC problem report from December, perhaps you're
interested, too:
Le 10-Apr-2001, Manuel A. McLure crivait :
This may be the difference - I always set "Plug-n-Play OS: No" on all my
machines. Linux works fine and it doesn't seem to hurt Windows 98 any.
I've been told it affects the way IRQs are assigned; With "PnP OS: No", some
boards (seen on several Asus
Hi,
I think that it is the bug of FAT-fs.
Please try the following patch.
Thanks
--
OGAWA Hirofumi [EMAIL PROTECTED]
fat-2.4.3.diff.gz
I believe there is a bug in Linux Kernel 4.2. I tried Kernels 2.4.2 and 2.4.0
with my german SuSE-Distribution (7.1).
The problem occurs with my SCSI MO drive. while it works fine with Kernel
2.2.18 on the same machine and distribution, the behaviour with the newer
SCSI M/O drives with 2K
I've been experiencing a particular kind of hang for many versions
(since 2.3.99 days, recently seen with 2.4.1, 2.4.2, and 2.4.2-ac4) on
the alpha architecture. The symptom is that any program that tries to
access the process table will hang. (ps, w, top) The hang will go away
by itself after
On Wed, 11 Apr 2001, Rik van Riel wrote:
OK, here it is. It's nothing like montavista's singing-dancing
scheduler patch that does all, just a really minimal change that
should stretch the nice levels to yield the following CPU usage:
Nice05 10 15 19
%CPU 100 56 256
# CONFIG_IPX_INTERN is not set
# CONFIG_SYSCTL is not set
net/network.o: In function `ipx_init':
net/network.o(.text.init+0x1008): undefined reference to `ipx_register_sysctl'
Do not do it! You cannot control some very important features of IPX without
sysctl! Anyway below is patch, Alan
Daniel Phillips wrote:
ls already can't handle the directories I'm working with on a regular
basis. It's broken and needs to be fixed. A merge sort using log n
temporary files is not hard to write.
ls -U | sort
should do the trick.
-- Jamie
-
To unsubscribe from this list: send the line
Mark Salisbury wrote:
The complexity comes in when you want to maintain indexes into the list
for quick insertion of new timers. To get the current insert
performance, for example, you would need pointers to (at least) each of
the next 256 centasecond boundaries in the list. But the
Maciej W. Rozycki wrote:
On Tue, 10 Apr 2001, Zdenek Kabelac wrote:
I think it would be wrong if we could not add new very usable features
to the system just because some old hardware doesn't support it.
s/old/crappy/ -- even old hardware can handle vsync IRQs fine. E.g. TVGA
8900C.
Hello,
I was wondering if anyone has a patch, or is working on something for what
im looking for, or if they are interested in an idea i have (forgive me if
this is someone elses idea, ill give credit to them), for file monitoring
at the kernel level.
I have put up a brief explanation of what im
On 11 Apr 01 at 20:15, info wrote:
By the way, I thung that it is a good idea - to modify
xconfig/meniconfig script in manner to make disable ipx if sysctl
setted off - like in many other cross-dependance options.
Without sysctl you cannot disable Netbios propagation packet routing.
And
i'm running 2.4.3, and attempting to use the ati mach64 framebuffer
driver (atyfb.c) in place of the slooow vesa fb. my card is an ati
mach64 vt4 according to lspci, claimed in atyfb.c line 555 to be
supported. on startup, however, i get kernel decompression, followed
by a black screen. it
One rule of optimization is to move any code you can outside the loop.
Why isn't the nice_to_ticks calculation done when nice is changed
instead of EVERY recalc.? I guess another way to ask this is, who needs
to see the original nice? Would it be worth another task_struct entry
to move this
Here's the RW semaphore patch #3. This time with more asm constraints added.
David
diff -uNr linux-2.4.3/arch/i386/config.in linux-rwsem/arch/i386/config.in
--- linux-2.4.3/arch/i386/config.in Thu Apr 5 14:44:04 2001
+++ linux-rwsem/arch/i386/config.in Wed Apr 11 08:38:04 2001
@@
You wouldn't happen to have khttpd loaded as a module, would you? I've seen
this type of problem caused by that before...
- Pete
Bob McElrath wrote:
I've been experiencing a particular kind of hang for many versions
(since 2.3.99 days, recently seen with 2.4.1, 2.4.2, and 2.4.2-ac4) on
Em Wed, Apr 11, 2001 at 06:02:35PM +0200, Petr Vandrovec escreveu:
# CONFIG_IPX_INTERN is not set
# CONFIG_SYSCTL is not set
net/network.o: In function `ipx_init':
net/network.o(.text.init+0x1008): undefined reference to `ipx_register_sysctl'
Do not do it! You cannot control some
þÔ×, 12 áÐÒ 2001, × ÓÏÏÂÝÅÎÉÉ ÎÁ ÔÅÍÕ "Re: 2.4.3 compile error No 3", Petr Vandrovec
ÎÁÐÉÓÁÌ:
On 11 Apr 01 at 20:15, info wrote:
By the way, I thung that it is a good idea - to modify
xconfig/meniconfig script in manner to make disable ipx if sysctl
setted off - like in many other
I have never tried it myself but it looks like it might do what you want:
http://oss.sgi.com/projects/fam/
fam and imon FAQ
===
What is fam?
fam, the File Alteration Monitor, provides an API which applications can use to
be notified when specific files or directories are
David Howells wrote:
Here's a patch that fixes RW semaphores on the i386 architecture. It is very
simple in the way it works.
The lock counter is dealt with as two semi-independent words: the LSW is the
number of active (granted) locks, and the MSW, if negated, is the number of
active
Peter Rival [[EMAIL PROTECTED]] wrote:
You wouldn't happen to have khttpd loaded as a module, would you? I've seen
this type of problem caused by that before...
Nope...
- Pete
Bob McElrath wrote:
I've been experiencing a particular kind of hang for many versions
(since 2.3.99
On 11 Apr 01 at 20:34, info wrote:
, 12 2001, - +- +- "Re: 2.4.3 compile error No 3", Petr Vandrovec
+-+-|:
On 11 Apr 01 at 20:15, info wrote:
Without sysctl you cannot disable Netbios propagation packet routing.
And no machine with enabled Netbios routing passes our 'you must not
Matti Aarnio wrote:
On Tue, Apr 10, 2001 at 07:30:36PM -0700, Miles Lane wrote:
Hi,
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LKML
Comments?
Proper place to do this discussion is [EMAIL PROTECTED]
It sounds good in
Jamie Locker wrote:
Mark Salisbury wrote:
The complexity comes in when you want to maintain indexes into the list
for quick insertion of new timers. To get the current insert
performance, for example, you would need pointers to (at least) each of
the next 256 centasecond
I'm hesitant to do this, since 1) You can put those printk's in yourself to
find out if your particular system is working and 2) You can just cat
/proc/sys/event, hit a button, and you should see output if it works.
Regards -- Andy
From: John Fremlin [mailto:[EMAIL PROTECTED]]
"Grover,
Hmpf. Haven't seen this at all on any of the Alphas that I'm running. What
exact system are you seeing this on, and what are you running when it happens?
- Pete
Bob McElrath wrote:
Peter Rival [[EMAIL PROTECTED]] wrote:
You wouldn't happen to have khttpd loaded as a module, would you?
What compiler are you using to compile the kernel?
Dave.
On Wed, 11 Apr 2001 [EMAIL PROTECTED] wrote:
Well, I don't know then. You have to debug it. It's probably
something stupid
(if fundamental services like alloc_skb/kfree_skb were
completely buggy
someone surely would have
-Original Message-
From: ext Dave Airlie [mailto:[EMAIL PROTECTED]]
Sent: 11. April 2001 20:20
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: RE: skb allocation problems (More Brain damage!)
What compiler are
Proper place to do this discussion is
[EMAIL PROTECTED]
It sounds good in theory. In practice, though, almost all of the
design discussions have been occuring in private e-mail.
For example, I have seen none of the messages discussing
the changes planned for the power management
Andrew Morton wrote:
I think that's a very good approach. Sure, it's suboptimal when there
are three or more waiters (and they're the right type and order). But
that never happens. Nice design idea.
Cheers.
These numbers are infinity :)
I know, but I think Linus may be happy with the
Coudl the problem be in the NIC driver not in the alloc_skb? I have used
both 2.4.{1,3} for some time and never seen this corruption. I use ping
-f with various packet sizes for stress testing my IPSec boxes... these do
quite a bit of extra skb creation as an IPSec header sometimes does not
Followup to: 3AD2CE98.28151.46E93A@localhost
By author:"Ulrich Windl" [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Hi, Cycle Counters,
Linux currently tries to synchronize TSCs for consistent time in SMP
systems. One would not believe what combinations of hardware are tried,
Peter Rival [[EMAIL PROTECTED]] wrote:
Hmpf. Haven't seen this at all on any of the Alphas that I'm running. What
exact system are you seeing this on, and what are you running when it happens?
This is a LX164 system, 533 MHz.
I have a hunch it's related to the X server because I've seen it
appropriately.) One could, at least theoretically, make them usable
in kernel space only (in user space there is no hope, since you can't
know which CPU's TSC you're reading), but these machines seem to be so
rare that hardly anyone technical enough to fix it cares.
Im working on making the
Followup to: [EMAIL PROTECTED]
By author:Linus Torvalds [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Note that the "fixup" approach is not necessarily very painful at all,
from a performance standpoint (either on 386 or on newer CPU's). It's not
really that hard to just replace the
Followup to: [EMAIL PROTECTED]
By author:Alan Cox [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Yes, and with CMPXCHG handler in the kernel it wouldn't be needed
(the other 686 optimizations like memcpy also work on 386)
They would still be needed. The 686 built glibc
Alan Cox wrote:
appropriately.) One could, at least theoretically, make them usable
in kernel space only (in user space there is no hope, since you can't
know which CPU's TSC you're reading), but these machines seem to be so
rare that hardly anyone technical enough to fix it cares.
Coudl the problem be in the NIC driver not in the alloc_skb?
No, i don't think so...i got the dump of the packet at the local_out and
post routing hooks found it in bad shape there. Here it is what it
looks like:
45 0 0 80 0 0 40 0 ff 1 2d f8 c0 a8 66 16 c0 a8 66 1d 0 0 e4 48 11 d 0 0 14
On Wed, Apr 11, 2001 at 01:47:18PM -0400, Bart Trojanowski wrote:
Coudl the problem be in the NIC driver not in the alloc_skb? I have used
both 2.4.{1,3} for some time and never seen this corruption. I use ping
-f with various packet sizes for stress testing my IPSec boxes... these do
On Wed, 11 Apr 2001, Bernd Schmidt wrote:
The example in there compiles out-of-the box and is much easier to
experiment on than the whole kernel :-)
That example seems to fail because a "memory" clobber only tells the compiler
that memory is written, not that it is read.
The above
On Wed, Apr 11, 2001 at 08:15:49PM +0300, [EMAIL PROTECTED] wrote:
And as a I said earlier, only ping packets with size within certain range
create this problem..Something is terribly wrong here!! But as I am not
a Linux mm guru, i can't tell what is wrong here!
What you can try is to
"Grover, Andrew" [EMAIL PROTECTED] writes:
[...]
+ printk ("acpi: Power button pressed!\n");
[...]
+ printk("acpi: Sleep button pressed!\n");
Do you think you could keep the above part of the patch? It would be
nice to know how much of ACPI was
On Wed, 11 Apr 2001, David Howells wrote:
These numbers are infinity :)
I know, but I think Linus may be happy with the resolution for the moment. It
can be extended later by siphoning off excess quantities of waiters into a
separate counter (as is done now) and by making the access
On Mon, 9 Apr 2001, Alan Cox wrote:
Its worth doing even on the ancient x86 boards with the PIT.
Note that programming the PIT is slw and doing it on every timer
add_timer/del_timer would be a pain.
You only have to do it occasionally.
When you add a timer newer than the
I had the almost exact same thing happen to me just yesterday, I started up
xcdroast, and cdda2wav and kswapd went crazy, backed out of X and all was
well, and still is.
Same kernel as you too.
On approximately Wed, Apr 11, 2001 at 04:24:48PM +0200, Priit Randla wrote:
Hi,
1 - 100 of 352 matches
Mail list logo
