I'm using RedHat Linux V2.2.13 and I made the following test:
I launched 10 times the same program with priority 10 of Round Robin
policy (from a shell having priority 20 of FIFO policy). Each program
does an infinite busy loop (while (1)).
One minute later, I
Mornin,
This patch adds error checking to the return value of kmalloc() in
2 places in ide-probe.c. It's against 2.4.5.y
Steve
--- ide-probe.c.origThu Jun 14 14:05:31 2001
+++ ide-probe.c Thu Jun 14 14:15:12 2001
@@ -58,6 +58,11 @@
struct hd_driveid *id;
id =
Hi,
I want to know if the watchdog_timer found in the struct net_device can be
used
as I want ?
Thanks
sebastien person
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Hi,
I have a DVD (IDE, using ide-scsi) with read errors, and when reading it
(UDF-mounted or directly with xine) on the read error the drive clicks,
I have an error in the log and, after a while, the kernel hangs.
Here is the (hand-copied) log:
scsi0: ERROR on channel 0, id 1, lun 0, CDB:
Marco wrote:
Hello, here is my problem :
[1.] 2.4.x kernels sends hda: status timeout: status=0xd0 { Busy }
errors
[2.] I have tried some 2.4.x kernels (2.4.0, 2.4.4, and now
2.4.5, from debs). They all produce the same error message :
Jun 14 13:32:19 debian kernel: hda: status
I see this message few times daily:
PPP: VJ uncompressed error
What does it mean? I searched news archives, HOWTOs, WWW, but only place I found that
string is kernel source.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
I'm looking for a way to do FIBMAP on linux 2.4 without being root, and
I learned from the archive that it's restricted for security reasons,
and that it's obsolete anyway. I found this discussion about a
replacement called FIONDEV:
http://uwsg.iu.edu/hypermail/linux/kernel/9906.1/0817.html
- Received message begins Here -
Cleanup is a nice idea , but Linux should support old hardware and should
not affect them in any way.
Jaswinder.
I agree - and added my comments below.
- Original Message -
From: Daniel [EMAIL PROTECTED]
To: Linux kernel
Tom Gall wrote:
The box that I'm wrestling with, has a setup where each PHB has an
additional id, then each PHB can have up to 256 buses. So when you are
talking to a device, the scheme is phbid, bus, dev etc etc. Pretty easy
really.
I am getting for putting something like this into
David S. Miller wrote:
1) Extending the type bus numbers use inside the kernel.
Basically how most multi-controller platforms work now
is they allocate bus numbers in the 256 bus space as
controllers are probed. If we change the internal type
used by the kernel to u32 or
Message-ID: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Linus,
In pre3, GFP_BUFFER allocations can eat from the emergency memory
reservations in case try_to_free_pages() fails for those allocations in
__alloc_pages().
Here goes the (tested) patch to
At 10:14 AM -0400 2001-06-14, Jeff Garzik wrote:
According to the PCI spec it is -impossible- to have more than 256 buses
on a single hose, so you simply have to implement multiple hoses, just
like Alpha (and Sparc64?) already do. That's how the hardware is forced
to implement it...
That's
Juri Haberland wrote:
You wrote:
I've been running 2.4.5 on my new Dell I8000 without too many
problems. Last night I built -ac13 (on my porch) and booted it
without incident. Later, going inside and re-connecting the AC I
notice that the thing's hung. I play around a bit and
On Wed, Jun 13, 2001 at 08:44:11PM -0400, Daniel wrote:
ISA bus, MCA bus, EISA bus
PCI is the defacto standard. Get rid of CONFIG_BLK_DEV_ISAPNP,
CONFIG_ISAPNP, etc
ISA, MCA, EISA device drivers
If support for the buses is gone, there's no point in supporting devices for
these buses.
The file _could_ be a temporary file, which gets removed before
we'd get around to writing it to disk. Sure, the chances of this
happening with a single file are close to zero, but having 100MB
from 200 different temp files on a shell server isn't unreasonable
to expect.
Daniel This still
Jonathan Lundell wrote:
At 10:14 AM -0400 2001-06-14, Jeff Garzik wrote:
According to the PCI spec it is -impossible- to have more than 256 buses
on a single hose, so you simply have to implement multiple hoses, just
like Alpha (and Sparc64?) already do. That's how the hardware is forced
You wrote:
Juri Haberland wrote:
Ok, I just tried that and my i8000 locked up as well. No problems with
2.4.5 as well. I have also another problem:
Running with -ac13 it doesn't poweroff properly - but it did running
2.4.5. Sometimes it just stops where it should poweroff and locks hard,
Firstly, I apologize for the lack of detail that this report contains,
but I have not been able to gather any detail so far. The crash seems
to occur when I'm using tcpdump and iptraf at the same time, but not
as soon as I run them - it takes a good couple of hours it seems. The
box crashed once
On Thursday 14 June 2001 10:34, Alexander Viro wrote:
On Thu, 14 Jun 2001, Daniel Phillips wrote:
This sounds a lot like apt-get, doesn't it?
Folks, RTFFAQ, please. URL is attached to the end of each posting.
The FAQ blesses the idea of people setting up incremental download services,
[EMAIL PROTECTED] wrote:
Firstly, I apologize for the lack of detail that this report contains,
but I have not been able to gather any detail so far. The crash seems
to occur when I'm using tcpdump and iptraf at the same time, but not
as soon as I run them - it takes a good couple of hours it
A PIII with 96MB ram became extremely sluggish inside X11. I managed
to terminate the X server, bringing the system in a useful state
again. While the system was completely quiet (no X server) I noticed
that a lot of both memory and swap was being used for no appearent reason:
# free
Kernel community,
Sorry for intrusion, but I could use some guidance and/or direction in
tracking
down the source of a problem. None of the messages I have seen in the
archives quite seem to match this problem (if there is one please let me
know). I am looking for where or how to dig (deeper)
What kernel are you using?? I used to get it after I switced from a
Linux-supported winmodem to a hardware modem, but the messages are now
mysteriously absent from me logs. If you're running something prior to
2.4.5, I'd say it was fixed there. Also, it could've been fixed in
Alan's tree; I'm
I've seen the exact same problem when trying to compile for sparc. I
might try and fix it myself, as it doesn't seemed to be fixed in the vger
cvs tree, or any other patch for that matter.
Regards,
Aaron
On Tue, 29 May 2001, John wrote:
Sorry if this is a repeat. Can't find anything on
I'm read Bovet's Understand the Linux Kernel
and looked at the assembly routine setup_idt...
I noticed the assembly has SYMBOL_NAME
(its all over the place).
This is define in include/linux/linkage.h
to just:
#define SYMBOL_NAME(X) X
(this wasn't in Bovet's book).
What's the purpose?
[EMAIL PROTECTED] wrote:
SUBJECT:
Lockup in 2.4.2 kernel ADSL PCI card ATM driver module
DRIVER RESULTS:
Works fine in 2.4.0 kernel.
Locks up system (no messages/oops/etc.) in 2.4.2-2 kernel (rh 7.1).
Locks up system (no messages/oops/etc.) in 2.4.2 kernel (w/ or w/o kgdb).
Locks up
What kind of network card, and what network driver?
I've got 3 NICs:
ne.c:v1.10 9/23/94 Donald Becker ([EMAIL PROTECTED])
Last modified Nov 1, 2000 by Paul Gortmaker
NE*000 ethercard probe at 0x300: 00 c0 df 64 7b d5
eth0: NE2000 found at 0x300, using IRQ 9.
NE*000 ethercard probe at 0x340: 00
On 12 Jun 2001 12:20:58 -0700, Ken Brownfield wrote:
Or you could keep your hardware and try the Intel driver, which seems to
work fine. It only works as a module, though. This might also help
narrow the issue to a driver vs. card vs. mobo/BIOS/IRQ/APIC/etc issue.
I did that, and it seems
On Thursday 14 June 2001 14:59, Marcelo Tosatti wrote:
--- linux/mm/page_alloc.c.origThu Jun 14 11:00:14 2001
+++ linux/mm/page_alloc.c Thu Jun 14 11:32:56 2001
@@ -453,6 +453,12 @@
int progress = try_to_free_pages(gfp_mask);
There are a number of changes in kernel API visisble to userspace that
are unregistered in 2.4 mainline. I recommend to merge them ASAP to
avoid generating collisions across different versions of the kernel.
I'll attach here a number of patches that should make us to return in
sync. They must be
Hi *!
I got this Oops at unmounting a already renamed NFS source.
The umount got a SEGFAULT.
I compiled my 2.4.5 with 2.95.4 20010319 (Debian prerelease).
Regards,
-Gregor
ksymoops 2.4.1 on i686 2.4.5. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules
Ok here are my only 2cents, I use some of this hardware that this clean up
would kill, I dont like that thought, and my brand spanking new 1.2ghz
athalon has a single ISA slot and on board parallel / serial ports all of
which are in use so maybee those should be kept, I however I do agree that a
On Thu, Jun 14, 2001 at 07:12:19PM +0200, Andrea Arcangeli wrote:
is not definitive yet, O_DIRECTIO of tru64 is our O_NOFOLLOW so we're
just screwed as we just need a wrapper anyways to make complex programs like
I just got the email from Richard that he prefers to break O_NOFOLLOW
than to
On Thursday 14 June 2001 08:14, David Luyer wrote:
Well, I'm actually looking at the 2nd idea I mentioned in my e-mail -- a
very small kernel package which has a config script, a list of config
options and the files they depend on and an appropriately tagged CVS tree
which can then be used
Daniel Phillips writes:
On Thursday 14 June 2001 10:34, Alexander Viro wrote:
On Thu, 14 Jun 2001, Daniel Phillips wrote:
This sounds a lot like apt-get, doesn't it?
Folks, RTFFAQ, please. URL is attached to the end of each posting.
The FAQ blesses the idea of people setting up
On Thu, Jun 14, 2001 at 07:16:34PM +0200, Andrea Arcangeli wrote:
I just got the email from Richard that he prefers to break O_NOFOLLOW
Richard are you sure we can break O_NOFOLLOW and still expect the machine to
boot?
./elf/cache.c: fd = open (temp_name, O_CREAT|O_WRONLY|O_TRUNC|O_NOFOLLOW,
I __finally__ got back on the list. They finally fixed the
company firewall!
During my absence, I had the chance to look at some SMP code
because of a performance problem (a few microseconds out of
spec on a 130 MHz embedded system) and I have a question about
the current spin-locks.
Andrea Arcangeli wrote:
Here the third, it registers the tux syscall at for the alpha so other
people won't use such same syscall for something else (I didn't remove
the #ifdefs since they don't hurt as they're undefined in mainline).
diff -urN ref/arch/alpha/kernel/entry.S
On Thu, Jun 14, 2001 at 07:21:22PM +0200, Andrea Arcangeli wrote:
Richard are you sure we can break O_NOFOLLOW and still expect the machine to
boot?
[uses in glibc]
Yes, I saw those. What is the effect of O_NOFOLLOW? To not
follow symbolic links when opening the file. If you open a
regular
Would it be possible to maintain a dirty-rate count
for the dirty buffers?
For example, we it is possible to figure an approximate
disk subsystem speed from most of the given information.
Disk speed is difficult. I may enable and disable swap on any number of
...
You may be able
I have an athlon system with a iwill kk266 motherboard (via kt133A). I
have a linksys 10/100 PCI ethernet card with wake on lan capabilities.
Anyway, when I shut the PC down it turns off, but refuses to stay off.
Within a minute or two, it turns itself on again. If i run over and
turn it off
Marty Leisner wrote:
I'm read Bovet's Understand the Linux Kernel
and looked at the assembly routine setup_idt...
I noticed the assembly has SYMBOL_NAME
(its all over the place).
This is define in include/linux/linkage.h
to just:
#define SYMBOL_NAME(X) X
(this wasn't in Bovet's
On Thu, Jun 14, 2001 at 01:26:05PM -0400, Richard B. Johnson wrote:
Question 2: What is the purpose of the code sequence, repz nop
Puts iP4 into low power mode.
Regards,
--
Kurt Garloff [EMAIL PROTECTED] Eindhoven, NL
GPG key: See mail header, key servers
Due to a catastrophic fan short-circuit, I was forced to exchange my
686A-based motherboard for a 686B. Bad idea!
The 686A MB (MSI-6330 aka K7T-Pro) worked perfectly well: no crashes,
UDMA 66. It accepted Athlon-optimized kernels.
The 686B MB (K7T-Lite) crashed if used with DMA (any kind -
On Thu, Jun 14, 2001 at 01:25:10PM -0400, Jeff Garzik wrote:
They don't hurt but it's also a bad precedent - you don't want to add a
ton of CONFIG_xxx to the Linus tree for stuff outside the Linus tree.
disagree with this patch.
If tux will ever be merged into mainline eventually I don't
On Thu, Jun 14, 2001 at 10:32:49AM -0700, Richard Henderson wrote:
within glibc, and (2) making these accesses slower since they
will be considered O_DIRECT after the change.
and then read/write will return -EINVAL which is life-threatening.
O_DIRECT like rawio via /dev/raw imposes special
Andrea Arcangeli wrote:
On Thu, Jun 14, 2001 at 01:25:10PM -0400, Jeff Garzik wrote:
They don't hurt but it's also a bad precedent - you don't want to add a
ton of CONFIG_xxx to the Linus tree for stuff outside the Linus tree.
disagree with this patch.
If tux will ever be merged into
On Thu, Jun 14, 2001 at 01:52:44PM -0400, Jeff Garzik wrote:
You're missing the point -- it's a bad precedent.
How many kernel forks and patches exist out there on the net?
How many of them are applied to 90% of kernels running out there? How
many of them will get merged eventually? How many
On 2.4.4, with the aic7xxx driver loaded, if a test unit ready
command (0) is sent to a device which is not loaded via the
generic scsi interface, it results in the driver rolling out
of memory, even though sg may have open file handles for
/dev/sgX, etc. active.
Jeff
-
To unsubscribe
On Thursday 14 June 2001 12:44 pm, David Monniaux wrote:
So we have two kinds of problems:
- *certain* 686B motherboards crash if used with an Athlon kernel
(and it does not depend on the compiler options, rather on hand-made
Athlon optimizations)
Abit KT7A, kernel oops right after
David Monniaux wrote:
I replaced this mobo+Duron with an ASUS A7V133+Athlon, which
work perfectly well.
Athlon-optimized kernel, UDMA100, no problem whatsoever.
Which is odd, because that's exactly my combination (ASUS A7V133 +
Athlon), and I get crashes with DMA on anything from 2.4.3-ac7
On Thu, 14 Jun 2001, Richard Henderson wrote:
Yes, I saw those. What is the effect of O_NOFOLLOW? To not
follow symbolic links when opening the file. If you open a
regular file, in effect nothing happens. Moreover, if these
opens were not finding files now, the system wouldn't work.
Hi,
For this scenario consider a set of 4 page frames.
Frames 0 and 2 are used while frames 1 and 3 are free.
The question is would the bitmap for order 1 be a 1 or 0 for this scenario.
I am not on the list so please cc me on your response.
Thanks in advance.
Ramil J.Santamaria
Toshiba
On Thu, Jun 14, 2001 at 07:47:57PM +0200, Andrea Arcangeli wrote:
On Thu, Jun 14, 2001 at 10:32:49AM -0700, Richard Henderson wrote:
within glibc, and (2) making these accesses slower since they
will be considered O_DIRECT after the change.
and then read/write will return -EINVAL which is
On Thu, Jun 14, 2001 at 07:47:57PM +0200, Andrea Arcangeli wrote:
On Thu, Jun 14, 2001 at 10:32:49AM -0700, Richard Henderson wrote:
within glibc, and (2) making these accesses slower since they
will be considered O_DIRECT after the change.
and then read/write will return -EINVAL which is
On Thursday 14 June 2001 17:10, John Stoffel wrote:
The file _could_ be a temporary file, which gets removed before
we'd get around to writing it to disk. Sure, the chances of this
happening with a single file are close to zero, but having 100MB
from 200 different temp files on a shell
Some days ago I posted patch to introduce KDKBDREP ioctl
to i386 keyboard routines. KDKBDREP is defined in linux/kd.h
but now he is used only on m68k. In sparc architectures is used
KIOCSRATE, on i386 -- user-space utility kbdrate and I know
nothing about others. It seems to be better to use one
Folks,
I checked 2.4.x source code but did not find any code for IPsec. Does
anyone know that current or latest Linux support IPsec? Or does anyone know
who is working on this ipv6 issue?
Many thanks!
Eddie
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
I just noticed that file rc.hints mentioned in modules.txt
does not exist anywhere in the module utilities package.
I looked in modutils-2.4.2 as documented in Changes.
If rc.hints really doesn't exist, perhaps the sentence in
parenthesis should be removed, since it doesn't assist the reader.
Alex,
Looking at the back of a Linksys EtherFast 10/100 manual I happen to have,
they describe two different remote wake-up events, Magic Packet and Link
Change. The first one is pretty obvious and is probably not related to
your problems, but the second one may be. The manual states Link
Yo Eddie!
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote:
I checked 2.4.x source code but did not find any code for IPsec. Does
anyone know that current or latest Linux support IPsec? Or does anyone know
who is working on this ipv6 issue?
www.freeswan.org
RGDS
GARY
On Wed, Jun 13, 2001 at 01:55:00PM +0200, Miquel Colom Piza wrote:
I should add 1 giga of RAM to a machine which already has 1 giga. I know
I will have to configure bigmem support in the kernel (2.2.19). I would
like to know if this option is considered really stable and tested or I
can
Diff between 2.4.6pre2aa2 and 2.4.6pre3aa1:
-
Moved on top of 2.4.6pre3.
Only in 2.4.6pre2aa2: 00_alpha-compile-swapon-1
Only in 2.4.6pre2aa2: 00_x86-entry.S-fix-1
Merged in 2.4.6pre3.
Only in 2.4.6pre3aa1:
On Wed, 13 Jun 2001, Daniel wrote:
i386, i486
The Pentium processor has been around since 1995. Support for these older
processors should go so we can focus on optimizations for the pentium and
better processors.
[SNIP]
Boy, if this isn't a troll, I don't know what is. Obviously
someone
On Wed, 13 Jun 2001, Colonel wrote:
I really think doing a clean up is worthwhile. Maybe while looking for stuff
You left out all the old non-IDE CDROM drives.
And also UP systems. I've got 2 SMP boxes here now. Why not
remove support for any system with less than 2 processors? ;o)
I'll
Now, if the NIC were to integrate with OpenSSL and offload some of THAT
donkey work... Just offloading DES isn't terribly useful, as Pavel says:
apart from anything else, DES is a bit elderly now - SSH using 3DES or
Blowfish etc... How dedicated is this card? Could it be used to offload
bert hubert wrote:
stuff deleted
I see lots of people only using:
pthread_create()/pthread_join()
mutex_lock/unlock
sem_post/sem_wait
no signals
My gut feeling is that you could implement this subset in a way that is both
fast and right - although it
David S. Miller wrote:
Jeff Garzik writes:
Thinking a bit more independently of bus type, and with an eye toward's
2.5's s/pci_dev/device/ and s/pci_driver/driver/, would it be useful to
go ahead and codify the concept of PCI domains into a more generic
concept of bus tree numbers?
Jeff Garzik writes:
ok with me. would bus #0 be the system or root bus? that would be my
preference, in a tiered system like this.
Bus 0 is controller 0, of whatever bus type that happens to be.
If we want to do something special we could create something
like /proc/bus/root or whatever,
On Thursday 14 June 2001 10:47, Daniel Phillips wrote:
On Thursday 14 June 2001 05:16, Rik van Riel wrote:
On Wed, 13 Jun 2001, Tom Sightler wrote:
Quoting Rik van Riel [EMAIL PROTECTED]:
After the initial burst, the system should stabilise,
starting the writeout of pages before we
Roger It does if you are running on a laptop. Then you do not want
Roger the pages go out all the time. Disk has gone too sleep, needs
Roger to start to write a few pages, stays idle for a while, goes to
Roger sleep, a few more pages, ...
That could be handled by a metric which says if the disk
Holger Lubitz wrote:
D. Stimits proclaimed:
down to 1.44 MB. But then it would also have to be self-extracting,
which complicates it, so I'm wondering how effective this current
compression is, and if a more bzip2-like system would be beneficial as
kernels get larger?
bzip2 has
Hi,
Wait a minute...
Spinlocks on a embedded system? Is it _really_ SMP?
What kind of performance problem do you have?
My guess, since you are mentioning spin locks, is that you are
having a latency problem - RT process does not execute/start
quickly enough?
If that is the case you should
Guus, there isn't a really official version of it..
At http://pdsf.nersc.gov/linux/ifenslave.c is the last version I
produced, that works with bonding in v2.2 and v2.4 kernels.
Please note; I'm currently bound up in DOE/LBNL contract issues, that
prevent any work on any GPL code on DOE/LBNL
On Thu, Jun 14, 2001 at 01:33:53PM +0200, Anders Peter Fugmann wrote:
Great to hear, but I cannot find anything that backs it up.
I really want to see the final RFC.
Perhaps you could send me an URL pointing to it?
Usually takes a few days until the RFC editor will announce and
publish the
On Thu, 14 Jun 2001, Roger Larsson wrote:
Hi,
Wait a minute...
Spinlocks on a embedded system? Is it _really_ SMP?
The embedded system is not SMP. However, there is definite
advantage to using an unmodified kernel that may/may-not
have been compiled for SMP. Of course spin-locks are
I'm attempting to write a piece of code that will validate the physical ethernet
link from a NIC to the nearest router/hub/switch. What I'd like to do is to
send out an ethernet packet addressed to me, bounce it off the
hub/switch/router, and then read it back in. This is all at the ethernet
On Thu, 14 Jun 2001, Brent D. Norris wrote:
Now, if the NIC were to integrate with OpenSSL and offload some of THAT
donkey work... Just offloading DES isn't terribly useful, as Pavel says:
apart from anything else, DES is a bit elderly now - SSH using 3DES or
Blowfish etc... How
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
2. A ping -f -s 64589 to a machine running kernel 2.2.19 results in 0%
packet loss. By incrementing the packetsize by one ping -f -s 64590 or
higher,
So what is the truth to the rumors 3com was throwing around about the
linux driver with ipsec support?
Nick
On Thu, 14 Jun 2001, Martin Moerman wrote:
On Thu, 14 Jun 2001, Brent D. Norris wrote:
Now, if the NIC were to integrate with OpenSSL and offload some of THAT
donkey
IPsec support will be binary only.
-Kip
On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote:
So what is the truth to the rumors 3com was throwing around about the
linux driver with ipsec support?
Nick
On Thu, 14 Jun 2001, Martin Moerman wrote:
On Thu, 14 Jun 2001, Brent D.
Erm, that is going to be a problem. Crypto benifits more from open source
than any other market segment, and binary only drivers for linux are not
the way to go. I guess I need to get rid of my 5-10 3cr990s and replace
them with someone else's product?
Nick
On Thu, 14 Jun 2001, Kip
On Thursday, 14 June 2001, at 12:30:02 -0600,
[EMAIL PROTECTED] wrote:
Folks,
I checked 2.4.x source code but did not find any code for IPsec. Does
anyone know that current or latest Linux support IPsec? Or does anyone know
who is working on this ipv6 issue?
Check FreeS/WAN
Rik There's another issue. If dirty data is written out in small
Rik bunches, that means we have to write out the dirty data more
Rik often.
What do you consider a small bunch? 32k? 1Mb? 1% of buffer space?
I don't see how delaying writes until the buffer is almost full really
helps us. As
In article [EMAIL PROTECTED],
Stelian Pop [EMAIL PROTECTED] wrote:
Well, not quite... I've had several X lockups while using the YUV
acceleration code. Let's say one lockup per half an hour.
Strange. I've watched DVD's etc. Maybe it's not the Xv code, but your
camera code?
Even the
On Thursday 14 June 2001 23:05, you wrote:
On Thu, 14 Jun 2001, Roger Larsson wrote:
Hi,
Wait a minute...
Spinlocks on a embedded system? Is it _really_ SMP?
The embedded system is not SMP. However, there is definite
advantage to using an unmodified kernel that may/may-not
have
In article [EMAIL PROTECTED],
Alan Cox [EMAIL PROTECTED] wrote:
Use pre2. Linus applied a patch that changed the PCI power management stuff
and broke all the drivers.
It shouldn't have broken anything. The warning happens, but the
function call ends up doing the same thing as it used to - old
So it would seem. Here is the polite message I received in response my
inquiry regarding the crypto interface to the card:
Thank you for your inquiry. We do not offer the
technical spec;s for the IPSec
features of this NIC, due to the intellectual
property-heavy nature of this
product.
On Thu, 14 Jun 2001, John Stoffel wrote:
Rik There's another issue. If dirty data is written out in small
Rik bunches, that means we have to write out the dirty data more
Rik often.
What do you consider a small bunch? 32k? 1Mb? 1% of buffer space?
I don't see how delaying writes until
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
In terms of going through the code audit almost all the sound drivers still
need fixing to lock against format changes during a
Hello,
I have implemented thread pooling (with an environment variable
where I can give the number of threads to be created). Results:
1. Linux, no change in the times (not under 2.2.x or 2.4)
2. SGI/Solaris/OSF/1: times decrease when the number of threads matched
the number of processors
Hello,
I have implemented thread pooling (with an environment variable
where I can give the number of threads to be created). Results:
1. Linux, no change in the times (not under 2.2.x or 2.4)
[snip]
I am now pretty much inclined to believe that it is either a) hardware
issue (someone
On Thu, Jun 14, 2001 at 04:42:29PM -0600, [EMAIL PROTECTED] wrote:
2. The main thread sets up the data (which are global) and then signals
that there is work to be done on the same condition variable. The first
thread to get awaken takes the work. the remaining threads keep waiting.
For
On Thursday, 14 June 2001, at 14:17:11 -0700,
[EMAIL PROTECTED] wrote:
1. When pinging a machine using kernel 2.2.19 I consistently get an 80%
packet loss when doing a ping -f with a packet size of 64590 or higher.
What happens here is (under kernel 2.2.19):
ping -f -s 49092 localhost --
Christopher Friesen wrote:
I'm attempting to write a piece of code that will validate the physical ethernet
link from a NIC to the nearest router/hub/switch. What I'd like to do is to
send out an ethernet packet addressed to me, bounce it off the
hub/switch/router, and then read it back
Odds are it's a raw socket receive buffer issue. Stock pings only ask for
a ~96k socket buffer, which means that they can only hold one ~64k packet
at a time. So, if you're ever slow grabbing packets out of the buffer,
you're going to drop traffic.
You can fix this by upping the socket buffer
On Wednesday June 13, [EMAIL PROTECTED] wrote:
I might just do that first step (find_ino) and offer it as as an
experimental patch to the growing number of people who have asked for
nfs exporting of FAT filesystems, and see how reliable it is in
practice.
Following is a patch against
Dieter Nützel wrote:
Hello Alan,
I see 4.29 GB under shm with your latest try.
something wrong?
total:used:free: shared: buffers: cached:
Mem: 1053483008 431419392 622063616 122880 24387584 260923392
Swap: 3947642880 394764288
MemTotal: 1028792 kB
Hello Alan,
I see 4.29 GB under shm with your latest try.
something wrong?
Regards,
Dieter
SunWave1cat /proc/meminfo
total:used:free: shared: buffers: cached:
Mem: 327802880 322592768 5210112 4294184960 8417280 253640704
Swap: 1052794880 95768576 957026304
Kurt Garloff wrote:
On Thu, Jun 14, 2001 at 01:26:05PM -0400, Richard B. Johnson wrote:
Question 2: What is the purpose of the code sequence, repz nop
Puts iP4 into low power mode.
Umm, slightly more accurate would be to say that it makes the P4 processor
wait before resuming the loop to
201 - 300 of 323 matches
Mail list logo
