Jeez David. Although it was insensitive of me to seek succor from the Linux
folks while speaking Microsoft, you needn't be so touchy about it. I
promise I won't commit that sin again, however, at least not in these
circles. (If it makes you feel any better, I'm using a Mac and not a
Wintel.)
Sorry, Tom about the word doc faux pas. I've set out my problem in plain
text below. I got my source from ftp.kernel.org.
Here's my problem:
Problem in compiling linux 2.4.3
Compile error message:
After the compiler message:
gcc D__KERNEL__ -I/home/jeff/kernel/linux/include Wall
On Fri, 20 Apr 2001, Marcelo Tosatti wrote:
Hi,
Argh. Silly.
Well...
Right now we can get a task killed by the OOM killer even if there is a
lot of _unused_ (but allocated) swap space. The reason for that is the
pre allocation of swap.
Practical example (128MB swap, 960MB ram):
#
Manfred H. Winter writes:
Apr 4 02:05:21 marvin pppd[1227]: Plugin /usr/lib/passwordfd.so loaded.
Apr 4 02:05:21 marvin pppd[1227]: pppd 2.4.0 started by mahowi, uid 500
Apr 4 02:05:21 marvin pppd[1227]: Perms of /dev/ttyS0 are ok, no 'mesg n' necce
sary.
Just out of curiosity, what pppd
On Thu, Apr 19, 2001 at 04:29:52PM -0400, Jeff Garzik wrote:
[EMAIL PROTECTED] wrote:
In the long run, it probably makes sense to adjust the algorithms to
allow for non-power-of-two inode sizes,
If you don't mind, does that imply packing inodes across block
boundaries?
No, it means that
"Eric S. Raymond" wrote:
David Woodhouse [EMAIL PROTECTED]:
[EMAIL PROTECTED] said:
I read this as "I haven't fixed the problem because..." not as
"Don't fix the problem." Please be more explicit next time so I won't
step on your toes?
"This is not a problem, please don't
On Thu, Apr 19, 2001 at 10:23:39PM -0400, Alexander Viro wrote:
I'm somewhat concerned about the following: last block of inode table
fragment may have less inodes than the rest. Reason: number of inodes
per group should be a multiple of 8 and with inodes bigger than 128
bytes it may give
On Thu, Apr 19, 2001 at 11:35:40PM -0600, Andreas Dilger wrote:
I don't _think_ that there is a requirement for a multiple-of-8 inodes
per group. OK, looking into mke2fs (actually lib/ext2fs/initialize.c)
it _does_ show that it needs to be a multiple of 8, but I'm not sure
exactly what the
Linus,
The following patch updates drivers/input/keybdev.c so that we can
generate either linux keycodes or ADB keycodes from keyboards that use
the input layer. We now have ADB keyboards and mice using the input
layer as well as USB, so it is very useful to have the flexibility to
choose at
Ion Badulescu wrote:
Well.. Space.c is a dinozaur. However, this is the 2.2 series and no more
surgery will happen on this kernel, at least normally.
Have you tried loading the drivers as modules? You might have more luck
with that approach. Space.c was designed at a time when having 4
On Fri, 20 Apr 2001, Jeff Garzik wrote:
Have you tried loading the drivers as modules? You might have more luck
with that approach. Space.c was designed at a time when having 4 NIC's in
a PC was "pushing the limits"...
2.2.recent has module_init/exit, so you don't even need Space.c.
Jeff Galloway writes:
I sent this report to the people indicated below, whose names I got from the
MAINTAINERS file in the 2.4.3 distribution, but the email address for Mr.
MacKerras is no longer good and Mr. Chastain wrote me back that he is not
following 2.4 issues.
I have left Linuxcare
[Oops, re-sent with a subject line this time...]
Linus,
This patch fixes some bugs in drivers/usb/hid.c. Johannes Erdfelt
(the maintainer) sent it to you previously but it got missed. Could
it go in 2.4.4 please? Here are the comments explaining the patch
that I wrote originally:
The first
Linus,
This patch fixes some bugs in drivers/usb/hid.c. Johannes Erdfelt
(the maintainer) sent it to you previously but it got missed. Could
it go in 2.4.4 please? Here are the comments explaining the patch
that I wrote originally:
The first hunk just fixes some typos in s32ton. For
Ion Badulescu wrote:
On Fri, 20 Apr 2001, Jeff Garzik wrote:
Have you tried loading the drivers as modules? You might have more luck
with that approach. Space.c was designed at a time when having 4 NIC's in
a PC was "pushing the limits"...
2.2.recent has module_init/exit, so you
On Friday 20 April 2001 00:49, J . A . Magallon wrote:
Hi,
Just built 2.4.3-ac10 and got an oops when booting. It tries to detect
the CD and gives the oops.
EIP; c01bfc7c cdrom_get_entry+1c/50 =
This appears to be a known problem. Jens Axboe sent a patch in a different
thread
Fuck! I hate these things early in the morning.
what gets me extremely pissed in the whole business is that i don't
believe that splitting the mailing list is the solution to LVM problems.
Escpecially since we have a number of lusers of lwm at the time being.
I believe sistina is mostly at
Just to follow up on this ...
I am now running 2.4.4pre4 and it seems to be stable. If I reboot the
machine (or simply stop and restart apache) the load avg does go much higher
than I am used to seeing (near 50 for about 5 minutes or so) it does not
hang as previous kernels did. I have the
Linus, Alan,
The patch below does two things:
- It takes out the rest of the compatibility stuff that is no longer
used, and which has the possibility of accessing memory that has
been kfree'd (this could happen if you did a blocking read on a tty
in PPP line discipline, and the tty hangs
In article 9bn90l$anp$[EMAIL PROTECTED],
Linus Torvalds [EMAIL PROTECTED] wrote:
Not that I've tested it myself.
I did a few months ago, it didn't work.
Wichert.
--
/ Generally uninteresting signature - ignore at your
[Giu@Jay Giu]$ eject /mnt/cdmac/ umount: /dev/sr0 is not in the fstab (and
you are not root) eject: unmount of `/dev/sr0' failed
Eject(1) is suid.
I have similar problem with my swim3 floppy drive. Digging deeply I found that
when I make do folowing steps then disk is lost and I have to
[EMAIL PROTECTED] said:
However, I don't think that wishing the world would avoid these
dominant (and very useful) formats is a realistic expectation. It is
certainly not "common sense" to assume as such.
Of course it's not a realistic expectation. There are times when it's a pain
to
Luca Berra wrote:
we have some serous problems here.
[...]
a better lvm (still buggy according to many kernel hackers, but better still),
which does not get into the kernel for communication reasons. (Alan can you help?
there is a lot of stuff that goes in -ac before going to mainstream)
I
On Wednesday 18 April 2001 20:40, Francois Romieu wrote:
Hello,
Oliver Teuber [EMAIL PROTECTED] écrit :
[...]
00:00.0 Host bridge: VIA Technologies, Inc. VT82C691 [Apollo PRO] (rev
06) 00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3 AGP]
00:07.0 ISA bridge: VIA
Linus Torvalds [EMAIL PROTECTED] wrote:
I think Andrea is right. Although this file seems to be entirely
old-fashioned and should never be used, right?
I presume you're talking about "include/asm-i386/rwsem-spin.h"... If so,
Andrea is right, there is a bug in it (repeated a number of times),
[EMAIL PROTECTED] said:
Doesn't this seem a little like the problems occurring with lvm right
now? A separate tree maintained with the maintainers not wanting
others submitting patches that conflict with their particular tree?
It seems that any project should be able to submit any patch
On Fri, Apr 20 2001, Stefan Jaschke wrote:
On Friday 20 April 2001 00:49, J . A . Magallon wrote:
Hi,
Just built 2.4.3-ac10 and got an oops when booting. It tries to detect
the CD and gives the oops.
EIP; c01bfc7c cdrom_get_entry+1c/50 =
This appears to be a known problem.
On Thu, Apr 19 2001, Rik van Riel wrote:
On 19 Apr 2001, Ulrich Drepper wrote:
Jens Axboe [EMAIL PROTECTED] writes:
Does attached patch fix it?
Yes.
Jens, I guess we should submit these patches to Alan and Linus
now. This way we'll get a working LVM again.
Already done
--
On Tue, Apr 10, 2001 at 02:35:52PM +0200, Heusden, Folkert van wrote:
So, I was wondering: isn't it a nice idea to have a switch in the
configuration menu to disable entropy-gathering in the interrupt-routines,
have some simplistic routine (like x'=(x * m + a) % p) which returns a non-
The UP-APIC wouldn't help much since there really aren't other processors
available to share the load.
Hmm, but doesn't the code in 2.4.x improve the hard IRQ signal delivery
even for UP systems with a local APIC table? I have an APIC aware board
but I have only got 1 CPU on it and I currently
Hmm...i guess there is a communication issue here. It sounds like the
message that our ML server was sending was misleading. We were not
rejecting mail because of content. The ML server was rejecting it
because
the address was not subscribed. Our idea was that we don't want spam.
Ehh.. I will bet you $10 USD that if libc allocates the next file
descriptor on the first "malloc()" in user space (in order to use the
semaphores for mm protection), programs _will_ break.
Of course, but this is a result from sloppy coding. In general, open()
can just return anything and
On Sat, Apr 14, 2001 at 03:27:53PM +0100, Alan Cox wrote:
For example the Zyxel 681 SDSL-Router breaks ECN by
stripping 0x80 (ECN Cwnd Reduced) but not 0x40 (ECN Echo)
(TOS bits) on all SYN packets (!).
I complained because of this two times more than a month ago
but they do not even
On Thu, 19 Apr 2001, Alan Cox wrote:
2.4.3-ac10
o Merge Linus 2.4.4pre4
o Reorder frame buffer probes (Geert Uytterhoeven)
These got somewhat mixed. Remove the duplicates:
--- linux-2.4.3-ac10/drivers/video/fbmem.c.orig Fri Apr 20 09:58:50 2001
+++
On Fri, 20 Apr 2001, Roberto Nibali wrote:
Hmm, but doesn't the code in 2.4.x improve the hard IRQ signal delivery
even for UP systems with a local APIC table? I have an APIC aware board
but I have only got 1 CPU on it and I currently need to run 2.2 kernel.
But if you tell me that there is
It is way OT here, but since Alan replied to this, I'll continue this
thread a bit: The interesting bit here, that I don't understand, is - how
in RedHat-7.0, that was released last year, libc is compiled against
2.4.0?... Did they include headers from one of pre / test versions?
Thanks
Guennadi
On Fri, 20 Apr 2001, Jeff Garzik wrote:
Check again. drivers/net builds a .a, not a .o. Trust me, I've tried.
Sure, but if you are patching anyway, it much better to fix that than
hack space.c :)
Well, I remember asking Alan if he'd prefer it done that way, and not
getting a reply back.
Ion Badulescu wrote:
On Fri, 20 Apr 2001, Jeff Garzik wrote:
Check again. drivers/net builds a .a, not a .o. Trust me, I've tried.
Sure, but if you are patching anyway, it much better to fix that than
hack space.c :)
Well, I remember asking Alan if he'd prefer it done that way, and
Argh, I just tried the kernels up to 2.4.4-pre4, not the pre5! Some sleep
and then I will try it!
/P-H
Per-Henrik Persson 0703-68 53 86
[EMAIL PROTECTED]
On Fri, 20 Apr 2001, Jeff Garzik wrote:
Sorry, I was talking about a local patch not a global patch. If a user
must patch their 2.2 kernel to get the starfire driver working anyway,
then adding a change to do s/.a/.o/ on Makefiles would be simple.
People don't need to patch *anything* to
About the benchmark you wrote it looks good measure to me, thanks.
As with all benchmarks, take with one pinch of salt and two of Mindcraft:-)
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
Hi Ion,
I think the UP-APIC support was added primarily to support the NMI oopser
on UP systems. I might be wrong, though.
You're right, at least from the perspective of this patch:
http://www.csd.uu.se/~mikpe/linux/upapic/upapic-2.4.1
You can safely disregard the "early initialization
In ens.mailing-lists.linux-kernel, you wrote:
You're probably even better off just intercepting the fork, turning it
into a clone, and setting the CLONE_PTRACE option. Which (together with
tracing the parent, which you will obviously be doing already in order
to do all this in the first place)
- Original Message -
From: "James Simmons" [EMAIL PROTECTED]
To: "Scott Prader" [EMAIL PROTECTED]
Cc: "Linux Kernel Mailing List" [EMAIL PROTECTED]
Sent: Thursday, April 19, 2001 5:16 PM
Subject: Re: ANNOUNCE New Open Source X server
Thank you. It is true all I want to do is help the
The included patch updates Documentation/filesystems/ext2 to reflect
current information about ext2. It also adds some more information
that people have told me is hard to find in other places (such as a
description of the superblock compatibility flags, file and filesystem
size limits).
I've
Stefan Jaschke [EMAIL PROTECTED] ecrit :
[...]
I don't believe the motherboard or the BIOS have anything to do with, simply
It may give a clue because the machine I wrote this mail from is a
2.4.3 + 2*EtherPower II it looks rather fine (old asus motherbord, BX,
backuped peaceful prod server):
Hi Jeff,
Here is the same starfire.c version I sent earlier, this time diff'ed
against 2.4.4-pre5. It's essentially the version from 2.2.19 plus your
2.4.4-pre5 changes minus the 2.2 compatibility stuff.
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
In article 9bn90l$anp$[EMAIL PROTECTED] you write:
You're probably even better off just intercepting the fork, turning it
into a clone, and setting the CLONE_PTRACE option.
Actually it is not that simple. The child process will be traced by its
father, not the tracing program. The father must
On Thu, Apr 19, 2001 at 04:09:32PM -0400, Jeff Garzik wrote:
AJ Lewis wrote:
Ok, the issue here is that we're trying to get a release out and so anything
that majorly changes the code is getting shunted aside for the moment. It
would be stupid to just add everything that comes in on the
On Thu, Apr 19, 2001 at 09:55:46PM -0500, Jordan wrote:
Bill Nottingham wrote:
J . A . Magallon ([EMAIL PROTECTED]) said:
Can you back out the ide-cd changes Jens did and see if that fixes it ?
Reverted the changes in ide-cd.[hc], and same result.
You want to back out the
Hi,
it seems the epic100 driver broke between 2.4.2 and 2.4.3.
I reloaded the epic100 module with the parameter "debug=6".
Unfortunately, I cannot make much out of the log:
Apr 20 12:47:01 antares kernel: epic100.c:v1.11 1/7/2001 Written by Donald Becker
[EMAIL PROTECTED]
Apr 20 12:47:01
Jeff Galloway writes:
Compiler error message:
fork.c: In function copy_mm:
fork.c:353: fixed or forbidden register 68 (0) was spilled for class
CR0_REGS.
This may be due to a compiler bug or to impossible asm statements or
clauses.
You need a newer gcc, I suspect you have egcs
Brown-paper bag time...
The patch I sent earlier didn't include the accompanying changes to
if_ppp.h and ppp_channel.h. Here they are.
Paul.
diff -urN linux/include/linux/if_ppp.h pmac/include/linux/if_ppp.h
--- linux/include/linux/if_ppp.hTue Mar 28 04:28:55 2000
+++
Hi,
On Fri, Apr 13, 2001 at 04:45:07AM -0400, Dan Maas wrote:
IIRC the problem with implementing asynchronous *disk* I/O in Linux today is
that the filesystem code assumes synchronous I/O operations that block the
whole process/thread. So implementing "real" asynch I/O (without the
overhead
On Fri, 20 Apr 2001, Jeff Garzik wrote:
alas:
http://gtf.org/garzik/kernel/files/patches/2.4/2.4.4/net-version-2.4.4.5.patch.gz
Oh well. Another hour, another patch to be sent out. :-)
I'll deal with CVS tomorrow, when I figure out on which disk I have enough
space for yet another tree. So I
Hi,
When i compiled the following program , (taken from
/usr/src/linux/Documentation/rtc.txt )
(See attached file: rtc2.c)
it gave me the following error:
[root@msatuts1 timer1]# gcc -s -Wall -Wstrict-prototypes rtc2.c -o rtc2
In file included from rtc2.c:17:
On Friday 20 April 2001 12:25, Francois Romieu wrote:
Summary:
Arnd Bergmann:
orig epic100"DMA mapped epic100 (any version)"
(=2.4.0-ac9)
VT8363ok fscked but ok after bios update
Daniel Nofftz:
2.4.2
Stefan Jaschke wrote:
I also noted that there are substantial differences between the original epic100.c at
http://www.scyld.com/network/epic100.html and the version included with 2.4.3.
Who did these changes?
Francois (PCI DMA) and me (everything else). The scyld version does not
support
Steven Cole [EMAIL PROTECTED]:
Axel Boldt wrote:
Eric has worked on Configure.help for some time now and I haven't,
so he will take over official maintenance of that file.
I've also been fixing up Configure.help for a while now, and helped Eric
recently with his huge update patch for
Thanks. I'll try your suggestions and check on the version of my compiler
and binutils.
on 4/20/01 3:57 AM, David Woodhouse at [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] said:
However, I don't think that wishing the world would avoid these
dominant (and very useful) formats is a
Could you try again with 2.4.4pre4 plus the below patch?
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.4/2.4.4pre2/rawio-3
I suppose that 2.4.4-pre4 + rawio-3 patch still has SMP-unsafe
raw i/o code and can cause the same panic I reported.
I think the following
Hello there!!
I am begineer in kernels. I would like to know more about Cache Kernel. Can
anyone tell me some good links for Cache Kernel? I have seen the stanford paper. Can
you suggest something other than that?
Pooja
_
Chat with
[EMAIL PROTECTED] wrote:
Hi,
When i compiled the following program , (taken from
/usr/src/linux/Documentation/rtc.txt )
(See attached file: rtc2.c)
it gave me the following error:
[root@msatuts1 timer1]# gcc -s -Wall -Wstrict-prototypes rtc2.c -o rtc2
In file included from rtc2.c:17:
On Fri, 20 Apr 2001, Andreas Dilger wrote:
The included patch updates Documentation/filesystems/ext2 to reflect
current information about ext2. It also adds some more information
that people have told me is hard to find in other places (such as a
description of the superblock compatibility
On Friday 20 April 2001 13:33, Jeff Garzik wrote:
Here's a suggestion to try: go through epic100.c and write 0x12
unconditionally to MIICfg register. Right now it is conditional: if
(dev-if_port...) out(0x12,ioaddr+MIICfg);
I changed all three such lines. Same behavior as before.
offtopic
On Wed, 18 Apr 2001, Alan Cox wrote:
Well, as this device is already configured by the bios, I just tried
to load it giving the right IO port, and got the following message:
The kernel PnP will deconfigure it
Ah, interesting.
The module parameters are
aha1542=io, irq, busff, dmaspeed
[EMAIL PROTECTED] writes:
Basically in the pmd, it would seem that the current design in 2.4.3 forces
you to have pointers in there. Currently in our source we're using offsets
instead of a 64 bit pointer... this of course saved us from having to alloc 2
contiguous pages in memory.
Nope,
On Wed, 18 Apr 2001, Rafael E. Herrera wrote:
lunix:~# isapnp pnpconfig.txt
Board 1 has Identity 08 0f 6d b9 45 42 15 90 04: ADP1542 Serial No 258849093
[checksum 08]
pnptext:60 -- Fatal - IO range check attempted while device activated
pnptext:60 -- Fatal - Error occurred executing
On Thu, Apr 19, 2001 at 01:17:38PM -0400, Eric S. Raymond wrote:
Go on. Tell me this isn't an error...
CONFIG_ARCH_CLPS7110: arch/arm/kernel/arch.c
CONFIG_ARCH_CLPS711X: arch/arm/Makefile arch/arm/config.in arch/arm/kernel/Makefile
arch/arm/kernel/entry-armv.S arch/arm/kernel/debug-armv.S
All devices should handle having power removed from them. And, all of the
drivers should as well, since that is the only way we're going to get
power management out of legacy devices and other things on the board. This
involves saving the current context on suspend, and reinitializing the
device,
I've attached two slightly different bits of i386 assembly that achieve the
same end, but in slightly different ways. Can some one tell me why Case 1 is
faster than Case 2? Case 1 involves an extra CALL instruction.
* Case 1 has a little wrapper function that saves ECX and EDX before
hello,all.after i create a new logical partition using fdisk or cfdisk
and exit with "w",there always comes report saying that re-read table
failed with error 16:device or resource busy.next time i attempt to mount
the newly created partition it comes error:mount /dev/sdx has wrong major
or
Benjamin Herrenschmidt wrote:
When a device comes out of D3[hot], the equivalent of a soft reset is
performed. From D3[cold], PCI RST# is asserted, and the device must be
completely reinitialized.
Some devices (bad bad HW designers ;) just can't do it themselves. The
Rage M3 requires the
Miles Lane [EMAIL PROTECTED] writes:
Gosh, this seems like a bit of a red herring, IMHO. Do you think the
LKML gets a "lot" of spam? Or, how about the linux-usb-devel or
linux-hotplug-devel lists? None of these lists are moderated and the
occasional spam gets sent to them, but I haven't
hello.one thing i forgot.there are 24 hard disk drives in two scsi channels
made into 3 RAID 5 logical drives on my machine.each consists of 8 drives.
is the way of making the logical drive a maybe factor of the problem?help
is in need greatly.
regards
james
-
To unsubscribe from this list:
fredhat-list red hat linux 7.1 on kernel 2.4?which release?2.4.2 or 2.4.3?
i'v downloaded and compiled a 2.4.3 kernel.i found the version
of header file package is 2.4.0 using rpm -qa|grep kernel.is this
right?where can get linux on 2.4 kernel?
thanks in advance.
xiong zhao
-
To unsubscribe
Some devices (bad bad HW designers ;) just can't do it themselves. The
Rage M3 requires the host to assert PCI RST#, and some motherboards
provide no documented facility for that (it might be possible with Apple
ASICs for example, it's just not documented).
Why should we support such a
I have run across a problem with 2.4.3 on my Dell lattitude CPx. It boots
ok but when it gets to bringing up the pcmcia adapter it gets a spurious
interrupt from the pcmcia socket and then fials to init. This is the last
problem (apart from NFS.lockd) that I am having.
If anyone has any
I am working on a VA Linux server machine model 2240 which came with a
RocketPort serial device.
The first issue is that it doesn't have support for devfs. I have attached a
patch to fix this that I believe to be good (I've done the same thing for
Stallion and Lucent WinModem drivers - it's
Hi,
On Tue, Apr 17, 2001 at 12:21:17PM -0700, H. Peter Anvin wrote:
Certain parts of drivers could get the __pageable prefix or so
(like the __init parts of drivers which get removed) for letting
the paging-code know that it can be discared if memory-pressure
demands it.
VMS does
Alan Cox [EMAIL PROTECTED]:
What is the right procedure for doing changes like this? Is "don't
touch that tree" a permanent condition, or am I going to get a chance
to clean up the global CONFIG_ namespace after your next merge-down?
Feeding arch related stuff to the architecture
What is the right procedure for doing changes like this? Is "don't
touch that tree" a permanent condition, or am I going to get a chance
to clean up the global CONFIG_ namespace after your next merge-down?
Feeding arch related stuff to the architecture maintainers.
That's the main thing
we sent him every single one of those patches individually. and we'd
go insane trying to keep up with what he'd taken and what he'd dropped.
until you've actually tried doing this, please don't attempt to criticise.
Have _you_ tried? If I recall correctly, Linus spoke out against the
Jeff Galloway wrote:
Sorry, Tom about the word doc faux pas. I've set out my problem in plain
text below. I got my source from ftp.kernel.org.
Hi Jeff,
Well that's problem #1. Source from kernel.org for 2.4 tends to not work on
PPC as it has been lagging on important patches and such.
Alan Cox [EMAIL PROTECTED]:
I have for one. Its definitely the wrong approach to bomb Linus with patches
when doing the merge of an architecture. All the architecture folk with in
their own trees for good reason.
On the other hand, Linus has objected to the One-Big-Patch approach in
the past
On Tue, 17 Apr 2001, Oliver Neukum did have cause to say:
load/init/etc. Hardware setup tends to only happen once..)
No they can't. Modules can't be finegrained enough to do this without wasting
more memory due to fragmentation than you'd gain.
Actually, don't they do this -already-? I
On Fri, Apr 20, 2001 at 08:44:35PM +0900, Takanori Kawano wrote:
Could you try again with 2.4.4pre4 plus the below patch?
ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.4/2.4.4pre2/rawio-3
I suppose that 2.4.4-pre4 + rawio-3 patch still has SMP-unsafe
raw i/o
Alan Cox [EMAIL PROTECTED]:
Alan Cox [EMAIL PROTECTED]:
I have for one. Its definitely the wrong approach to bomb Linus
with patches when doing the merge of an architecture. All the
architecture folk with in their own trees for good reason.
On the other hand, Linus has objected to
Alan Cox [EMAIL PROTECTED]:
I have for one. Its definitely the wrong approach to bomb Linus with patches
when doing the merge of an architecture. All the architecture folk with in
their own trees for good reason.
On the other hand, Linus has objected to the One-Big-Patch approach in
OK, so maybe I'm being stupid. But the implication of this talk of separate
port trees and architecture merges is that these guys periodically send big
resync patches to you and Linus.
If that's not what's going on, what is?
People send batches of small fixes to Linus or to me. So for
On Friday 20 April 2001 12:25, Francois Romieu wrote:
What happen's if you compile 2.4.2 epic100 driver in a 2.4.3 tree (I) ?
I would really appreciate if you could give a look at (I).
I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles and works
without
problems.
This
Em Fri, Apr 20, 2001 at 02:07:11PM +0200, Stefan Jaschke escreveu:
offtopic
'A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
[EMAIL PROTECTED]:
unrouteable mail domain "skyld.com"'
/offtopic
Olaf Titz [EMAIL PROTECTED]:
Ehh.. I will bet you $10 USD that if libc allocates the next file
descriptor on the first "malloc()" in user space (in order to use the
semaphores for mm protection), programs _will_ break.
Of course, but this is a result from sloppy coding. In general,
Alan Cox [EMAIL PROTECTED]:
People send batches of small fixes to Linus or to me. So for example
the S/390 folks send me things like 'fix the mm layer to match the
changes in 2.4.3' and 'Update the DASD storage driver'. Each of
which fixes one thing or one set of things and is easy to check
VMS does this. It at least used to have a great tendency to crash
itself, because it swapped out something that was called from a driver
that was called by the swapper -- resulting in deadlock. You need
iron discipline for this to work right in all circumstances.
Actually, VMS doesn't
On Fri, 20 Apr 2001, Xiong Zhao wrote:
fredhat-list red hat linux 7.1 on kernel 2.4?which release?2.4.2 or 2.4.3?
i'v downloaded and compiled a 2.4.3 kernel.i found the version
of header file package is 2.4.0 using rpm -qa|grep kernel.is this
right?where can get linux on 2.4 kernel?
thanks
Stefan Jaschke [EMAIL PROTECTED] ecrit :
[...]
I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles and works
without
problems.
This gives me a workable solution :-)
Thanks for the info.
Now, why do you get so much Receive Queue Empty indications...
--
Ueimor
-
To
I'll continue asking stupid questions, then. Like, under this system how
can either you or the port maintainers maintain a good representation of
how far out of sync they are with the main tree?
diff and read the output.
[bizzare sociopolitical mumble deleted]
well, though. One is the
compared to the complexity that gets added to the kernel. We can keep the
kernel simpler(and faster) without having parts of drivers pageable. But one
more issue is having the page tables pageable...
At the moment we can almost go a stage further - when we are short of memory
we can
The behaviour of CLONE_PTRACE in Linux 2.4.x is different from the
behaviour in 2.2.x. Linus is describing the 2.4.x. behaviour, where
the program that's doing the tracing will get the events instead of
the "real" parent. I believe the 2.2.x behaviour was pretty much
useless, and IIRC that was
1 - 100 of 509 matches
Mail list logo
