Rik van Riel <[EMAIL PROTECTED]> writes:
> On Wed, 21 Mar 2001, Patrick O'Rourke wrote:
>
> > Since the system will panic if the init process is chosen by
> > the OOM killer, the following patch prevents select_bad_process()
> > from picking init.
>
> One question ... has the OOM killer ever se
On Wed, Mar 21, 2001 at 09:13:05AM -0800, James Simmons wrote:
> >Isn't that a job of the device drivers?
> Well most of those resources are present on every PC motherboard.
I still can't see a reason for allocating it before the device drivers
could do that.
Any suggestions? Anyone?
> This wi
On Wed, 21 Mar 2001, Linus Torvalds wrote:
> diff -u --recursive --new-file pre6/linux/mm/memory.c linux/mm/memory.c
> --- pre6/linux/mm/memory.cTue Mar 20 23:13:03 2001
> +++ linux/mm/memory.c Wed Mar 21 22:21:27 2001
> @@ -1031,18 +1031,20 @@
> struct vm_area_struct * vma, unsigned l
On 21 Mar 2001, Kevin Buhr wrote:
> Mike Galbraith <[EMAIL PROTECTED]> writes:
> >
> > Yes. I'm so used to UP numbers I didn't think. I saw user larger than
> > real on my UP box yesterday during some testing, and then seeing this
> > post... oops.
>
> Okay, so you see "user > real" on a UP box
Hi
I have a question related to forwarding information base(FIB).
Depending upon destination IP address a packet can be
a) for this machine
b) for a machine to which this machine is directly connected
c) for a machine to which this machine is not directly connected.
Does FIB contain the
On Wed, Mar 21, 2001 at 09:27:47PM -0800, Dr. Kelsey Hudson wrote:
> I've got a SmartCACHE IV...This driver seems not to recognize it.
It is not supposed to. For DPT .* I - IV use CONFIG_SCSI_EATA
'EATA ISA/EISA/PCI (DPT and generic EATA/DMA-compliant boards)'
option.
--
marko
-
To unsubscri
Jens Axboe wrote:
> You don't need a slow disk, it's trivial to provoke 256 sector sized
> request on even the fastest disk available. People hit it all the time,
> just with working drives...
Here is an update on the 255 vs 256 IDE issue. As Jens said, if it
screws up on every 256, then I shou
Hello lkml,
I have two machines AlphaServers ES40
machine 1 with 4 Gbytes of RAM
machine 2 with 8 Gbytes of RAM
These two machines work perfectly with Tru64, The RAM is ok
on both of these machines.
1) I recompiled kernel 2.2.19pre17aa1
==> The two machines boot well, but are limited to 2 Gb
No luck with either William's or Agus's suggestions. Still 11 MB/s
transfer rate, dma enabled or not. The motherboard is a newer IWILL.
dmesg outputs:
Uniform Multi-Platform E-IDE driver Revision: 6.30
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE contr
Andrzej Krzysztofowicz wrote:
>
> Hi,
> It looks like a not fully merged patch from Alan's tree:
>
> drivers/net/net.o: In function `pcnet32_open':
> drivers/net/net.o(.text+0x3bb9): undefined reference to `is_valid_ether_addr'
> drivers/net/net.o: In function `pcnet32_probe1':
> drivers/net/n
On 22 Mar 2001, Eric W. Biederman wrote:
> Is there ever a case where killing init is the right thing to do? My
> impression is that if init is selected the whole machine dies. If you
> can kill init and still have a machine that mostly works, then I guess
> it makes some sense not to kill it.
>
And for the record:
"hdparm -d1 -t -X69 /dev/hda" gives:
/dev/hda:
setting using_dma to 1 (on)
setting xfermode to 69 (UltraDMA mode5)
using_dma= 1 (on)
Timing buffered disk reads: 64 MB in 5.64 seconds = 11.35 MB/sec
--
%%
Tomasz Sterna wrote:
>
> On Wed, Mar 21, 2001 at 09:13:05AM -0800, James Simmons wrote:
> > >Isn't that a job of the device drivers?
> > Well most of those resources are present on every PC motherboard.
>
> I still can't see a reason for allocating it before the device drivers
> could do that.
>
> Ok, the question is: does anyone know a place on the web where I can find
> specifications of ISA-slots? I need to know what is supposed to be
connected
> to
> the pins (1, 2, 6, etc.)
AO> It is supposed to do that!
Yes, I guess so!
AO> That sounds like the card that came with an old DOS debug
hello,
It is for all the three cases.
It also contains for the case in which it does not match any one of them
that is the default entry.
Warm Regards,
Nomit Kalidhar,
Infosys-West, Pune.
ph 925-32801
Extn. 2293
Haven't seen a post for sometime from the usually prolific Mr Cox.
What's the gossip?
-
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
> Since the system will panic if the init process is chosen by
> the OOM killer, the following patch prevents select_bad_process()
> from picking init.
Hmmm, wouldn't it be nice to make this all configurable? Like; have
some list of PIDs that can be killed?
I would hate it the daemon that checks
alterity <[EMAIL PROTECTED]> wrote:
>Haven't seen a post for sometime from the usually prolific Mr Cox.
>What's the gossip?
Don't worry, missed him as well, but he's been posting
comments since yesterday. His personal webpage hasn't
been updated since 13th of this month though...
Danny
--
---
Hi !
I'm changing the ADB bus reset & probe code to be in a kernel threads
that is created when a bus reset is triggered and that dies of it's own
death.
Everything is fine when the bus reset is triggered during kernel init as
my thread is a child of init. However, when created as a result of a
On Wed, Mar 21, 2001 at 08:48:54PM -0300, Rik van Riel wrote:
> On Wed, 21 Mar 2001, Patrick O'Rourke wrote:
> > Since the system will panic if the init process is chosen by
> > the OOM killer, the following patch prevents select_bad_process()
> > from picking init.
There is a dozen other proces
> here http://www.eurocomla.com/m805lr.htm) I have to get it working to
> stream our meetings with realserver. as such I cannot use the new 2.4
> kernels with it since Realserver won't work with them. I am having
That seems strange. What is realserver failing with ?
-
To unsubscribe from this
Alan,
patch against -ac20 fixes a few things:
- console.c: reviewed and commented locking rules
- tioclinux(): set_selection() was racy wrt console writes, which
causes mouse droppings on the screen when using gpm. It was
always SMP racy. Removing the console_lock make it UP-racy.
Now f
On Wed, Mar 21, 2001 at 11:41:33PM +, Alan Cox wrote:
> > > handle the situation with 2 different CPUs (AMP = Assymmetric
> > > multiprocessing ;-) correctly.
> >
> > "correctly". Intel doesn't support this (mis)configuration:
> > especially with different steppings, not to mention models.
I have a question regarding a busy box I recently updated to
'2.4.2-ac20'. It has been running for several hours without any real
problems until I started getting 'dmesg' entries like:
Out of Memory: Killed process 30293 (httpd).
Out of Memory: Killed process 32552 (mysqld).
Not a quick check wi
In response to some suggestions I give
more for the record on my problem of getting
ata100 transfer rates:
"hdparm /dev/hda" gives:
/dev/hda:
multcount= 0 (off)
I/O support = 1 (32-bit)
unmaskirq= 1 (on)
using_dma= 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
re
[EMAIL PROTECTED] said:
> drivers/char/applicom.c
There's a rewrite of this for the new PCI API. Doesn't yet support the ISA
cards because I didn't have one to test with. I'll try to get hold of one
and submit it.
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-ke
instead of need_reshed being a per-task flag, could it be
as a global flag ?, since every time current->need_reshed
is checked, schedule() is just called to pick another
process.
---
ðÏÌÕÞÉÔÅ É ÷Ù Ó×ÏÊ ÂÅÓÐÌÁÔÎÙÊ ÜÌÅËÔÒÏÎÎÙÊ ÁÄÒÅÓ ÎÁ http://Mail.ru
-
To unsubscribe from this list: send the line
On Wed, 21 Mar 2001, David Schwartz wrote:
>
> > how does linux provide the hostid string?
> >
> > on a sun box this is a guaranteed unique identifier, since AFAIK
> > intel architecture does not have this unique identifier can
> > two linux boxes end up with same hostid by chance?
>
> If
>From the source code of drivers/net/e100.c:
/
* Name: Phy82562EHDelayMilliseconds
*
* Description: Stalls execution for a specified number of milliseconds.
*
* Arguments: Time - milliseconds to delay
Andre Hedrick wrote:
> You may get a burst because of caching prefetch or predictive readahead,
> but that is artifical; however, in your case the root directory begins 25%
> in the drive.
But still it gives faster transfers than /dev/hda. The question is why.
I do not think that factor 2 can be
Hi. I was wondering if there has been any discussion of kernel
regression testing. Wouldn't it be great if we didn't have to depend
on human testers to verify every change didn't break something?
OK, I'll admit I haven't given this a lot of thought. What I'm
wondering is whether the user-mode
Ulrich Windl wrote:
> void
> Phy82562EHDelayMilliseconds(int Time)
> {
> udelay(Time);
> }
>
> AFAIK, udelay() delays microseconds, not milliseconds.
Yep, you are correct, and the code is incorrect.
mdelay() delays milliseconds.
--
Jeff Garzik | May you have warm words on a cold eve
On Thu, 22 Mar 2001, Brian Dushaw wrote:
> And for the record:
>
> "hdparm -d1 -t -X69 /dev/hda" gives:
My current hdparm line looks like this:
hdparm -m16 -c1 -u1 -k1 -X69 /dev/...
With this, I can get 28.x MB/s instead of 15.y with just -X69.
Nils
--
Nils Philippsen / Berliner Straße 39 /
hmm, on second thought, I think I would prefer the attached patch
(compiled but not tested).
Hardware usually returns all 1's when it's not present, or not working,
so think checking for addresses filled with 1's is a good idea too.
I also took the patch from alan's tree and made the memcmp agai
> That seems strange. What is realserver failing with ?
It isn't so much failing as it hangs. I don't know if you have used it
or not. On a startup of the realserver under a 2.2 kernel here is the
output:
*
RealServer (c) 1995-2000
"Mohammad A. Haque" <[EMAIL PROTECTED]> said:
> My machine locked hard last night for an unknown reason under
> 2.4.3-pre4. Rebooted and it did it's fsck thing. Got alot of errors
> about missing '..', fixed alot of things and moved some stuff to
> /lost+found.
>
> Some files got screwed up so I
On 22 Mar 2001 [EMAIL PROTECTED] wrote:
> Hi. I was wondering if there has been any discussion of kernel
> regression testing. Wouldn't it be great if we didn't have to depend
> on human testers to verify every change didn't break something?
>
> OK, I'll admit I haven't given this a lot of tho
> > > > handle the situation with 2 different CPUs (AMP = Assymmetric
> > > > multiprocessing ;-) correctly.
> > >
> > > "correctly". Intel doesn't support this (mis)configuration:
> > > especially with different steppings, not to mention models.
>
> I wouldn't call it misconfiguration, just be
> "Richard" == Richard B Johnson <[EMAIL PROTECTED]> writes:
Richard> On 22 Mar 2001 [EMAIL PROTECTED] wrote:
>> Hi. I was wondering if there has been any discussion of kernel
>> regression testing. Wouldn't it be great if we didn't have to depend
>> on human testers to veri
"David S. Miller" wrote:
>
> alterity <[EMAIL PROTECTED]> wrote:
> >Haven't seen a post for sometime from the usually prolific Mr Cox.
> >What's the gossip?
>
> They needed some help from him to position Mir for it's
> final descent.
Strange. I thought his key skill was stopping things from cr
Andreas Dilger wrote:
> > Correct, this was after running e2fsck. I'll try running it again when I
> > get home. Here is debugfs stat output for one of the broken files.
> > Again, I havent run e2fsck a second time yet.
Ok, I ran e2fsck twice last night. It didnt do anything the first run
but the
I have a Redhat 6.1 WS that was installed with 64 MB RAM. I added another
64 MB, booted, BIOS sees it, but top, free, etc still see only 64 MB.
Any clues on what to do?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More maj
Hi,
>How do I force a kernel thread to always be a child of init and never
>become a zombie ?
>
>I do call daemonize at the beginning of the thread (as it won't do
>anything with files, signals or whatever), but that doesn't
>seem to be enough.
>
Have a look at:
http://www.scs.ch/~frey/linux/ker
Jeff Garzik wrote:
>
> hmm, on second thought, I think I would prefer the attached patch
> (compiled but not tested).
>
> Hardware usually returns all 1's when it's not present, or not working,
> so think checking for addresses filled with 1's is a good idea too.
>
> I also took the patch from
Eli Carter wrote:
> The "!(addr[0]&1)" part of the test already catches the ff's case, so
> that is redundant.
> Using 6 bytes instead of 7 is an improvement.
oops. Thanks, updated patch attached. My patch also adds inline source
docs, and uses 'static inline' instead of 'static __inline__', tw
Rik van Riel wrote:
> One question ... has the OOM killer ever selected init on
> anybody's system ?
Yes, which is why I created the patch.
--
Patrick O'Rourke
978.606.0236
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Thu, 22 Mar 2001, Alan Cox wrote:
> > Regression testing __is__ what happens when 10,000 testers independently
> > try to break the software!
>
> Nope. Thats stress testing and a limited amount of coverage testing.
>
> > Canned so-called "regression-test" schemes will fail to test at least
>
On Thu, Mar 22, 2001 at 12:18:27AM -0500, Alexander Viro wrote:
>
> I started with adding
> void invalidate_dev(kdev_t dev, int sync_flag)
> {
> struct super_block *sb = get_super(dev);
> if (sync_flag == 1)
> sync_dev(dev);
> else if (sync_flag == 2
> hmm, on second thought, I think I would prefer the attached patch
> (compiled but not tested).
Pointless...
> Hardware usually returns all 1's when it's not present, or not working,
> so think checking for addresses filled with 1's is a good idea too.
If the multicast bit is set then we alrea
> Regression testing __is__ what happens when 10,000 testers independently
> try to break the software!
Nope. Thats stress testing and a limited amount of coverage testing.
> Canned so-called "regression-test" schemes will fail to test at least
> 90 percent of the code paths, while attempting to
On Thu, 22 Mar 2001, Neal Gieselman wrote:
> I have a Redhat 6.1 WS that was installed with 64 MB RAM. I added another
> 64 MB, booted, BIOS sees it, but top, free, etc still see only 64 MB.
> Any clues on what to do?
Maybe append="mem=128M" in lilo.conf helps ...
--
Thomas
-
To unsubscribe f
Hi,
There is what appears to be a simple thinko in kswapd. We really
ought to keep kswapd running as long as there is either a free space
or an inactive page shortfall; but right now we only keep going if
_both_ are short.
Diff below. With this change, I've got a 64MB box running Applix and
St
On Thu, 22 Mar 2001, Neal Gieselman wrote:
> I have a Redhat 6.1 WS that was installed with 64 MB RAM. I added another
> 64 MB, booted, BIOS sees it, but top, free, etc still see only 64 MB.
> Any clues on what to do?
Add mem=128M (or mem=127M if that fails) to the boot line (append in
LILO), o
On Thu, Mar 22, 2001 at 08:29:14AM -0600, Neal Gieselman wrote:
> I have a Redhat 6.1 WS that was installed with 64 MB RAM. I added another
> 64 MB, booted, BIOS sees it, but top, free, etc still see only 64 MB.
> Any clues on what to do?
Upgrade to linux-2.2.18 or linux-2.4.2.
Erik
--
J.A.K
Jeff Garzik wrote:
>
> Eli Carter wrote:
> > The "!(addr[0]&1)" part of the test already catches the ff's case, so
> > that is redundant.
> > Using 6 bytes instead of 7 is an improvement.
>
> oops. Thanks, updated patch attached. My patch also adds inline source
> docs, and uses 'static inline
>Have a look at:
>http://www.scs.ch/~frey/linux/kernelthreads.html
>I have an example there that starts and stops kernel threads
>from init_module and never produced a zombie.
>I use the same code also to start threads from ioctl and it
>works for me. I tested it on UP and SMP, Intel and Alpha,
>2
[EMAIL PROTECTED] wrote:
>
> Hi. I was wondering if there has been any discussion of kernel
> regression testing. Wouldn't it be great if we didn't have to depend
> on human testers to verify every change didn't break something?
IMHO, much of the strength of Linux is the very large, extremely
It seems that having a Myrinet 2k board plugged into any slot of the second
PCI bus
of the ES40 make the system freeze with 4 GBytes of RAM when doing cat
/proc/pci.
I just plugged the board back into one slot of PCI 0 and it works again.
Why does it work with Tru64 and not with Linux ? I don't
>If you write into those resources and they are absent, bad things
>sometimes happen. So, they are always added to the reserved-resource
>list. I already had this argument with Linus :)
Oops. Got that wrong. Time to fix CVS.
MS: (n) 1. A debilitating and surprisingly widespread affliction tha
>I still can't see a reason for allocating it before the device drivers
>could do that.
See Jeff's response. We got it wrong as well :-( Time to fix that.
>What is the "input api"? Could You give me any URL to read?
http://www.suse.cz/development/inputhttp://www.suse.cz/development/
And http:
On Thu, Mar 22, 2001 at 10:13:04AM -0500, Wade Hampton wrote:
> [EMAIL PROTECTED] wrote:
> > Hi. I was wondering if there has been any discussion of kernel
> > regression testing. Wouldn't it be great if we didn't have to depend
> > on human testers to verify every change didn't break something?
On Thu, 22 Mar 2001, Guest section DW wrote:
> > One question ... has the OOM killer ever selected init on
> > anybody's system ?
>
> Last week I installed SuSE 7.1 somewhere.
> During the install: "VM: killing process rpm",
> leaving the installer rather confused.
> (An empty machine, 256MB, 14
Eli Carter wrote:
> Mmmm documentation. Yummy. ;)
>
> When I submitted the original patch, someone wanted to add the ff's
> check as well... to reduce the number of people who make that
> suggestion, perhaps the comment should read:
>
> + * Check that the Ethernet address (MAC) is not a mu
Guest section DW <[EMAIL PROTECTED]> writes:
> On Wed, Mar 21, 2001 at 08:48:54PM -0300, Rik van Riel wrote:
> > On Wed, 21 Mar 2001, Patrick O'Rourke wrote:
>
> > > Since the system will panic if the init process is chosen by
> > > the OOM killer, the following patch prevents select_bad_process
Hi!
When I try to build the new aic7xxx modules in kernel 2.4.3-pre6 it
stops at "/usr/src/linux-2.4.3-pre6/drivers/scsi/aic7xxx/aicasm":
+++
make -C aic7xxx modules
make[3]: Entering directory `/usr/src/linux-2.4.3-pre6/drivers/scsi/aic7xxx'
yacc aicasm/aicasm_gram.y
mv -f y.tab.c aicasm/aic
On 22 Mar 2001 [EMAIL PROTECTED] wrote:
> Hi. I was wondering if there has been any discussion of kernel
> regression testing. Wouldn't it be great if we didn't have to depend
> on human testers to verify every change didn't break something?
This is definately a great idea. A relatively easy
On Thu, 22 Mar 2001, Tom Kondilis wrote:
> I had a 2.4.3pre3 do a 'Killing Init'
> My assuption is that I had a large benchmark running, while the benchmark
> was running, I updated inittab to uncomment a mgetty of my serial port, and
> followed it with a 'telinit q'.
> When the system thought i
Vincent Sweeney wrote:
>
> I have a question regarding a busy box I recently updated to
> '2.4.2-ac20'. It has been running for several hours without any real
> problems until I started getting 'dmesg' entries like:
>
> Out of Memory: Killed process 30293 (httpd).
> Out of Memory: Killed process
On Thu, Mar 22, 2001 at 09:56:16AM -0600, Nathan Straz wrote:
> On Thu, Mar 22, 2001 at 10:13:04AM -0500, Wade Hampton wrote:
> > However, a lab dedicated to testing the linux kernel, properly
> > funded, staffed, and containing the most common hardware and
> > software would be a good idea. Do
Please reply directly as I'm in ECN exile from this mailing list!
[1.] One line summary of the problem:
2.2.18 oops leaves umount hung in disk sleep
[2.] Full description of the problem/report:
Greetings! We have a backup server running 2.2.18,
nfs-kernel-server 0.1.9.1-1
On Thu, Mar 22, 2001 at 02:24:56AM +0900, Chiaki Ishikawa wrote:
> --- begin quote ---
> > enclosed are 163 potential bugs in 2.4.1 where blocking functions are
> > called with either interrupts disabled or a spin lock held. The
> > checker works by:
>
> Here's the file manifest. Apologies.
>
>
Hi again.
I've written my own test program, and I get 12M throughput.
I used a packet size of 1024 Bytes. Smaller packages seems to result in
less throughput.
There was no load on the machine I tested on. Does the throughput get
better is there is a lot of stress on the machine? (eg. compilin
Hi,
>> http://www.scs.ch/~frey/linux/kernelthreads.html
>Could you explain me a bit why you need the lock_kernel ? My probe
>thread is already protected by some atomic ops, but I'm considering
>changing them to semaphores. Is there any need for the bkl to be taken
>when calling daemonize or is th
On Thu, 22 Mar 2001, Ingo Oeser wrote:
> Could we remove the "magic" sync_flag from the exported interface?
Sure. But I seriously suspect that sync_dev() is wrong in 100% of cases.
So "flag" is eventually going to become "do we want to sync it or not?"
thing. However, I don't want to deal with
On Thu, 22 Mar 2001, Stephen C. Tweedie wrote:
>
> There is what appears to be a simple thinko in kswapd. We really
> ought to keep kswapd running as long as there is either a free space
> or an inactive page shortfall; but right now we only keep going if
> _both_ are short.
Hmm.. The comment
list
-
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/
If I compile the kernel with 4GB support it doesn't
boot. The kernel starts fine but the boot sequence
ends with an error about modprobe that repeats
endlessly.
In 1GB It works fine but it doesn't use 128MB of
very useful memory.
Suggestions ?
[Dual-800, 1GB, 2.4.2, egcs-2.91.66, modutils 2.4.
On Thu, 22 Mar 2001, Stephen C. Tweedie wrote:
> Hi,
>
> There is what appears to be a simple thinko in kswapd. We really
> ought to keep kswapd running as long as there is either a free space
> or an inactive page shortfall; but right now we only keep going if
> _both_ are short.
>
> Diff below
I'm sorry for the empty message. As you can see it was
delivered to the wrong address.
Please disregard this posting.
Again, my apologies.
> list
>
> -
> To unsubscribe from this list: send the line "unsubscribe
linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo i
> pull it all right back in again. It continues through the entire
> build with the cost seen in the time numbers. (the ac20.virgin run
> was worse by 30 secs than average, but that doesn't matter much)
Using my reference interactive test (An application which renders 3D graphics
and generates
"Brent D. Norris" wrote:
> > That seems strange. What is realserver failing with ?
>
> It isn't so much failing as it hangs.
It might be interesting to strace the realserver startup
both under 2.2 and 2.4 -
cu
Jup
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
th
Richard Guenther <[EMAIL PROTECTED]> wrote:
>On Mon, 19 Mar 2001, Colin Watson wrote:
>> Or you can register binfmt names that are registered already and
>> silently shadow old ones, or register names like 'register', 'status',
>> '.', and '..'. It's hideous to manage reliably from userspace.
>
>I
>- automated heavy stress testing
This would be an interesting one to me, from a benchmarking POV. I'd like
to know what my hardware can really do, for one thing - it's all very well
saying this box can do X Whetstones and has a 100Mbit NIC, but it's a much
more solid thing to be able to say "my
} On 22 Mar 2001 [EMAIL PROTECTED] wrote:
}
} > Hi. I was wondering if there has been any discussion of kernel
} > regression testing. Wouldn't it be great if we didn't have to depend
} > on human testers to verify every change didn't break something?
} >
} > OK, I'll admit I haven't given thi
We have a start for PPC. It has the title "Regression Tester" but is
actually a "compiles and boots tester". The aim is a automated regression
test.
Take a look at http://altus.drgw.net/
It pulls directly from our BitKeeper archive every time we push a change
and goes through the build targete
Hi.
My program controls a device (a programmer for microcontrollers) via the
serial port. The program sits in a tight loop, writing a few (typical 6)
bytes to the port, and waits for a few (typ. two) bytes to be returned from
the programmer.
The program works, but it is very slow. I use an osc
Hi,
On Thu, Mar 22, 2001 at 09:36:48AM -0800, Linus Torvalds wrote:
> On Thu, 22 Mar 2001, Stephen C. Tweedie wrote:
> >
> > There is what appears to be a simple thinko in kswapd. We really
> > ought to keep kswapd running as long as there is either a free space
> > or an inactive page shortfall
>The stuff done in daemonize() and the exit_files could need
>the kernel lock. At least on some 2.2.x version it does,
>I did not check whether it is still needed on 2.4.
Well, I don't really plan to backport this to 2.2.x. I'll
try to see if my problem is related to the lack of kernel
lock, or m
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
(Note that the cmsfs port to 2.4 is a work in progress)
2.4.2-ac21
o Merge with Linus 2.4.3pre6
o Close last known rei
> " " == Camm Maguire <[EMAIL PROTECTED]> writes:
> 2.2.18 oops leaves umount hung in disk sleep
This is normal behaviour for an Oops ;-)
> Unable to handle kernel NULL pointer dereference at
> virtual address
current-> tss.cr3 = 02872000, %%cr3 = 02872
I am trying to compile the 2.4.3-pre6 linux kernel and it is failing
because
it cannot find the "db.h" header file. I've got no such file on my
system nor
as there any reference to "db.h" in the whole of the kernel source.
According
to the changelog this is a new version of the aic7xxx driver add
Parity Error wrote:
>
> instead of need_reshed being a per-task flag, could it be
> as a global flag ?, since every time current->need_reshed
> is checked, schedule() is just called to pick another
> process.
>
> ---
But for which cpu? Really this is a short cut to provide a per cpu area
that I
I can't say I understand the whole MM system, however the random killing of
processes seems like a rather unfortunate solution to the problem. If someone
has a spare minute, maybe they could explain to me why running out of free
memory in kswapd results in a deadlock situation.
That aside, wou
Rik van Riel wrote:
>This is definately a great idea.
[...]
>Note that some of these testing options are almost trivial to
>set up
[...]
If an effort in this direction produced a "kernel-tester.tar.gz"
package, I'm sure lots of people with spare hardware would install
it, and then check it on
I found some code that seems wrong and didn't even match it's comment.
Patch is against 2.4.2, but should go cleanly against 2.4.3-pre6 as well.
Jan
--- linux/fs/inode.c.orig Thu Mar 22 13:20:55 2001
+++ linux/fs/inode.cThu Mar 22 13:21:32 2001
@@ -133,7 +133,7 @@
if (sb) {
On Thu, 22 Mar 2001, Alan Cox wrote:
> > pull it all right back in again. It continues through the entire
> > build with the cost seen in the time numbers. (the ac20.virgin run
> > was worse by 30 secs than average, but that doesn't matter much)
>
> Using my reference interactive test (An appli
On Thu, 22 Mar 2001, Colin Watson wrote:
> I would very much like to be able to assume that a filesystem never
> contains two identical filenames linking to different inodes, and that
> any . and .. links I find always point to things that are vaguely like
> directories! I realize that you can'
On Tue, 20 Mar 2001, Gérard Roudier wrote:
> On Tue, 20 Mar 2001, Geert Uytterhoeven wrote:
> > On Tue, 20 Mar 2001, Geert Uytterhoeven wrote:
> > > On Mon, 19 Mar 2001, Jeff Garzik wrote:
> > I did some more tests:
> > - The problem also occurs when tarring up files from a disk on the Sym53c875
On Thu, Mar 22, 2001 at 12:01:43PM -0300, Rik van Riel wrote:
> > Last month I had a computer algebra process running for a week.
> > Killed. But this computation was the only task this machine had.
> > Its sole reason of existence.
> > Too bad - zero information out of a week's computation.
> >
Hi,
On Thu, Mar 22, 2001 at 01:42:15PM -0500, Jan Harkes wrote:
>
> I found some code that seems wrong and didn't even match it's comment.
> Patch is against 2.4.2, but should go cleanly against 2.4.3-pre6 as well.
Patch looks fine to me. Have you tested it? If this goes wrong,
things break
1 - 100 of 241 matches
Mail list logo
