I'll try to remove it again for 3.7
Helge Hafting
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
try to remove it again for 3.7
Helge Hafting
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-bit 3.5.4 or 3.6.0
Distro: funtoo
Audio according to lspci:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family
High Definition Audio Controller (rev 04)
Please tell if there is anything I should try. I can test other kernel versions
or try patches.
Helge Hafting
--
To unsubs
or 3.6.0
Distro: funtoo
Audio according to lspci:
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family
High Definition Audio Controller (rev 04)
Please tell if there is anything I should try. I can test other kernel versions
or try patches.
Helge Hafting
--
To unsubscribe from
ade available to
them_,
then increase the processor speed.
The cputime allocated to niced tasks (that may be cpu intensive but
shouldn't
cause max speed on their own) won't matter then.
Helge Hafting
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
for the root
device and root fs is built-in, and you can drop the initrd.
Takes a second or two off the boot, and some more off the build.
Helge Hafting
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
available to
them_,
then increase the processor speed.
The cputime allocated to niced tasks (that may be cpu intensive but
shouldn't
cause max speed on their own) won't matter then.
Helge Hafting
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
for the root
device and root fs is built-in, and you can drop the initrd.
Takes a second or two off the boot, and some more off the build.
Helge Hafting
--
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
an option.
Helge Hafting
--
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/
. The boot failed, reboot with init=/bin/sh
and replace the dysfunctional labels with oldfashioned device names.
I can live with this kind of problem on my desktop, but this machine
was going to be a internet router for a customer, so occational
boot failure requiring intervention was not an option.
Helge
count the unrealistic option
of using generic 2MB pages.
Having said that, it is possible to get a feel of what a 8kB page system
will be like on intel, by always allocating pages in pairs.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
count the unrealistic option
of using generic 2MB pages.
Having said that, it is possible to get a feel of what a 8kB page system
will be like on intel, by always allocating pages in pairs.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
etc.) can run on another system with lesser memory.
You can test this directly.
Boot your 2G machine with
mem=
Then the machine uses less memory, you get
a realistic test of how the smaller machine will
perform.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe
for anyone capable of making the driver in
the first place. Modularity and firmware loading
are not connected. One is for kernel flexibility, the other
is for making a particular device work.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
for anyone capable of making the driver in
the first place. Modularity and firmware loading
are not connected. One is for kernel flexibility, the other
is for making a particular device work.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
etc.) can run on another system with lesser memory.
You can test this directly.
Boot your 2G machine with
mem=size of smaller system
Then the machine uses less memory, you get
a realistic test of how the smaller machine will
perform.
Helge Hafting
-
To unsubscribe from this list: send the line
Jarek Poplawski wrote:
On Fri, Oct 12, 2007 at 02:44:51PM +0200, Helge Hafting wrote:
...
The point is that we _trust_ intel when they says "this will work".
Therefore, we can use the optimizations. It was never about
legal matters. If we didn't trust intel, then we co
Jarek Poplawski wrote:
On Fri, Oct 12, 2007 at 02:44:51PM +0200, Helge Hafting wrote:
...
The point is that we _trust_ intel when they says this will work.
Therefore, we can use the optimizations. It was never about
legal matters. If we didn't trust intel, then we couldn't
use
Jarek Poplawski wrote:
On Fri, Oct 12, 2007 at 10:42:34AM +0200, Helge Hafting wrote:
Jarek Poplawski wrote:
On 04-10-2007 07:23, Nick Piggin wrote:
According to latest memory ordering specification documents from Intel and
AMD, both manufacturers are committed to in-order
know, so now we may optimize.
Helge Hafting
-
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/
optimize.
Helge Hafting
-
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/
Jarek Poplawski wrote:
On Fri, Oct 12, 2007 at 10:42:34AM +0200, Helge Hafting wrote:
Jarek Poplawski wrote:
On 04-10-2007 07:23, Nick Piggin wrote:
According to latest memory ordering specification documents from Intel and
AMD, both manufacturers are committed to in-order
mine. mini-itx.com seems to get this right.
Helge Hafting
-
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/
seems to get this right.
Helge Hafting
-
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/
Thomas Gleixner wrote:
On Sat, 29 Sep 2007, Helge Hafting wrote:
Thomas Gleixner wrote:
I have gone back to 2.6.22rc4, which seems to work.
This is a single opteron, although on a dual-slot board.
Can you switch to serial console, so we can get some information out
Adrian Bunk wrote:
On Tue, Oct 09, 2007 at 12:00:38AM +0200, Helge Hafting wrote:
CC drivers/video/fbmon.o
drivers/video/fbmon.c: In function ‘fb_parse_edid’:
drivers/video/fbmon.c:867: error: expected ‘=’, ‘,’, ‘;’,
‘asm’ or ‘__attrib
_’ before ‘*’ token
drivers/video/fbmon.c:867
$*block;
Source error, or is my tree simply corrupt?
Helge Hafting
-
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/
happen.
Helge Hafting
-
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/
happen.
Helge Hafting
-
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/
$*block;
Source error, or is my tree simply corrupt?
Helge Hafting
-
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/
Adrian Bunk wrote:
On Tue, Oct 09, 2007 at 12:00:38AM +0200, Helge Hafting wrote:
CC drivers/video/fbmon.o
drivers/video/fbmon.c: In function ‘fb_parse_edid’:
drivers/video/fbmon.c:867: error: expected ‘=’, ‘,’, ‘;’,
‘asm’ or ‘__attrib
_’ before ‘*’ token
drivers/video/fbmon.c:867
Thomas Gleixner wrote:
On Sat, 29 Sep 2007, Helge Hafting wrote:
Thomas Gleixner wrote:
I have gone back to 2.6.22rc4, which seems to work.
This is a single opteron, although on a dual-slot board.
Can you switch to serial console, so we can get some information out
Andi Kleen wrote:
Helge Hafting <[EMAIL PROTECTED]> writes:
shrink_dcache_memory
That usually means random memory corruption from somewhere -- dcache
tends to use a lot of memory and when it is corrupted anywhere these
functions tend to crash while walking the lists.
Unfortu
Andi Kleen wrote:
Helge Hafting [EMAIL PROTECTED] writes:
shrink_dcache_memory
That usually means random memory corruption from somewhere -- dcache
tends to use a lot of memory and when it is corrupted anywhere these
functions tend to crash while walking the lists.
Unfortunately
unning.)
Helge Hafting
-
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/
.)
Helge Hafting
-
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/
Andi Kleen wrote:
Helge Hafting <[EMAIL PROTECTED]> writes:
shrink_dcache_memory
That usually means random memory corruption from somewhere -- dcache
tends to use a lot of memory and when it is corrupted anywhere these
functions tend to crash while walking the lists.
Unfortu
Andi Kleen wrote:
Helge Hafting [EMAIL PROTECTED] writes:
shrink_dcache_memory
That usually means random memory corruption from somewhere -- dcache
tends to use a lot of memory and when it is corrupted anywhere these
functions tend to crash while walking the lists.
Unfortunately
Thomas Gleixner wrote:
On Sat, 29 Sep 2007, Helge Hafting wrote:
Thomas Gleixner wrote:
I have gone back to 2.6.22rc4, which seems to work.
This is a single opteron, although on a dual-slot board.
Can you switch to serial console, so we can get some information out
Thomas Gleixner wrote:
On Sat, 29 Sep 2007, Helge Hafting wrote:
Thomas Gleixner wrote:
I have gone back to 2.6.22rc4, which seems to work.
This is a single opteron, although on a dual-slot board.
Can you switch to serial console, so we can get some information out
Thomas Gleixner wrote:
On Mon, 2007-09-24 at 23:08 +0200, Helge Hafting wrote:
The two kernels mentioned hangs occationally.
Typically when I compile something and pass the time
by surfing the web.
A few minutes and then I notice that the mouse (and everything else in X)
stops. kbd LEDs
Thomas Gleixner wrote:
On Mon, 2007-09-24 at 23:08 +0200, Helge Hafting wrote:
The two kernels mentioned hangs occationally.
Typically when I compile something and pass the time
by surfing the web.
A few minutes and then I notice that the mouse (and everything else in X)
stops. kbd LEDs
etwork driver, it is a protocol. You might be able to remove it
if you zap
all the routes and applications, ...
Wouldn't it be enough to down all the interfaces and close all the sockets?
No need to bring down every app.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubs
, it is a protocol. You might be able to remove it
if you zap
all the routes and applications, ...
Wouldn't it be enough to down all the interfaces and close all the sockets?
No need to bring down every app.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
this has happened while running X, so no messages.
I have gone back to 2.6.22rc4, which seems to work.
This is a single opteron, although on a dual-slot board.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
this has happened while running X, so no messages.
I have gone back to 2.6.22rc4, which seems to work.
This is a single opteron, although on a dual-slot board.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Jacob Meuser wrote:
On Mon, Sep 17, 2007 at 09:47:43AM +0200, Helge Hafting wrote:
Your problem seems to be with the BSD licence,
and the power to alter that licence lies in the BSD community.
I hope you can understand that this mentality is _exactly_ what has
some in the BSD
Jacob Meuser wrote:
On Mon, Sep 17, 2007 at 09:47:43AM +0200, Helge Hafting wrote:
Your problem seems to be with the BSD licence,
and the power to alter that licence lies in the BSD community.
I hope you can understand that this mentality is _exactly_ what has
some in the BSD
in the BSD community.
Helge Hafting
-
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/
community.
Helge Hafting
-
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/
.
That is what memory with parity is for. Don't know if
that exists for laptops though.
Helge Hafting
-
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 re
opup -
every time - whether he needs the warning or not.
But feel free to print a warning somewhere, such as a
status line. The warning itself is useful, but not something
we will have to dismiss in order to go on with the job.
Helge Hafting
-
To unsubscribe from this list: send the line "un
-
every time - whether he needs the warning or not.
But feel free to print a warning somewhere, such as a
status line. The warning itself is useful, but not something
we will have to dismiss in order to go on with the job.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe
.
That is what memory with parity is for. Don't know if
that exists for laptops though.
Helge Hafting
-
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
ings duplicated in userspace" so
they too merge in the same way.
Helge Hafting
-
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/
so
they too merge in the same way.
Helge Hafting
-
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/
Xavier Bestel wrote:
On Thu, 2007-08-30 at 15:55 +0200, Helge Hafting wrote:
If the swap device is full, then there is no need for random
seeks as the swap pages can be read in disk order.
If the swap file is full, you probably have a machine dead into a swap
storm.
Only if you have
swap will skip over the unused areas, the time
needed should still be limited to the time needed for reading the
whole swap device.
If this optimization is worth it is another problem though.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
swap will skip over the unused areas, the time
needed should still be limited to the time needed for reading the
whole swap device.
If this optimization is worth it is another problem though.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Xavier Bestel wrote:
On Thu, 2007-08-30 at 15:55 +0200, Helge Hafting wrote:
If the swap device is full, then there is no need for random
seeks as the swap pages can be read in disk order.
If the swap file is full, you probably have a machine dead into a swap
storm.
Only if you have
something that isn't flawed, that is well planned, not
just a bunch of "well - we could do *that* perhaps" but then
it turns out that *that* idea was flawed as well.
Helge Hafting
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
flawed, that is well planned, not
just a bunch of well - we could do *that* perhaps but then
it turns out that *that* idea was flawed as well.
Helge Hafting
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
already.
Now, linux is open-source, so you can of course use it as a
starting point for your different system. Then you can compete
with "standard linux" - see who attracts most developers and
most users in the long run.
Helge Hafting
-
To unsubscribe from this list: send the line "un
ay and then I figure out
how.
Sure - you don't have to prove that it will work now.
Working it out over time and then showing us is ok.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordo
good idea. atimes will then be written only by
memory pressure - or umount. The atimes could be wrong after
a crash, but loosing atimes only is not something
I'd worry about.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [E
will then be written only by
memory pressure - or umount. The atimes could be wrong after
a crash, but loosing atimes only is not something
I'd worry about.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
.
Sure - you don't have to prove that it will work now.
Working it out over time and then showing us is ok.
Helge Hafting
-
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
is open-source, so you can of course use it as a
starting point for your different system. Then you can compete
with standard linux - see who attracts most developers and
most users in the long run.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
, I would be fine disabling the Page Cache altogether as well.
Assuming what you really mean is that you don't want to cache
file i/o for that process - try opening files with O_DIRECT.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" i
to the handfull
of distributions that matter to update their defaults.
Indeed. Just change /bin/mount so it defaults to "noatime"
unless there is an explicit "atime". Similiar for diratime.
Problem solved.
Helge Hafting
-
To unsubscribe from this list: send the line "
to the handfull
of distributions that matter to update their defaults.
Indeed. Just change /bin/mount so it defaults to noatime
unless there is an explicit atime. Similiar for diratime.
Problem solved.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
, I would be fine disabling the Page Cache altogether as well.
Assuming what you really mean is that you don't want to cache
file i/o for that process - try opening files with O_DIRECT.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Matthew Hawkins wrote:
updatedb by itself doesn't really bug me, its just that on occasion
its still running at 7am
You should start it earlier then - assuming it doesn't
already start at the earliest opportunity?
Helge Hafting
-
To unsubscribe from this list: send the line "unsubs
Matthew Hawkins wrote:
updatedb by itself doesn't really bug me, its just that on occasion
its still running at 7am
You should start it earlier then - assuming it doesn't
already start at the earliest opportunity?
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux
compiling linux for BIOS usage is targetting
a single machine. So an ability to target a single machine is useful,
i.e. run the CPUID at compile-time, put the answer in a constant/macro,
let the optimizer prune the alternatives. :-)
Helge Hafting
-
To unsubscribe from this list: send the line &q
ng fancy. Could the kernel support a way to do this?
The normal way is to set permissions on the device in
question - give either root only or the logged-in user
write access as needed.
It seems to me that "loadkeys" uses /dev/tty / /dev/tty0
So set permissions on that as needed.
then read whatever you want from that page. Nothing is ever accessed
by physical address, physical addresses is only used indirectly
to set up the page tables.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTE
then read whatever you want from that page. Nothing is ever accessed
by physical address, physical addresses is only used indirectly
to set up the page tables.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
a way to do this?
The normal way is to set permissions on the device in
question - give either root only or the logged-in user
write access as needed.
It seems to me that loadkeys uses /dev/tty / /dev/tty0
So set permissions on that as needed.
Helge Hafting
-
To unsubscribe from this list: send
linux for BIOS usage is targetting
a single machine. So an ability to target a single machine is useful,
i.e. run the CPUID at compile-time, put the answer in a constant/macro,
let the optimizer prune the alternatives. :-)
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux
will take some effort of course;
but once it is done, you're protected from module API changes. . .
Helge Hafting
-
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
will take some effort of course;
but once it is done, you're protected from module API changes. . .
Helge Hafting
-
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
upposed to work fine,
but you must upgrade the whole kernel then. This includes
all driver modules. An older module may not work,
or it may even hang the kernel immediately. You can't
generally put together pieces of different kernels - the kernel
is one piece. (Other pieces of a linux system
generally put together pieces of different kernels - the kernel
is one piece. (Other pieces of a linux system is the
various packages your distribution vendor ships . . .)
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
to see how the Linux kernel itself compares to other Unix kernels
(*BSD, Solaris, AIX, etc) in terms of *real* innovation.
It certainly has an innovative licence - which is why
it is attracting developers and replacing most of those other unices . . .
Helge Hafting
-
To unsubscribe from this list
know what is needed, they can write their programs so they set useful
priorities.
Helge Hafting
-
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.htm
rk with vista either - unless
the device is extremely mainstream. For all other devices,
the device manufacturer have to provide updated drivers.
If your vendor don't want to support you anymore, try getting
the source.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubsc
devices,
the device manufacturer have to provide updated drivers.
If your vendor don't want to support you anymore, try getting
the source.
Helge Hafting
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
write their programs so they set useful
priorities.
Helge Hafting
-
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
to see how the Linux kernel itself compares to other Unix kernels
(*BSD, Solaris, AIX, etc) in terms of *real* innovation.
It certainly has an innovative licence - which is why
it is attracting developers and replacing most of those other unices . . .
Helge Hafting
-
To unsubscribe from this list
box after the sale is
their risk, and there is nothing unfair about failure here.
Helge Hafting
-
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
this
automatically?)
An extra bootscript seems better than loosing memory.
Helge Hafting
-
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 FA
for all VT's and so on.
In the multiseat case there are several possibly dissimiliar
keyboards, but then they have separate event devices too.
Helge Hafting
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo i
on.
In the multiseat case there are several possibly dissimiliar
keyboards, but then they have separate event devices too.
Helge Hafting
-
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
this
automatically?)
An extra bootscript seems better than loosing memory.
Helge Hafting
-
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
the sale is
their risk, and there is nothing unfair about failure here.
Helge Hafting
-
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
llocations that the oom-killer would have stepped in without swap.
You can then monitor swapping. If anything is written to swap,
then you're using too much memory and should investigate.
For production, this is usually better than cleaning up after
the oom-killer busted some random processes.
have stepped in without swap.
You can then monitor swapping. If anything is written to swap,
then you're using too much memory and should investigate.
For production, this is usually better than cleaning up after
the oom-killer busted some random processes.
Helge Hafting
-
To unsubscribe from
tion error instead of
triggering the oom-killer.
Helge Hafting
-
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/
still so no extra cooling. So it burns out.
Helge Hafting
-
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/
1 - 100 of 558 matches
Mail list logo
