Riley Williams writes:
> Hi Albert.
The rule should be like this:
List the lowest version number required to get
2.2.xx-level features while running a 2.4.xx kernel.
>>> Replace that "a 2.2.xx" with "my current" and remove all
>>> restrictions on what the current kernel
Jacob Luna Lundberg wrote:
>
> Oh Great Gurus:
>
> I have an agp video card that seems quite picky about interrupts, and a
> bios that is insisting on sharing the video card's interrupt with whatever
> is in the first pci slot. So my question is, is there any way for the
Your problem is most l
Under linux-2.4.3-pre6 compiled for SMP, loading agpgart.o
hangs the system in remap_area_pages (arch/i386/mm/ioremap.c) at
the call to spin_lock(&init_mm.page_table_lock), which is not in 2.4.2.
When I load agpgart.o, I get the following messages:
Linux agpgart interface v0.99 (
> That's not the OOM killer however, but init dying because it
> couldn't get the memory it needed to satisfy a page fault or
> somesuch...
Ehrm, I would like to re-state that it still would be nice if
some mechanism got introduced which enables one to set certain
processes to "cannot be killed".
On Fri, Mar 23, 2001 at 01:38:00AM +0100, J . A . Magallon wrote:
> Yes, a null sentence can shut up the compiler. But what is the purpose of
> a jump to the end instead of a return ? Some optimization ?
So that when someone decides that the function needs to do some extra
initialisation at the
Hi Albert.
Since you appear to be determined to ignore reason and stick to your
misguided guns I'll leave you to destroy all the good work that has
gone into the Linux kernel's documentation and make it something even
Bill Gates would be proud of. However, I'll stick to documentation
that actuall
On Thu, 22 Mar 2001, Alexander Viro wrote:
> Actually, the right thing to do would be to drop the ugly tricks with
> writing to .../register and use normal create()/write()/close() to add
> entries. Commit-on-close and there you go. unlink() to remove these
> suckers, chmod g-r to disable.
>
> IO
> If it's a 500MHz Thinkpad, then I'm guessing it's something like a 600X.
> That doesn't have Speedstep. The speed changes are done by some circuitry
> in the laptop. I can try to find out more if this would help.
> The newer machines are using Speedstep.
Ok
Any info on how the laptop wants to
> > o Fix ppp memory corruption (Kevin Buhr)
> > | Bizzarely enough a direct re-invention of a 1.2 ppp bug
>
> Could this explain my MPPP skb corruption I've reported since 2.3.x?
At most it explains some weird corruption cases with small kernel blocks.
I really doubt they are related
-
To unsu
I wrote:
> Under linux-2.4.3-pre6 compiled for SMP, loading agpgart.o
>hangs the system in remap_area_pages (arch/i386/mm/ioremap.c) at
>the call to spin_lock(&init_mm.page_table_lock), which is not in 2.4.2.
[...]
> agp_backend_initialize
> agp_generic_create_gatt_table
>
> Wonder of wonders, I flashed the bios to the latest and greatest version.
> Current data transfer rates are 35.7 MB/sec on both udma drives, exactly
> as expected and darn close to the continuous read limits of the disks.
> The audio also started working, flawlessly.
>
> There are other issues
> On the ThinkPad 600E (at least), we get a Power Status Change APM event.
Any reason we couldn't recalibrate the bogomips on a power status change,
at least for laptops we know appear to need it (I can make the DMI code look
for matches there..)
-
To unsubscribe from this list: send the line "un
On Fri, 16 Mar 2001, Jeff Garzik wrote:
> Does the attached patch solve the problem?
I didn't have a crash so far, so until now it look's okay. I would like to
say "you fixed it", but that's the problem with bugs: You can prove, there
are no bugs.
I will tell you as soon as possible if it should
Hi,
On Thu, Mar 22, 2001 at 09:42:55PM -0500, Pete Zaitcev wrote:
> Some guy sent me the attached patch. He says it allows
> him to use 2 additional keys on the 106 key USB keyboard.
> I never saw a 106 key keyboard before, USB or not.
> Does anyone understand what is going on? Vojtech?
don't kn
Kurt Garloff <[EMAIL PROTECTED]> writes:
> 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:
> > > especia
On Thu, Mar 22, 2001 at 01:20:40PM +, Pavel Machek wrote:
> > Kurt Garloff <[EMAIL PROTECTED]> wrote:
> Notice, that one of your CPUs is twice as fast as second one. You'll
> need some heavy updates in scheduler.
I know that making sure to have a fair scheduling on non-symmetric
multiprocess
[EMAIL PROTECTED] writes:
> 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?
There is a some truth to this. However for kernel development the
On Wed, 21 Mar 2001 11:14:53 -0800
Tim Moore <[EMAIL PROTECTED]> wrote:
> Change partition type to 'c' (fat32+LBA); check that BIOS is set for
> (AUTO or USER) and LBA.
>
Hi Tim,
I am afraid that I do not know how to change my partition type. I can confirm.
however, that the BIOS is set to Au
The latest version is always available at http://www.tuxedo.org/~esr/cml2/
Release 0.9.6: Fri Mar 23 05:16:05 EST 2001
* When we return from a submenu in the tk interface, restore
the scrolling location in the parent.
* Disable width resizing in tk front end, it only con
Hi,
When I mount a storage device using the command as follow
mount -t msdos /dev/xxx /mnt/xxx -o blocksize=1024
This command will cause error on kernel linux2.4.2
When I remove the option , " -o blocksize=1024", it's OK.
But on the kernel version 2.2.17, with the option blocksize=1024, it wor
On Wed, 21 Mar 2001 11:29:00 -0800 (PST)
Andre Hedrick <[EMAIL PROTECTED]> wrote:
>
> First you have the faster portion of the drive using a lame OS, so do
> not
> expect Linux to perform if you put it on the slowest portions of the
> device.
>
Hi Andre,
Thanks for responding. The days of the
On Wed, 21 Mar 2001 11:38:47 -0500
Mike Dresser <[EMAIL PROTECTED]> wrote:
>
> Keep in mind that drives have different transfer rates depending on
> where on the drive you read from.
>
That is something I knew a little about, and am now learning much more. Even so, I am
surprised that there i
[Sorry for posting three messages to linux-kernel about this.
Each time I was pretty sure I was done for the night. Anyhow, I
hope this proposed patch makes up for it.]
In linux-2.4.3-pre6, a call to vmalloc can result in a call to
pte_alloc without the appropriate page_table_loc
Hi, we modified the block checker and run it again on linux 2.4.1. (The
block checker flags an error when blocking functions are called with
either interrupts disabled or a spin lock held. )
It gave us 4 warnings in kernel/module.c. Because we are unaware of the
contexts where these functions are
Hi everybody,
thanks for your patience.
It's an error on my side (as expected).
Looking through the sources of mount I found out that due to a bad copying
mount had -rwsr-xr-x with a non-0 user id. That explains it.
Thanks again!
Phil
-
To unsubscribe from this list: send the line "unsubsc
Which kernel are you using.
I've had a similar problem with 2.2.18.
I've backported 2.2.19pre changes to it.
(i.e. apply on 2.2.18 a diff of the file drivers/net/eepro100.c made between 2.2.18
and the last 2.2.19pre)
And since I've never seen this problem again.
Christophe
On jeu, 22 mar 2001
Kevin Buhr wrote:
>
> ...
> When changing line disciplines, "sys_ioctl" gets the big kernel lock
> for us, and the "tty_set_ldisc" function doesn't get any additional
> locks. It just calls the line discipline "open" function.
>
> Suppose, at this point, the modem hangs up. From a hardware
> i
Rik van Riel wrote:
>
> On Sat, 23 Mar 2002, Martin Dalecki wrote:
>
> > This is due to the broken calculation formula in oom_kill().
>
> Feel free to write better-working code.
I don't get paid for it and I'm not idling through my days...
-
To unsubscribe from this list: send the line "unsubs
This is just a final pre so people can double check the build fixes
2.2.19pre18
o Fix a problem where the scc driver could hang (Jean F6FBB)
o Fix buffer/page cache coherency problem when
user/kernel addresses are ambiguous (S/390) (Ulrich Weigand)
o Update credit
On Fri, 23 Mar 2001 02:41:40 -0800 (PST),
Junfeng Yang <[EMAIL PROTECTED]> wrote:
>Hi, we modified the block checker and run it again on linux 2.4.1. (The
>block checker flags an error when blocking functions are called with
>either interrupts disabled or a spin lock held. )
>
>It gave us 4 warni
> Hi, we modified the block checker and run it again on linux 2.4.1. (The
> block checker flags an error when blocking functions are called with
> either interrupts disabled or a spin lock held. )
lock_kernel() isnt a spinlock as such.
> 2. Can functions like kmem_cache_create, kmem_cache_alloc,
On Fri, 23 Mar 2001, Adam J. Richter wrote:
> [Sorry for posting three messages to linux-kernel about this.
> Each time I was pretty sure I was done for the night. Anyhow, I
> hope this proposed patch makes up for it.]
>
> In linux-2.4.3-pre6, a call to vmalloc can result in a cal
Amit D Chaudhary wrote:
> So, it is not a requirement currently but it is useful to have the script not
> dependent on the current pivot_root implementation.
Yes. Also note that the relative path for dev/console works in
either case, while /dev/console would fail without the implied
chroot in
Amit D Chaudhary wrote:
> To summarize, pivot_root has been a life saver as the earlier real_root_dev
> might not have been useful in this case.
The whole old change_root mechanism with real_root_dev is best forgotten
quickly ;-) It's also completely helpless as soon as you fire off some
kernel
On Fri, Mar 23, 2001 at 04:04:09AM -0300, Rik van Riel wrote:
> On 22 Mar 2001, Michael Peddemors wrote:
>
> > Here, Here.. killing qmail on a server who's sole task is running mail
> > doesn't seem to make much sense either..
>
> I won't defend the current OOM killing code.
>
> Instead, I'm as
Marcelo Tosatti <[EMAIL PROTECTED]> writes:
>There is no need to hold mm->page_table_lock for vmalloced memory.
I don't know if it makes a difference, but I should clarify
that mm == &init_mm throughout this code, not ¤t->mm.
Adam J. Richter __ __ 4880 Stevens Creek
On Thu, 22 Mar 2001, Andreas Dilger wrote:
> If this is the case, then all of the other zero initializations can be
> removed as well. I figured that if most of the fields needed to be
> zeroed, then ones _not_ being zeroed would lead to this problem.
Other zero initializations in ino
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
Hi!
> Problem: Certain Laptops (IBM Thinkpads is where i see the issue) reduce the
> CPU frequency based upon whether the unit is on battery power or direct
> power. When the Linux kernel boots up, then the cpu_khz (time.c)
This is issue with my toshiba sattelite, too. I even had a patch to
det
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-ac23
o Fix a nasty shared memory locking bug (Steph
Hi,
I want to use a semaphore for the classic producer/consumer case
(put the consumer to wait until X items are produced, where X != 1).
If X is 1, the semaphore is a simple MUTEX, ok.
But if the consumer wants to wait for several items, it doesn't
seem to work (or something is bad in my code
In message <[EMAIL PROTECTED]> you write:
> Nigel Gamble wrote:
> >
> > On Wed, 21 Mar 2001, Keith Owens wrote:
> > > I misread the code, but the idea is still correct. Add a preemption
> > > depth counter to each cpu, when you schedule and the depth is zero then
> > > you know that the cpu is n
Andrew Morton writes:
> Mikael Pettersson wrote:
> >
> > [+] Speaking as a hacker on a runtime system for a concurrent
> > programming language (Erlang), I consider the current Unix/POSIX/Linux
> > default of having the kernel throw up[*] at the user's current stack
> > pointer to be unbeli
"Adam J. Richter" wrote:
>
> In case anyone is interested, the conflicting lock of
> init_mm.page_table_lock was acquired in line 1318 of mm/memory.c,
> in pte_alloc.
You can sorta blame me for that. I reviewed the locking in
the mmap_sem patch and said it was correct :(
I only checke
In message <[EMAIL PROTECTED]> you write:
>skb_queue_len : 56 : 2:
skb_queue_len not being checked? Look at these two places: either
your analysis has a bug, or there's some wierd code...
skb_push and skb_pull return the new skb data region, but
In message <[EMAIL PROTECTED]> you write:
> If I understood Andrew's mail correctly, rsync freezes when
> large amount of errors happen. Particularly, here ssh always freezes
Known hard-to-fix bug in rsync; too many errors in the pipe, and it
locks up.
Rusty.
--
Premature optmztion is rt of all
JorgP ([EMAIL PROTECTED]) wrote
> Lucent Microelectronics 56k WinModem s (rev 01)
> VIA Technologies, Inc. VT82C686 [Apollo Super AC97/Audio] (rev 50)
>
> are either or both support by 2.4 kernel? If so, what modules need to be
> loaded?
For VIA audio , load the via82cxxx_audio module.
--
Hi!
Only a small cosmetic thing : when doing a 'make menuconfig' then
--> "Processor type and features"
--> "(Pentium/K6/TSC/CyrixIII) Processor family"
When doing enter on this entrry, the background of the screen disapears.
If I remember, this has been already reported in a previous version.
-
2.4.2-ac23
...
o Fix i386 #ifdef bug with notsc disable (Anton Blanchard)
...
This change has broken the compile for me (my .config is attached):
gcc -D__KERNEL__ -I/home/bunk/linux/linux/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpre
On Fri, Mar 23, 2001 at 12:06:30PM +, Alan Cox wrote:
> o Fix i386 #ifdef bug with notsc disable (Anton Blanchard)
gcc -D__KERNEL__ -I/usr/src/kernel/2.4.2-ac23/include -Wall
-Wstrict-prototypes -O2 -fomit-frame-pointer -fno-strict-aliasing -pipe
-mpreferred-stack-boundary=2 -mar
[EMAIL PROTECTED] said:
> Also as a note, what we are doing is keeping our rootfs on flash as a
> tar.gz and reading it and mounting it on a ramfs in the /linuxrc
> before doing a pivot_root. To summarize, pivot_root has been a life
> saver as the earlier real_root_dev might not have been use
Duh yes.. it would for some people
--- arch/i386/kernel/setup.c~ Thu Mar 22 23:18:21 2001
+++ arch/i386/kernel/setup.cFri Mar 23 13:26:08 2001
@@ -2276,7 +2276,7 @@
*/
/* TSC disabled? */
-#ifdef CONFIG_X86_TSC
+#ifndef CONFIG_X86_TSC
if ( tsc_disable )
> >
> >It was causing SMP boxes to crash mysteriously after
> >several hours or days. Quite a lot of them. Nobody
> >was able to explain why, so it was turned off.
>
> I know why it was turned off by default. The annoying this is that now
> the *only* way to activate the watchdog is via a boot
Brian Dushaw ([EMAIL PROTECTED]) wrote :
> Dear Linux Kernel Wisemen,
>I have been following the discussion of the VIA vt82c686b chipset
> and the troubles people have had in getting UDMA(100) to work. This
> is to report that I have now tried the 2.4.2-ac20 kernel and the
> 2.2.18 kernel
I've compiled kernel 2.2.18 with DHCP support for
diskless workstation. And I noticed, that machine
doesn't send DHCP requests.
2.2.16 in identical configuration works good.
Is it really bug?
I'm sending my .config in attachment.
Regards,
Michal 'Orr' Daszkowski
PS. Forgive me my poor englis
On Fri, 23 Mar 2001, Admin Mailing Lists wrote:
> > >It was causing SMP boxes to crash mysteriously after
> > >several hours or days. Quite a lot of them. Nobody
> > >was able to explain why, so it was turned off.
> >
> > I know why it was turned off by default. The annoying this is that now
>
Hi Dawson,
On Sat, Mar 17, 2001 at 08:23:34PM -0800, Dawson Engler wrote:
> > 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.
>
[...]
> dri
Guest section DW <[EMAIL PROTECTED]> writes:
> On Fri, Mar 23, 2001 at 04:04:09AM -0300, Rik van Riel wrote:
> > On 22 Mar 2001, Michael Peddemors wrote:
> >
> > > Here, Here.. killing qmail on a server who's sole task is running mail
> > > doesn't seem to make much sense either..
> >
> > I won
On Fri, 23 Mar 2001, Martin Dalecki wrote:
> Rik van Riel wrote:
> > On Sat, 23 Mar 2002, Martin Dalecki wrote:
> >
> > > This is due to the broken calculation formula in oom_kill().
> >
> > Feel free to write better-working code.
>
> I don't get paid for it and I'm not idling through my days..
I have sent a patch to Alan and Linus about this also. We have cpqarray and
cciss controllers that use major 72-79 and 104-111. Alan said he doesn't
have time to look at it till mid April and Linus hasn't responded to me at
all about it. The best way is to actually rewrite the kstat architectur
Jonathan Morton <[EMAIL PROTECTED]> said:
> >- 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
Problem solved !
The main problem was that I didn't know that the equipment used
DTR as character acknowledge (not RTS/CTS which is common for flow
control). I didn't even bother to look at those lines with the
oscilloscope. Now the software runs fine with negligible latency.
Now the total laten
"Christian Bodmer" <[EMAIL PROTECTED]> said:
> 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 kswap
>So I think it's reasonable to use keventd as `kinit', if you like.
>Something which knows how to launch and reap kernel daemons, and
>which provides a known environment to them.
>
>A kernel API function (`kernel_daemon'?) which does all this
>boilerplate is needed, I think.
>
I completely agree.
Personally I think the OOM killer itself is fine. I think there are
problems elsewhere which are triggering the OOM killer when it should
not be triggered, ie. a leak like Doug Ledford was reporting.
I definitely see heavier page/dcache usage in 2.4 -- but that is to be
expected due to 2.4 chang
I had a similar experience:
X crashed , hosing the console , so I could not initiate
a proper shutdown.
Here I must note that the response you got on linux-kernel is
shameful.
What I did was to write a kernel/apmd patch , that performed a
proper shutdown when I press the power button ( which lu
From: "Andrew Morton" <[EMAIL PROTECTED]>
> Your analysis is correct. It's a bug.
>
> Furthermore, n_hdlc_tty_open() (for example) can sleep prior to
> incrementing the module refcount, which means the module can be
> unloaded while it's running. I cut a patch ages ago which fixes
> this one f
On Fri, Mar 23, 2001 at 10:13:55AM -0500, Jeff Garzik wrote:
> Personally I think the OOM killer itself is fine. I think there are
> problems elsewhere which are triggering the OOM killer when it should
> not be triggered, ie. a leak like Doug Ledford was reporting.
>
> I definitely see heavier
Thanks Alan, but no dice. Most of the stuff on the board is autodetect
anyway, but even after a reset it exhibited the same behaviour.
Windows, however, continues to run fine. It's not properly set up with
all the various drivers installed though, so its probably running with the
equivalent of
On Fri, Mar 23, 2001 at 05:10:56PM +0100, Jan Harkes wrote:
> btw. There definitely is a network receive buffer leak somewhere in
> either the 3c905C path or higher up in the network layers (2.4.0 or
> 2.4.1). The normal path does not leak anything.
What do you mean with "normal path" ?
And ar
Mikael Pettersson <[EMAIL PROTECTED]> said:
> Oh I know 99% of the processes getting this will die. The behaviour I'd
> expect from vanilla code in this particular case (stack overflow) is:
> - page fault in stack "segment"
> - no backing store available
> - post SIGSEGV to current
> * push sigh
Hi, here is the error message
make[1]: Entering directory `/usr/src/linux-test/linux/arch/i386/kernel'
gcc -D__KERNEL__ -I/usr/src/linux-test/linux/include -Wall -Wstrict-prototypes
-O2 -fomit-frame-pointer -fno-strict-aliasing -pipe -mpreferred-stack-boundary=2
-march=i686-c -o setup.o setup
Hi,
I'm having problems getting my 2.4.2 kernel to synchronise properly. For
some reason, NTP is insisting on making time offset adjustments.
Is anyone else using NTP with 2.4.2, and if so, are you synchronising
properly?
(I'm using the RH7.0 version of ntp-4.0.99j here)
--
Russell King ([EMA
I'm trying to use Stephen Tweedie's raw device support to access disks
attached to a Qlogic ISP 1040/B controller and kernel oopses.
Has anyone used the raw device with qlogicisp driver? Does anyone have any
interest in looking at this?
Thanks!
--
Joel Gallun
Leandro Bernsmuller ([EMAIL PROTECTED])
> Hi,
>
> some body know if exist or is possible to do one
> driver
> to makes floppy drive use some type of "balanced" bits
> distribution?
> The idea is simple: format a disk doing inner tracks
> with less bits than
> in external tracks.
> Maybe
> Your idea is nice, but the patch lacks a few things:
>
> - SMP locking, what if some other process faults in this page
> between the atomic_read of the page count and the test later?
It can't happen. free_pte is called with the page_table_lock held in
addition to having the mmap_sem downed
> I'm trying to use Stephen Tweedie's raw device support to access disks
> attached to a Qlogic ISP 1040/B controller and kernel oopses.
2.2 or 2.4 ?
> Has anyone used the raw device with qlogicisp driver? Does anyone have any
> interest in looking at this?
It shouldnt matter which driver is in
ok, results of additional testing are a little different than i anticipated.
here is some recent information using the IBM Thinkpad 600X. for testing
purposes I used an mdelay of 1 (10 seconds) in the driver in the resume
code. the results are the same with or without booting with the "notsc"
On Fri, Mar 23, 2001 at 12:24:03PM -0400, Horst von Brand wrote:
> Can we please remember that OOM is *not* in any way a "normal system state"
> that has to be handled in a civilized, orderly way? This is just an escape
> route in case everything else has failed.
Can we please remember that a Bl
On Fri, Mar 23, 2001 at 05:17:16PM +0100, Andi Kleen wrote:
> On Fri, Mar 23, 2001 at 05:10:56PM +0100, Jan Harkes wrote:
> > btw. There definitely is a network receive buffer leak somewhere in
> > either the 3c905C path or higher up in the network layers (2.4.0 or
> > 2.4.1). The normal path does
On Fri, Mar 23, 2001 at 11:56:23AM -0300, Rik van Riel wrote:
> On Fri, 23 Mar 2001, Martin Dalecki wrote:
> > > Feel free to write better-working code.
> >
> > I don't get paid for it and I'm not idling through my days...
>
>
No lies please.
Andries
-
To unsubscribe from this list: send t
> This is just an escape route in case everything else has failed.
>
> Linux is unreliable.
> That is bad.
Since your definition of reliability is a mathematical abstraction requiring
infinite storage why don't you start by inventing infinitely large SDRAM
chips, then get back to us ?
-
To unsu
Rik, is there any way we could get a /proc entry for this, so that one
could do something like:
cat /proc/oom-kill-scores | sort +3
to get a process list (similar to ps) with a field for the current oom
scores? It would likely be very useful to be able to dump the current
scores and see what wi
"J . A . Magallon" <[EMAIL PROTECTED]> said:
> I have been building (and hopefully booting) ac-21 with gcc-3.0 snapshot
> dated 20010312. I have cleared the 99% of the warnings that 3.0 issues
> when building the kernel. Obviuosly, only in the main kernel part for
> i386 and the drivers I use. I s
Russell King wrote:
> Is anyone else using NTP with 2.4.2, and if so, are you synchronising
> properly?
Works for me. (RH7, ntp-4.0.99j-7, Kernel 2.4.2-ac23 - but worked with
plain 2.4.2, too)
Holger
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a messa
Hello!
2.4.2-ac23 doesn't compile in arch/i386/kernel/setup.c. Somebody has
changed CONFIG_TSC to CONFIG_X86_TSC, probably without testing the
resulting code.
CONFIG_TSC was never defined, so it was an error. However, what we have
now is that tsc_disable is declared if CONFIG_X86_TSC is not defi
Resend. I got no answer.
--
Mircea Damian
E-mails: [EMAIL PROTECTED], [EMAIL PROTECTED]
WebPage: http://taz.mania.k.ro/~dmircea/
Hello,
[1.] One line summary of the problem:
Kernel OOPS. Machine hanged under heavy load.
[2.] Full description of the problem/report:
The computer that is
On Thu, 22 Mar 2001, Guest section DW wrote:
> 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()
On Wed, 21 Mar 2001, Rik van Riel wrote:
> One question ... has the OOM killer ever selected init on
> anybody's system ?
Hi Rik,
When I ported your OOM killer to 2.2.x and integrated it into the
'reserved root memory' [*] patch, during intensive testing I found two
cases when init was killed.
On Fri, 23 Mar 2001, Horst von Brand wrote:
> Jonathan Morton <[EMAIL PROTECTED]> said:
> > >- 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
On Fri, Mar 23, 2001 at 07:50:25AM -0700, Eric W. Biederman wrote:
> > Mar 23 11:48:49 mette kernel: Out of Memory: Killed process 2019 (emacs).
> > Mar 23 11:48:49 mette kernel: Out of Memory: Killed process 1407 (emacs).
> > Mar 23 11:48:50 mette kernel: Out of Memory: Killed process 1495 (emac
christophe barbe wrote:
>
> Which kernel are you using.
>
> I've had a similar problem with 2.2.18.
> I've backported 2.2.19pre changes to it.
> (i.e. apply on 2.2.18 a diff of the file drivers/net/eepro100.c made between 2.2.18
>and the last 2.2.19pre)
> And since I've never seen this problem
> That depends what you mean by "must not". If it's your missile guidance
> system, aircraft autopilot or life support system, the system must not run
> out of memory in the first place. If the system breaks down badly, killing
> init and thus panicking (hence rebooting, if the system is set up th
Werner Almesberger wrote:
> Amit D Chaudhary wrote:
>> But other information in the
>> initrd.txt mentions otherwise, hence the query here.
>
>
> Hmm, sounds like a bug. Where did you find this ?
I quote from the version in linux-2.4.2-ac22
"
Now, the initrd can be unmounted and the memory all
I'm annoyed when persons post virus alerts to unrelated lists but this
is a serious threat. If your offended flame away.
Bob
March 23, 2001 7:00 AM
Late last night, the SANS Institute (through its Global Incident
Analysis Center) uncovered a dangerous new worm that appears to be
spreading rapi
Hi David,
I did consider CRAMFS and JFFS2 when it was announced on the mtd list.
Conserving flash over system ram is more relevant. Our reasons are below:
RAMFS v/s CRAMFS
1. RAMFS is just more stable in terms of less complexity, less bugs reported
over the time, etc.
2. RAMFS is a fairly robu
Hi,
I am using an USB wacom intuos tablet on a dell laptop. Whenever the
laptop has been in standby mode the tablet does not work anymore.
More detailed, I was in X and submitted an 'apm --suspend' command. After
the resume I have to switch to a console (Ctrl-Alt-F3 for example), pull
the usb-
This sounds very nice.. can such a thing be done with the reset switch as
well?
Gerhard
On Fri, 23 Mar 2001, David Balazic wrote:
> I had a similar experience:
> X crashed , hosing the console , so I could not initiate
> a proper shutdown.
>
> Here I must note that the response you g
>I'm annoyed when persons post virus alerts to unrelated lists but this
>is a serious threat. If your offended flame away.
Since this worm exploits a BIND vulerability, it would be better placed on
the BIND mailing list than the kernel one. If it exploited a kernel bug,
then it would be more wel
On Fri, Mar 23, 2001 at 05:04:07PM +, Alan Cox wrote:
> > This is just an escape route in case everything else has failed.
> >
> > Linux is unreliable.
> > That is bad.
>
> Since your definition of reliability is a mathematical abstraction requiring
> infinite storage why don't you start by in
1 - 100 of 241 matches
Mail list logo
