haha, ok! :)
(well i'm sure you know the history, but for others -- that code entered
apache not specifically for linux... but specifically for handling the
many early-to-mid 90s unixes that just plain broke on multiple accept :)
-dean
On Mon, 6 Nov 2000, David S. Miller wrote:
Date:
David S. Miller wrote:
Linux resends 21:557, Windows95 (finally) acknowledges it.
Looking at the equivalent 220 traces, the only difference appears to
be that the packets are not getting dropped.
This smells of "wrong checksums getting generated", in my opinion.
(This is not my field of
David S. Miller wrote:
It is clear though, that something is messing with or corrupting the
packets. One thing you might try is turning off TCP header
compression for the PPP link, does this make a difference?
Try specifying "asyncmap 0x" too.
Roger.
On Mon, Nov 06, 2000 at 11:27:54PM -0800, David S. Miller wrote:
What 2.4.x is doing is completely legal. Really, even if not all of
these people are from Earthlink (well, you should see if this is for
certain) they may all be using the same buggy terminal server at these
different ISPs.
I
On Mon, Nov 06, 2000 at 11:16:21PM -0800, Jordan Mendelson wrote:
It is clear though, that something is messing with or corrupting the
packets. One thing you might try is turning off TCP header
compression for the PPP link, does this make a difference?
Actually, there has been several
Here's a slightly modified version of Andrew's patch: the version he
sent me on Sunday contained an incomplete merge of my fix to
locks_remove_posix(), meaning that the host server was not being
notified that posix locks were cleared in the call to close().
The following patch contains his
On Tue, Nov 07, 2000 at 08:59:11AM +0100, Arnaud S . Launay wrote:
In the fact, the first limit to be reached will be NR_TASKS defined in
linux/tasks.h:
#define NR_TASKS512 /* On x86 Max 4092, or 4090 w/APM configured. */
So I wonder if we could really have more than 4092
I'm running 2.2.17 vanilla on a UP x86 box, and getting occasionally a
couple of 'VM: do_try_to_free_pages failed' messages.
The system appears to be running perfectly. It's almost out of real RAM,
but has about 100M swap unused.
I can't figure out how this happens. Specifically, how come the
On Tue, 07 Nov 2000, Gerhard Mack wrote:
Then none of this is relevant to you, since you can't unload any modules! And
now you're the one doing the trolling... WTF do you think module code is
supposed to do when you don't use modules?!
Simple ... I'd rather the hardware was set to 0
On Mon, 06 Nov 2000, Horst von Brand wrote:
"James A. Sutherland" [EMAIL PROTECTED] said:
On Mon, 06 Nov 2000, Horst von Brand wrote:
[...]
The problem (AFAIU) is that if the levels aren't set on startup, they are
random in some cases.
So set them on startup. NOT when the driver
As long as you don't try to do any more mm once you've allocated with
malloc(0), and as long as you haven't done any previous allocations with
malloc, you should be able to scribble all over malloc. In fact, if you
want, I think you can scribble all over your own stack without causing
Linux
We have a generic way of doing this which we are about to release - called
GKHI (Generalised Kernel Hooks Interface) would you like a copy to test?
Richard Moore - RAS Project Lead - Linux Technology Centre (PISC).
http://oss.software.ibm.com/developerworks/opensource/linux
Office: (+44)
Alan Cox wrote:
It would probably be better (in this case) to increment the module count
when the mixer settings go above 0, and decrement it when the settings
go totally to 0. This prevents an unwanted unload.
Thats about 200 lines of code and also about 50,000 emails complaining
On Mon, 6 Nov 2000, James Simmons wrote:
Unfortunately I cannot confirm this. Checked 2.4.0-test10 and the problem
is still there. I digged further and it seems to be a race condition(?)
triggered by swapped out stuff - because just starting X and switching
back to the console works
Hello Horst!
Strange somebody from a distribution forgets _the_ most important use of
modules: Remember old-time Slackware, with dozens of different boot
diskettes, and the imperative to compile a kernel to your machine once you
got it running?
But how is this related to automatic unloading
Martin Mares wrote:
Hi Alan!
If the sound card is only used some of the time or setup and then used
for TV its nice to get the 60K + 128K DMA buffer back when you dont need it
especially on a low end box
So why don't we allocate / free the DMA buffer on device open / close instead
Hi folks,
Does anyone know why a Linux ethernet driver might appear to be up
working (that is, no errors, ifconfig says UP, etc), and the board has a
link light on it, but the hub link light is not on and no packets are
transmitted or received? rmmod/insmod of the driver doesn't help.
I
On Mon, 6 Nov 2000, Michael Vines wrote:
On Mon, 6 Nov 2000, Erik Mouw wrote:
On Mon, Nov 06, 2000 at 10:11:11AM -0500, Michael Vines wrote:
On Mon, 6 Nov 2000, Erik Mouw wrote:
Use LD_PRELOAD instead.
You could also write a simple kernel module that replaces the open system
On Mon, 6 Nov 2000, Erik Mouw wrote:
On Mon, Nov 06, 2000 at 10:11:11AM -0500, Michael Vines wrote:
On Mon, 6 Nov 2000, Erik Mouw wrote:
Use LD_PRELOAD instead.
You could also write a simple kernel module that replaces the open system
call. See the Linux Kernel Module Programming
On Tue, 7 Nov 2000, Tigran Aivazian wrote:
To test Y2k readiness of programs one simply can use my timetravel kernel
module. No, doing things in userspace is far more complex and less
reliable and also simply not good enough (because doesn't cover the case
yes, yes, I am aware of
From: "Matthew Sanderson" [EMAIL PROTECTED]
I'm running 2.2.17 vanilla on a UP x86 box, and getting occasionally a
couple of 'VM: do_try_to_free_pages failed' messages.
The system appears to be running perfectly. It's almost out of real RAM,
but has about 100M swap unused.
I can't figure
On Fri, Nov 03, 2000 at 01:25:10AM -0500, [EMAIL PROTECTED] wrote:
Just happened with test10, same circumstances .. font map got corrupted, and
noise on the screen. Switching back and forth from X to a vc fixed it, tho.
Sort of amusing that it (apparently) only happens with ppp + wget
I've noticed noticeably slower screen refresh in 2.4.x than under the
2.2 kernel series. It's most noticeable when running xscreensaver with
fast scrolling patterns, or when doing opague moves of large windows.
I'm using Xfree 4.01 and the XFree driver for the Nvidia card (not the
Nvidia binary
I am trying to use removable EIDE hard disks on
a Red Hat Linux 6.1 machine, for backup / walknet purposes.
Issuing a BLKRRPART ioctl call immediately after
changing the disk works, but only if the new disk is no larger than the disk
present at boot time (smaller and equal capacity disks
I noticed that Pentium 4 isn't an config option in 2.4.0-test10. Is
someone working on a patch for the the kernel (if needed) to support the
Pentium 4 after 2.4.0 is released?
And also for 2.2. 2.2.18pre18/19 should ident the CPU fine. A contributed patch
should also report the caches
When I plug it in and modprobe is triggered to load the driver, a script then
runs to feed the device appropriate configuration info. Since the driver only
resets the hardware when it is given the correct configuration, there's no
problem.
Thats another 100 lines of race prone network kernel
Agreed, I was unhappy that the build symlink was added to 2.2 kernels.
Now you need modutils = 2.3.14 for 2.2 kernels :(. But nobody asks
me, I'm just the kernel module.[ch] and modutils maintainer.
Actually they do. I agree that it wants sorting. Im just wondering what the
best approach is
Not to worry, some of us are working with the 'I' guys to do proper P4
detection.
Be careful with the intel patches. The ones I've seen so far tried to call the
cpu 'if86' breaking several tools that do cpu model checking off uname. They
didnt fix the 2GHz CPU limit, they use 'rep nop' in the
Oct 24 00:07:39 gimme kernel: VM: do_try_to_free_pages failed for
postmaster...
2.2.18pre19 should fix this problem if andrea's patch is inside.
if not, you have to patch pre18 with VM-global-2.2.18pre18-7.bz2
if you are from europe you can downlaod it from:
This issue, and all related issues, need to be taken care of for all
speed
changing CPUs from Intel, AMD and Transmeta. Is the answer of "howto
Sensibly configured power saving/speed throttle systems do not change the
frequency at all. The duty cycle is changed and this controls the cpu
On Tue, 07 Nov 2000, Alan Cox wrote:
When I plug it in and modprobe is triggered to load the driver, a script then
runs to feed the device appropriate configuration info. Since the driver only
resets the hardware when it is given the correct configuration, there's no
problem.
Thats
Does anyone know why a Linux ethernet driver might appear to be up
working (that is, no errors, ifconfig says UP, etc), and the board has a
link light on it, but the hub link light is not on and no packets are
transmitted or received? rmmod/insmod of the driver doesn't help.
I have an
works, but only if the new disk is no larger than the disk present at =
boot time (smaller and equal capacity disks work OK).
How do I get Linux to recognise that the media in /dev/hdc has changed?
I imagine your disks are not reporting themselves as 'removable' ? If they
correctly report
Plese add power-saving devices like in notebooks to the list as well.
For example in my notebook the PC speaker loops through the maestro-3e.
The BIOS is initializing the maestro with some sane mixer values but
after
a suspend cycle the pc speaker is compleatly off due to suspension of
the
In the NIC example, I might well want the DHCP client to run whenever I
activate the card. Bringing the NIC up with the old configuration - which, with
dynamic IP addresses, could now include someone else's IP address! - is worse
than useless.
You'll notice the pcmcia subsystem already
On Tue, Nov 07, 2000 at 11:12:00AM -, Joe Woodward wrote:
I am trying to use removable EIDE hard disks
Issuing a BLKRRPART ioctl call immediately after changing the disk works
It should not be necessary to use BLKRRPART.
Does the disk advertise itself as removable?
% dmesg | grep remov
hi all,
just a few reports:
1. zImage in test10 somehow isn't working properly. i have a
zImage sized a bit more than 500kb on my harddrive which hangs at
the loading process (the one showing dots).
i write the image to a floppy, and it boots
Keith Owens [EMAIL PROTECTED] said:
[...]
I have not decided where to save the persistent module parameters. It
could be under /lib/modules/version/persist or it could be under
/var/log or /var/run. I am tending towards /var/run/module_persist, in
any case it will be a modules.conf
On Tue, 07 Nov 2000, Alan Cox wrote:
In the NIC example, I might well want the DHCP client to run whenever I
activate the card. Bringing the NIC up with the old configuration - which, with
dynamic IP addresses, could now include someone else's IP address! - is worse
than useless.
Alan Cox wrote:
In the NIC example, I might well want the DHCP client to run whenever I
activate the card. Bringing the NIC up with the old configuration - which, with
dynamic IP addresses, could now include someone else's IP address! - is worse
than useless.
You'll notice the pcmcia
eth0pegasus
nopersist eth0
post-install eth0 /usr/local/sbin/my-dhcp-stuff
So, in short, this is already done perfectly well in userspace without some
sort of Registry-style kernelside hack?
Thats the idea. Once the rmmod code can read back values the cycle is complete
and the
Linus Torvalds wrote:
On Tue, 7 Nov 2000, Andrew Morton wrote:
Alan Cox wrote:
Even 2.2.x can be fixed to do the wake-one for accept(), if required.
Do we really want to retrofit wake_one to 2.2. I know Im not terribly keen to
try and backport all the mechanism. I think for
Joe Woodward wrote:
I am trying to use removable EIDE hard disks on a Red Hat Linux 6.1
machine, for backup / walknet purposes.
Issuing a BLKRRPART ioctl call immediately after changing the disk
works, but only if the new disk is no larger than the disk present at
boot time (smaller and
On Tue, 7 Nov 2000 12:11:57 + (GMT),
Alan Cox [EMAIL PROTECTED] wrote:
Agreed, I was unhappy that the build symlink was added to 2.2 kernels.
Now you need modutils = 2.3.14 for 2.2 kernels :(. But nobody asks
me, I'm just the kernel module.[ch] and modutils maintainer.
Actually they do.
On Tue, 7 Nov 2000, Keith Owens wrote:
On Mon, 6 Nov 2000 16:31:23 -0500 (EST),
"Richard B. Johnson" [EMAIL PROTECTED] wrote:
However when running, the new kernel 2.4.0-test9, can't be used to
make a usable initrd ram disk. The result being that 2.4.0-test9
can't, itself, build an "initrd"
Horst von Brand [EMAIL PROTECTED] said:
[Yes, I know this is bad taste...]
Keith Owens [EMAIL PROTECTED] said:
[...]
I have not decided where to save the persistent module parameters. It
could be under /lib/modules/version/persist or it could be under
/var/log or /var/run. I am
On Tue, 07 Nov 2000 09:45:42 -0300,
Horst von Brand [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] said:
I have not decided where to save the persistent module parameters. It
could be under /lib/modules/version/persist or it could be under
/var/log or /var/run. I am tending towards
On Tue, 07 Nov 2000 10:30:39 -0300,
Horst von Brand [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] said:
I have not decided where to save the persistent module parameters. It
could be under /lib/modules/version/persist or it could be under
/var/log or /var/run. I am tending
Anyway, version 2 below uses LIFO for the accept() wakeups. This
appears to be a 5%-10% win for Apache. The browsing loop for
exclusive tasks will now pull in cachelines 0 and 2, rather
than the previous 0 and 1.
That makes it much worse for the newest cpus which use 64byte lines (Athlon
Note! This _has_ to be in the / filesystem so it works before mounting the
rest of the stuff (if ever). This would rule out /var, and leave just
/lib/modules/version. Makes me quite unhappy...
The /lib filesystem is likely not writable so /var is the right default.
Any reason it cant be
On Tue, 7 Nov 2000, Richard B. Johnson wrote:
On Tue, 7 Nov 2000, Keith Owens wrote:
On Mon, 6 Nov 2000 16:31:23 -0500 (EST),
"Richard B. Johnson" [EMAIL PROTECTED] wrote:
However when running, the new kernel 2.4.0-test9, can't be used to
make a usable initrd ram disk. The result
On Tue, 7 Nov 2000 01:22:06 +0100, Erik Mouw [EMAIL PROTECTED] wrote:
Hi,
I'm running 2.4.0-test10 on my desktop machine. The system works
perfectly well, but I get some strange PCI messages at boot time. Here
is part it:
I've the same motherboard
part of my syslog:
orac kernel: ALI15X3: IDE
[EMAIL PROTECTED] said:
You will need to use a function pointer hook that the module fills in
when it is loaded. For an example look at devpts_upcall_new and
devpts_upcall_kill in fs/devpts/inode.c. The hooks are resident in
the kernel and are exported so the module can see them. The
Keith Owens [EMAIL PROTECTED] said:
[...]
It makes no sense to allow duplicate module names in the same kernel
tree. "modprobe foo" - which one gets loaded?
Why the tree then?
--
Dr. Horst H. von Brand mailto:[EMAIL PROTECTED]
Departamento de Informatica
On Tue, 07 Nov 2000 11:47:57 -0300,
Horst von Brand [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED] said:
It makes no sense to allow duplicate module names in the same kernel
tree. "modprobe foo" - which one gets loaded?
Why the tree then?
Mainly so you can "modprobe -t net \*" and
Hi everybody,
I have a question for you; How Linux avoids the memory fragmentation in
linked lists?
Windows 9x/NT/2000 (sorry, ;-)), have specific functions (like List_Create,
ExInitializeSListHead, ...) to create generic linked lists but I don't find
something similar in Linux.
Has Linux a generic linked list management API ?
Yes - if you want to use it
linux/list.h
Is the kernel memory fragmentation a solved problem in Linux? (I wish =
Its not a problem you can solve without causing serious performance hits so
we don't solve it. If you want to
On Tue, Nov 07, 2000 at 04:20:20PM +0100, Abel Muñoz Alcaraz wrote:
I have a question for you; How Linux avoids the memory fragmentation in
linked lists?
Windows 9x/NT/2000 (sorry, ;-)), have specific functions (like List_Create,
ExInitializeSListHead, ...) to create generic
On Tue, 07 Nov 2000, Erik Mouw wrote:
Is the kernel memory fragmentation a solved problem in Linux? (I wish it).
My guess is that the slab allocator solves this, but I don't know that
much about the MM.
Linux lists implementation stores linking informations directly inside the
block
From: Ulrich Drepper [EMAIL PROTECTED]
Date: 06 Nov 2000 10:50:37 -0800
Arguably though the bug is in glibc, in that if it's using signals
behinds the scenes, it should have passed SA_RESTART to sigaction.
Why are you talking such a nonsense?
The claim was made that pthreads
Keith Owens [EMAIL PROTECTED]:
Enough people have asked for persistent module storage to at least
justify me writing the code. The design is simple.
MODULE_PARM(var,type) currently defines type as [min[-max]]{b,h,i,l,s}.
For persistent data support, type is now [min[-max]]{b,h,i,l,s}{p},
hi,
why does this program works. when executed, it doesnt
give a segmentation fault. when the program requests
memory, is a standard chunk is allocated irrespective
of the what the user specifies. please explain.
main()
{
char *s;
s = (char*)malloc(0);
On Mon, Nov 06, 2000 at 09:56:49AM +1100, Eyal Lebedinsky wrote:
Alex Buell wrote:
tahallah[alex]:/home/alex ppp-on
tahallah[alex]:/home/alex /usr/sbin/pppd: This system lacks kernel
support for PPP. This could be because the PPP kernel module could not be
loaded, or because PPP
Here's a small patch to allow a user to protect certain PIDs from death-
by-OOM-killer. It uses the proc entry '/proc/sys/vm/oom_protect'; echo the
PIDs to be protected:
echo 1 516 /proc/sys/vm/oom_protect
The idea is that sysadmins can mark some daemon processes as off-limits for
the OOM
"Tim" == Tim Riker [EMAIL PROTECTED] writes:
Tim Alan Cox wrote:
1. There are architectures where some other compiler may do
better optimizations than gcc. I will cite some examples here, no
need to argue
I think we only care about this when they become free software.
Tim This may be
main()
{
char *s;
s = (char*)malloc(0);
strcpy(s,"f");
printf("%s\n",s);
}
I rather suspect that the strcpy() scribbled over malloc()s record keeping
data. However, that memory was in the processes allowed address space so
it didn't SIGSEGV. Now, when you
On Tue, 7 Nov 2000, Abel Muñoz Alcaraz wrote:
my question is about memory fragmentation when I allocate and free a lot of
small memory pieces in a kernel module.
Can it do a memory fragmentation problem?
Can I solve it using 'linux/list.h' API?
Fragmentation is not
I think that is better to allocate a big piece of memory and get the n=
odes
from this buffer with my own memory management functions; Is this corre=
ct?.
See the SLAB interface. It'll do that for you. Kmalloc uses SLAB so will do
similarly sane things
-
To unsubscribe from this list:
Hi,
In the recent 2.2.x I discovered that saa7xxx driver expects norm
to be an int, while struct video_channel defines it as __u16.
This bombs if video_channel has something dirty next to it
on the stack.
Only one file is touched by the patch: drivers/char/buz.c, but
some more code is related.
Umm, so why does this not happen with 2.2.X at all? Also the system is
not really stressed, but I simply do startx, inside an xterm go to
some random source, make -j, wait till the compile is complete and then
switch back to the console - its just that it seems that swapped out
X server or
Hello.
When attempting to boot Linux kernel v2.2.17 from a Compact Flash (CF) device I
am getting the errors shown below. This CF device is in a PCMCIA form factor
and is the Master device on the secondary IDE controller
Before we get to the errors, though, a little background. I can
Actually I just thought about it. Do you DRI running. When you have DRI
enabled you shouldn't VT switch. It is a design flaw in DRI and the
console system :-(. Disable DRI you you will be fine.
The theory behind DRI covers this fine. If its breaking fix the bugs in the
Xserver and DRI code. X
Dunlap, Randy writes:
I'm not following your argument very well. I've read it
and reread it several times.
Does adding a call to usb_init() in init/main.c cause
USB to be init 2 times?
No. As I said elsewhere in this thread, the USB OHCI chip is not accessible
until other board-specific
Linus/Rik,
I might be missing something, but with final load testing of NWFS on
2.4, I occasionally see sendmail fail to accept connections on a live
internet server when low memory conditions are present. I reviewed the
buffer cache, and it does appear that periodically buffer cache pages
get
[EMAIL PROTECTED] said:
No. As I said elsewhere in this thread, the USB OHCI chip is not
accessible until other board-specific initialisation has happened.
This is done via an initcall. Unfortunately, moving usb_init() back
into init/main.c will mean that USB is again initialised before
On Tue, Nov 07, 2000 at 11:22:37AM +0100, Ragnar Hojland Espinosa wrote:
snip
You have a voodoo3 or voodoo5 with X4, and the DRI X4 module loaded.
Or am I wrong?
v3.. bingo :)
Comment out the 'Load "dri"' line from /etc/X11/XF86Config-4, I'm
working on debugging the problems.
From: Russell King [mailto:[EMAIL PROTECTED]]
Dunlap, Randy writes:
I'm not following your argument very well. I've read it
and reread it several times.
Does adding a call to usb_init() in init/main.c cause
USB to be init 2 times?
No. As I said elsewhere in this thread, the USB
[EMAIL PROTECTED] said:
Yes, your proposal is to init only "usbcore" from init/main.c. I
still don't see a need to do this in test10. It's fixed now AFAIK.
Not my proposal. The proposal to which Russell was objecting.
My proposal was to just make the thing work without having to care about
[EMAIL PROTECTED] said:
Yes, your proposal is to init only "usbcore" from init/main.c. I
still don't see a need to do this in test10. It's fixed now AFAIK.
Not my proposal. The proposal to which Russell was objecting.
My proposal was to just make the thing work without having to
Date: Fri, 03 Nov 2000 16:10:50 -0500
From: Jeff Garzik [EMAIL PROTECTED]
Part of that might be that serial doesn't support hotplug without
patching.
Did the patch which I sent out a few weeks ago actually work? I haven't
had time to get back to it, but I now have a cardbus card,
[EMAIL PROTECTED] wrote:
Date: Fri, 03 Nov 2000 16:10:50 -0500
From: Jeff Garzik [EMAIL PROTECTED]
Part of that might be that serial doesn't support hotplug without
patching.
Did the patch which I sent out a few weeks ago actually work? I haven't
had time to get back to
Date: Fri, 03 Nov 2000 17:20:53 -0500
From: Jeff Garzik [EMAIL PROTECTED]
4. Boot Time Failures
* Crashes on boot on some Compaqs ? (may be fixed)
compaq laptops? desktops? or alphas?
Absolutely no idea. This was one I inherited from Alan's list. If Alan
or
a quick correction: I'm running Redhat 7.0 with some updates. sorry
about that.
j.d.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
Anil kumar wrote:
Hi ,
I installed Red Hat 7.0, I am able to find the
linux-2.2.16 in /usr/src
These are the following steps I did to install
kernel 2.4:
cd /usr/src
#rm -r linux
# rm -rf linux-2.2.16
#tar -xvf linux-2.4.0-test9.tar
#cd /usr/src
#ls
linux
Alan,
are you saying that rep;nop is not needed in the spinlocks? (because they
are for P4)
Thanks
Lyle
- Original Message -
From: "Alan Cox" [EMAIL PROTECTED]
To: "Andre Hedrick" [EMAIL PROTECTED]
Cc: "Frank Davis" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Tuesday, November 07, 2000
Mostly driver updates.
With a few notable exceptions: two rather subtle MM race conditions that
happened with SMP and highmem respectively. And the FXCSR and file locking
that was already discussed on the list.
Linus
-
- pre1:
- me: make PCMCIA work even in the
On Tue, 7 Nov 2000, Tim Riker wrote:
Jes,
Hey how's Itanium been lately?
As was mentioned before, there are nonproprietary compilers around as
well that might be good choices. My point is that the ANSI C steering
committee is probably a more balanced forum to determine C syntax than
On Tue, 7 Nov 2000 11:58:48 -0600
[EMAIL PROTECTED] wrote:
Hello.
When attempting to boot Linux kernel v2.2.17 from a Compact Flash (CF) device I
am getting the errors shown below. This CF device is in a PCMCIA form factor
and is the Master device on the secondary IDE controller
Dick Johnson,
earlier in the discussion there was a post of the 'incompatabilities'
that were noted and one of the replies to that listed several c99 tools
available to do the same job with the c99 syntax, so there are at least
some cases where things are done the gcc-only way instead of the
On Tue, Nov 07, 2000 at 01:06:27PM -0800, Linus Torvalds wrote:
Mostly driver updates.
With a few notable exceptions: two rather subtle MM race conditions that
happened with SMP and highmem respectively. And the FXCSR and file locking
that was already discussed on the list.
Shouldn't you
On Tue, 7 Nov 2000, David Lang wrote:
Dick Johnson,
earlier in the discussion there was a post of the 'incompatabilities'
that were noted and one of the replies to that listed several c99 tools
available to do the same job with the c99 syntax, so there are at least
some cases where things
hi!
i have the following very nasty problem.
everytime i execute ipchains -F [rule] my box freezes for 25 minutes!
i run slackware on 2.2.17.
a friend of mine told me that he had a simliar problem and fixed it with
downgrading shlibs.
any suggestion??
thx
michael
below the output of
On Tue, 7 Nov 2000, Anil kumar wrote:
The system hangs after messages:
loading linux..
uncompressing linux, booting linux kernel OK.
The System hangs here.
Please let me know where I am wrong
Hi Anil,
The only serious mistake you did was using test9 kernel when
On Tue, Nov 07, 2000 at 02:19:05PM +1100, Keith Owens wrote:
On Mon, 6 Nov 2000 23:03:44 +0100,
Frank van Maarseveen [EMAIL PROTECTED] wrote:
First a firewall is installed (ppp0). Starting the network (eth0/lo only. ppp0 is
nonexistent at this point) gives the following Oops:
klogd has
On Tue, Nov 07, 2000 at 11:19:37AM -0500, Chris Swiedler wrote:
Here's a small patch to allow a user to protect certain PIDs from death-
by-OOM-killer. It uses the proc entry '/proc/sys/vm/oom_protect'; echo the
PIDs to be protected:
echo 1 516 /proc/sys/vm/oom_protect
Hmm, I'd prefer
are you saying that rep;nop is not needed in the spinlocks? (because they
are for P4)
rep;nop is a magic instruction on the PIV and possibly some PIII series CPUs
[not sure]. As far as I can make out it naps momentarily or until bus
activity thus saving power on spinlocks.
The problem is 'rep
On Tue, 7 Nov 2000 10:01:02 -0600 (CST),
Jesse Pollard [EMAIL PROTECTED] wrote:
Keith Owens [EMAIL PROTECTED]:
Enough people have asked for persistent module storage to at least
justify me writing the code. The design is simple.
MODULE_PARM(var,type) currently defines type as
This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
chipset.
Strange, I've got a dual Katmai (non-Xeon) and notice the same...
CPU0 CPU1
0: 95135438 95720832IO-APIC-edge timer
1: 579101 572402IO-APIC-edge keyboard
2:
On Tue, Nov 07, 2000 at 02:02:23PM -0800, Dr. Kelsey Hudson wrote:
This machine isn't even a Xeon, just a PIII CuMine on a ServerWorks HeIII
chipset.
Strange, I've got a dual Katmai (non-Xeon) and notice the same...
I've just gotten a dual PIII (Coppermine) to my hands. I *think* that
On Tue, 7 Nov 2000, Jan-Benedict Glaw wrote:
[...]
NMI: 190856196 190856196
LOC: 190858464 190858463
...are these two lines okay? I've noticed that as well, but I've not
seen that on UP machines as well...
Yes, please don't worry, it's just the NMI watchdog doing its work.
1 - 100 of 441 matches
Mail list logo
