Nick Piggin wrote:
The other nice thing about it was that it didn't have a hard
cutoff that the current reclaim_mapped toggle does -- you could
opt to scan the mapped list at a lower ratio than the unmapped
one. Of course, it also has some downsides too, and would
require retuning...
Here's a
I just encountered the following oops and general protection fault
trying to suspend/resume my laptop. I've got a Dell D820 laptop with a 2
GHz Core 2 Duo CPU. It usually suspends/resumes fine but not always. The
relevant errors are below but the full dmesg log is at
will be a device driver. Common causes of suspend/resume problems from
the list you give below are acpi modules, bluetooth and usb. I'd also be
consider pcmcia, drm and fuse possibilities. But again, go for unloading
everything possible in the first instance.
Actually, the reason I sent this
Hi,
(run echo 1 coremask, echo 0 coremask in a loop while dumping
core. Do you have enough locking to make it work as expected?)
Currently, any lock isn't acquired. But I think the kernel only
have to preserve the coremask setting in a local variable at the
begining of core dumping. I'm
Hi,
I was playing with user-mode Linux and found that mknod creates
devices node in hostfs with wrong major/minor numbers.
The patch below fixes it for me.
Johannes
---
mknod() is broken on UML because userspace has differernt
dev_t size and encoding than kernel.
Signed-off-by: Johannes
On Sun, 21 Jan 2007 14:27:34 -0500 (EST) Justin Piszcz [EMAIL PROTECTED]
wrote:
Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke
the OOM killer and kill all of my processes?
What's that? Software raid or hardware raid? If the latter, which driver?
Doing this
What's that? Software raid or hardware raid? If the latter, which
driver?
Software RAID (md)
On Mon, 22 Jan 2007, Andrew Morton wrote:
On Sun, 21 Jan 2007 14:27:34 -0500 (EST) Justin Piszcz [EMAIL PROTECTED]
wrote:
Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to
Justin Piszcz wrote:
My .config is attached, please let me know if any other information is
needed and please CC (lkml) as I am not on the list, thanks!
Running Kernel 2.6.19.2 on a MD RAID5 volume. Copying files over Samba to
the RAID5 running XFS.
Any idea what happened here?
On Monday January 22, [EMAIL PROTECTED] wrote:
Justin Piszcz wrote:
My .config is attached, please let me know if any other information is
needed and please CC (lkml) as I am not on the list, thanks!
Running Kernel 2.6.19.2 on a MD RAID5 volume. Copying files over Samba to
the RAID5
On Monday January 22, [EMAIL PROTECTED] wrote:
If the bitmap size is less than one page including super_block and
bitmap and the inode's i_blkbits is also small, when doing the
read_page function call to read the sb_page, it may return a error.
For example, if the device is 12800 chunks, its
On Mon 2007-01-22 13:48:44, Justin Piszcz wrote:
On Mon, 22 Jan 2007, Pavel Machek wrote:
On Sun 2007-01-21 14:27:34, Justin Piszcz wrote:
Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to
invoke
the OOM killer and kill all of my processes?
Doing this
Following are 4 patches suitable for inclusion in 2.6.20.
Thanks,
NeilBrown
[PATCH 001 of 4] md: Update email address and status for MD in MAINTAINERS.
[PATCH 002 of 4] md: Make 'repair' actually work for raid1.
[PATCH 003 of 4] md: Make sure the events count in an md array never returns
to
Signed-off-by: Neil Brown [EMAIL PROTECTED]
### Diffstat output
./MAINTAINERS |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff .prev/MAINTAINERS ./MAINTAINERS
--- .prev/MAINTAINERS 2007-01-23 11:14:14.0 +1100
+++ ./MAINTAINERS 2007-01-23 11:23:03.0
In most cases we check the size of the bitmap file before
reading data from it. However when reading the superblock,
we always read the first PAGE_SIZE bytes, which might not
always be appropriate. So limit that read to the size of the
file if appropriate.
Also, we get the count of available
Now that we sometimes step the array events count backwards
(when transitioning dirty-clean where nothing else interesting
has happened - so that we don't need to write to spares all the time),
it is possible for the event count to return to zero, which is
potentially confusing and triggers and
When 'repair' finds a block that is different one the various
parts of the mirror. it is meant to write a chosen good version
to the others. However it currently writes out the original data
to each. The memcpy to make all the data the same is missing.
Signed-off-by: Neil Brown [EMAIL
Andrew Morton wrote:
On Sun, 21 Jan 2007 14:27:34 -0500 (EST) Justin Piszcz [EMAIL PROTECTED]
wrote:
Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke
the OOM killer and kill all of my processes?
What's that? Software raid or hardware raid? If the latter, which
On Tue, 23 Jan 2007 11:37:09 +1100
Donald Douwsma [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
On Sun, 21 Jan 2007 14:27:34 -0500 (EST) Justin Piszcz [EMAIL PROTECTED]
wrote:
Why does copying an 18GB on a 74GB raptor raid1 cause the kernel to invoke
the OOM killer and kill all of my
I think your patch is not enough to slove the read_page error
completely. I think in the bitmap_init_from_disk we also need to check
the 'count' never exceeds the size of file before calling the
read_page function. How do your think about it.
Thanks your reply.
2007/1/23, Neil Brown [EMAIL
On 1/22/07, Neil Brown [EMAIL PROTECTED] wrote:
On Monday January 22, [EMAIL PROTECTED] wrote:
Justin Piszcz wrote:
My .config is attached, please let me know if any other information is
needed and please CC (lkml) as I am not on the list, thanks!
Running Kernel 2.6.19.2 on a MD RAID5
On Monday January 22, [EMAIL PROTECTED] wrote:
On 1/22/07, Neil Brown [EMAIL PROTECTED] wrote:
On Monday January 22, [EMAIL PROTECTED] wrote:
Justin Piszcz wrote:
My .config is attached, please let me know if any other information is
needed and please CC (lkml) as I am not on the
From: Dan Williams [EMAIL PROTECTED]
* introduce struct dma_async_tx_descriptor as a common field for all dmaengine
software descriptors
* convert the device_memcpy_* methods into separate prep, set src/dest, and
submit stages
* support capabilities beyond memcpy (xor, memset, xor zero sum,
From: Dan Williams [EMAIL PROTECTED]
async_tx is an api to describe a series of bulk memory
transfers/transforms. When possible these transactions are carried out by
asynchrounous dma engines. The api handles inter-transaction dependencies
and hides dma channel management from the client. When
From: Dan Williams [EMAIL PROTECTED]
The parity calculation for an expansion operation is the same as the
calculation performed at the end of a write with the caveat that all blocks
in the stripe are scheduled to be written. An expansion operation is
identified as a stripe with the POSTXOR flag
From: Dan Williams [EMAIL PROTECTED]
handle_stripe sets STRIPE_OP_CHECK to request a check operation in
raid5_run_ops. If raid5_run_ops is able to perform the check with a
dma engine the parity will be preserved in memory removing the need to
re-read it from disk, as is necessary in the
From: Dan Williams [EMAIL PROTECTED]
This is a driver for the iop DMA/AAU/ADMA units which are capable of pq_xor,
pq_update, pq_zero_sum, xor, dual_xor, xor_zero_sum, fill, copy+crc, and copy
operations.
Changelog:
* fixed a slot allocation bug in do_iop13xx_adma_xor that caused too few
slots to
From: Dan Williams [EMAIL PROTECTED]
Use raid5_run_ops to carry out the memory copies for a raid5 read request.
Signed-off-by: Dan Williams [EMAIL PROTECTED]
---
drivers/md/raid5.c | 40 +++-
1 files changed, 15 insertions(+), 25 deletions(-)
diff --git
From: Dan Williams [EMAIL PROTECTED]
replaced by raid5_run_ops
Signed-off-by: Dan Williams [EMAIL PROTECTED]
---
drivers/md/raid5.c | 124
1 files changed, 0 insertions(+), 124 deletions(-)
diff --git a/drivers/md/raid5.c
From: Dan Williams [EMAIL PROTECTED]
handle_stripe now only updates the state of stripes. All execution of
operations is moved to raid5_run_ops.
Signed-off-by: Dan Williams [EMAIL PROTECTED]
---
drivers/md/raid5.c | 68
1 files changed,
From: Dan Williams [EMAIL PROTECTED]
Each stripe has three flag variables to reflect the state of operations
(pending, ack, and complete).
-pending: set to request servicing in raid5_run_ops
-ack: set to reflect that raid5_runs_ops has seen this request
-complete: set when the operation is
From: Dan Williams [EMAIL PROTECTED]
Prepare the raid5 implementation to use async_tx for running stripe
operations:
* biofill (copy data into request buffers to satisfy a read request)
* compute block (generate a missing block in the cache from the other
blocks)
* prexor (subtract existing data
From: Dan Williams [EMAIL PROTECTED]
handle_stripe sets STRIPE_OP_COMPUTE_BLK to request servicing from
raid5_run_ops. It also sets a flag for the block being computed to let
other parts of handle_stripe submit dependent operations. raid5_run_ops
guarantees that the compute operation completes
From: Dan Williams [EMAIL PROTECTED]
handle_stripe sets STRIPE_OP_PREXOR, STRIPE_OP_BIODRAIN, STRIPE_OP_POSTXOR
to request a write to the stripe cache. raid5_run_ops is triggerred to run
and executes the request outside the stripe lock.
Signed-off-by: Dan Williams [EMAIL PROTECTED]
---
On Thu, 18 Jan 2007, Andi Kleen wrote:
let me know what you think... thanks.
It's ok, although I would like to have the file in a separate directory.
cool -- do you have a directory in mind?
and would you like this change as two separate patches or one combined
patch?
thanks
-dean
-
To
Björn Steinbrink wrote:
Hm, I don't think it is unhappy about looking at NV_INT_STATUS_CK804.
I'm running 2.6.20-rc5 with the INT_DEV check removed for 8 hours now
without a single problem and that should still look at
NV_INT_STATUS_CK804, right?
I just noticed that my last email might not have
re-code my patch, tab = 8. Sorry!
Signed-off-by: Yunfeng Zhang [EMAIL PROTECTED]
Index: linux-2.6.19/Documentation/vm_pps.txt
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ linux-2.6.19/Documentation/vm_pps.txt
Nick Piggin wrote:
Balbir Singh wrote:
This makes me wonder if it makes sense to split up the LRU into page
cache LRU and mapped pages LRU. I see two benefits
1. Currently based on swappiness, we might walk an entire list
searching for page cache pages or mapped pages. With these
lists
Remove bits left over from prior ftape removal.
Please pull from 'ftape' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git ftape
to receive the following updates:
include/linux/Kbuild |1 -
include/linux/mtio.h | 146
On Mon, 2007-01-22 at 09:57 +0100, Xavier Roche wrote:
Hi folks,
I have a probably louzy question regarding sigaction() behaviour when an
alternate signal stack is used: it seems that I can not get the user
stack reference in the ucontext_t stack context ; ie. the uc_stack
member contains
Rik van Riel wrote:
Nick Piggin wrote:
The other nice thing about it was that it didn't have a hard
cutoff that the current reclaim_mapped toggle does -- you could
opt to scan the mapped list at a lower ratio than the unmapped
one. Of course, it also has some downsides too, and would
require
This patchset represents the most stable clocksource changes in my tree. Also
John (and others) have reviewed these changes a few times. I think it's all
acceptable.
Daniel
--
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Move the generic timekeeping code from kernel/timer.c to
kernel/time/timekeeping.c . This requires some glue code which is
added to the include/linux/timekeeping.h header.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
include/linux/clocksource.h |3
include/linux/timekeeping.h | 19
Adds a call back interface for register/rating change events. This is also used
later in this series to signal other interesting events.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
include/linux/clocksource.h | 37 +
include/linux/timekeeping.h |
Update drivers/clocksource/ with list initialization.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
drivers/clocksource/acpi_pm.c|1 +
drivers/clocksource/cyclone.c|1 +
drivers/clocksource/scx200_hrt.c |1 +
3 files changed, 3 insertions(+)
Index:
A change to clocksource initialization. If the list field is initialized
it allows clocksource_register to complete faster since it doesn't have
to scan the list of clocks doing strcmp on each looking for duplicates.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
kernel/time/clocksource.c
Update arch/x86_64/ with list initialization.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
arch/x86_64/kernel/hpet.c |1 +
arch/x86_64/kernel/tsc.c |1 +
2 files changed, 2 insertions(+)
Index: linux-2.6.19/arch/x86_64/kernel/hpet.c
Update arch/i386/ with list initialization.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
arch/i386/kernel/hpet.c |1 +
arch/i386/kernel/i8253.c |1 +
arch/i386/kernel/tsc.c |1 +
3 files changed, 3 insertions(+)
Index: linux-2.6.19/arch/i386/kernel/hpet.c
Update arch/mips/ with list initialization.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
arch/mips/kernel/time.c |1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.19/arch/mips/kernel/time.c
===
---
Update arch/avre32/ with list initialization.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
arch/avr32/kernel/time.c |1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.19/arch/avr32/kernel/time.c
===
---
Update arch/arm/ with list initialization.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
arch/arm/mach-imx/time.c |1 +
arch/arm/mach-ixp4xx/common.c |1 +
arch/arm/mach-netx/time.c |1 +
arch/arm/mach-pxa/time.c |1 +
4 files changed, 4 insertions(+)
Index:
Converts the original plain list into a sorted list based on the clock rating.
Later in my tree this allows some of the variables to be dropped since the
highest rated clock is always at the front of the list. This also does some
other nice things like allow the sysfs files to print the clocks in
Modifies the way clocks are switched to in the timekeeping code. The original
code would constantly monitor the clocksource list checking for newly added
clocksources. I modified this by using atomic types to signal when a new clock
is added. This allows the operation to be used only when it's
Uses the block notifier to replace the functionality of update_callback().
update_callback() was a special case specifically for the tsc, but including
it in the clocksource structure duplicated it needlessly for other clocks.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
---
Bisection shows the bad patch to be:
gregkh-driver-uio-documentation.patch
The htmldocs build failure can be eliminated by:
quilt remove Documentation/DocBook/kernel-api.tmpl
The error messages were:
.../linux-2.6.19 $ make htmldocs
DOCPROC
On 2006-12-29, Tim Schmielau wrote:
[]
OK, building 2.6.20-rc2-mm1 with all 59 configs from arch/arm/configs
with and w/o the patch indeed found one mysterious #include that may not
be removed. Thanks, Russell!
Andrew, please use the attached patch instead of the previous one, it also
has
Soeren Sonnenburg wrote:
OK, how about this (please especially check the non SIL part):
SATA Hotplug from the User Side
- For SIL3114 and SIL3124 you don't have to run any commands at all. It
ahci and ck804 flavor of sata_nv's can do hotplug without user
assistance too.
[--snip--]
- For
On 2006-12-13, Robert P. J. Day wrote:
Replace the very few remaining depends Kconfig directives with
depends on.
Signed-off-by: Robert P. J. Day [EMAIL PROTECTED]
---
For this kind of fixes, please use
kconfig subsystem instead of
kbuild in subject. Thanks.
-
To unsubscribe from
Henrique de Moraes Holschuh wrote:
Does SATA electrical conector keying let the disk firmware unload
heads before the user manages to pull it out enough to sever power?
I don't think so.
If it does not, the drive will do an emergency head unload, which is
not good and will likely reduce the
On Mon, 22 Jan 2007 22:02:30 -0800 Don Mullis wrote:
Bisection shows the bad patch to be:
gregkh-driver-uio-documentation.patch
The htmldocs build failure can be eliminated by:
quilt remove Documentation/DocBook/kernel-api.tmpl
or by: quilt delete
On Mon, Jan 22, 2007 at 10:02:30PM -0800, Don Mullis wrote:
Bisection shows the bad patch to be:
gregkh-driver-uio-documentation.patch
The htmldocs build failure can be eliminated by:
quilt remove Documentation/DocBook/kernel-api.tmpl
The error messages were:
On Mon, 2007-01-22 at 22:22 -0800, Randy Dunlap wrote:
On Mon, 22 Jan 2007 22:02:30 -0800 Don Mullis wrote:
Bisection shows the bad patch to be:
gregkh-driver-uio-documentation.patch
The htmldocs build failure can be eliminated by:
quilt remove
JFFS is already marked CONFIG_BROKEN in fs/Kconfig, with a note that
it's going away in 2.6.21, but the corresponding update to
feature-removal-schedule.txt was accidentally omitted. Fixed.
Please pull from 'kill-jffs-prep' branch of
Hi Dann,
On Mon, Jan 22, 2007 at 11:19:43AM -0700, dann frazier wrote:
On Mon, Jan 22, 2007 at 10:50:47AM +1100, Grant Coady wrote:
On Mon, 22 Jan 2007 00:03:21 +0100, Willy Tarreau [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:/home/other$ uname -r
2.4.34b
[EMAIL PROTECTED]:/home/other$
Avi Kivity [EMAIL PROTECTED] wrote:
A g constraint may place a local variable in an %rsp-relative memory
operand.
but if your assembly changes %rsp, the operand points to the wrong location.
An r constraint fixes that.
Thanks to Ingo Molnar for neatly bisecting the problem.
what about removing psmouse module?
On 1/23/07, Jean-Marc Valin [EMAIL PROTECTED] wrote:
will be a device driver. Common causes of suspend/resume problems from
the list you give below are acpi modules, bluetooth and usb. I'd also be
consider pcmcia, drm and fuse possibilities. But again, go
On 2006-11-17, Oleg Verych wrote:
On Tue, Oct 31, 2006 at 02:51:36PM +0100, olecom wrote:
[]
On Tue, Oct 31, 2006 at 02:14:16AM +0100, Horst Schirmeier wrote:
[]
I'm not sure what you mean by $(objdir); I just got something to work
which creates the /dev/null symlink in a (newly created if
Zan Lynx wrote:
I have been running 2.6.20-rc2-mm1 without problems, but both rc3-mm1
and rc4-mm1 have been giving me these freezes. They were happening
inside X and without external console it was impossible to get anything,
plus I was reluctant to test it since the freeze sometimes requires a
601 - 667 of 667 matches
Mail list logo