On Mon, 2007-01-15 at 21:47 -0800, Christoph Lameter wrote:
> Currently cpusets are not able to do proper writeback since
> dirty ratio calculations and writeback are all done for the system
> as a whole. This may result in a large percentage of a cpuset
> to become dirty without writeout being tri
I have a PCI-E pro/1000 MT Quad Port adapter, which works quite well
under 2.6.19.2 but fails to see link under 2.6.20-rc5. Earlier today I
reported this to [EMAIL PROTECTED], but thought I should get the
word out in case someone else is testing this kernel on this nic chipset.
Due to changes
On Monday 15 January 2007 5:54 pm, Nate Diller wrote:
> This removes the aio implementation from the usb gadget file system.
NAK. I see a deep mis-understanding here.
> Aside
> from making very creative (!) use of the aio retry path, it can't be of any
> use performance-wise
Other than the
On Monday 15 January 2007 5:54 pm, Nate Diller wrote:
> --- a/drivers/usb/gadget/inode.c 2007-01-12 14:42:29.0 -0800
> +++ b/drivers/usb/gadget/inode.c 2007-01-12 14:25:34.0 -0800
> @@ -559,35 +559,32 @@ static int ep_aio_cancel(struct kiocb *i
> return value;
> }
>
On Mon, 2007-01-15 at 18:26 -0500, Daniel Drake wrote:
> Hi,
>
> Tim Ryan has reported the following bug at the Gentoo bugzilla:
>
> https://bugs.gentoo.org/show_bug.cgi?id=162199
>
> His home dir is mounted over NFS. 2.6.18 worked OK but 2.6.19 is very
> slow to load the desktop environment. N
This patch replace kmalloc() + memset() pairs with the appropriate
kzalloc().
Signed-off-by: Joe Jin <[EMAIL PROTECTED]>
--- drivers/net/slip.c.orig 2007-01-16 14:21:52.0 +0800
+++ drivers/net/slip.c 2007-01-16 14:23:07.0 +0800
@@ -1343,15 +1343,12 @@
printk(KERN_INFO
[PATCH 05/06]
This patch introduces all that is needed to process per namespace tunables.
Signed-off-by: Nadia Derbey <[EMAIL PROTECTED]>
---
include/linux/akt.h | 12 +++
kernel/autotune/akt.c | 80 ++
2 files changed, 73 insertions(
[PATCH 06/06]
The following kernel components register a tunable structure and call the
auto-tuning routine:
. file system
. shared memory (per namespace)
. semaphore (per namespace)
. message queues (per namespace)
Signed-off-by: Nadia Derbey <[EMAIL PROTECTED]>
---
fs/file_table.c
[PATCH 04/06]
Introduces the kobjects associated to each tunable min and max value
Signed-off-by: Nadia Derbey <[EMAIL PROTECTED]>
---
include/linux/akt.h | 30
include/linux/akt_ops.h | 311
kernel/autotune/akt.c | 120
[PATCH 02/06]
Introduces the auto-tuning activation routine
The auto-tuning routine is called by the fork kernel component
Signed-off-by: Nadia Derbey <[EMAIL PROTECTED]>
---
include/linux/akt.h | 50 ++
kernel/exit.c | 11 +++
[PATCH 03/06]
Introduces the kobjects associated to each tunable and the sysfs registration
Signed-off-by: Nadia Derbey <[EMAIL PROTECTED]>
---
include/linux/akt.h | 25 -
init/main.c |1
kernel/autotune/Makefile|2
kernel/autotune/akt.c |
[PATCH 01/06]
Defines the auto_tune structure: this is the structure that contains the
information needed by the adjustment routine for a given tunable.
Also defines the registration routines.
The fork kernel component defines a tunable structure for the threads-max
tunable and registers it.
Si
This is a series of patches that introduces a feature that makes the kernel
automatically change the tunables values as it sees resources running out.
The AKT framework is made of 2 parts:
1) Kernel part:
Interfaces are provided to the kernel subsystems, to (un)register the
tunables that might be
On Sat, Jan 13, 2007 at 08:11:25AM +0100, Adrian Bunk wrote:
> On Fri, Jan 12, 2007 at 02:27:48PM -0500, Linus Torvalds wrote:
> >...
> > A lot of developers (including me) will be gone next week for
> > Linux.Conf.Au, so you have a week of rest and quiet to test this, and
> > report any problems
Remove Kconfig entries (and some documentation) for apparently
"dead" config variables.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
A script I threw together identified the following as apparently
useless config variables. By "useless," I mean that they:
1) aren't consulted
Make page writeback obey cpuset constraints
Currently dirty throttling does not work properly in a cpuset.
If f.e a cpuset contains only 1/10th of available memory then all of the
memory of a cpuset can be dirtied without any writes being triggered. If we
are writing to a device that is mounted v
Throttle VM writeout in a cpuset aware way
This bases the vm throttling from the reclaim path on the dirty ratio
of the cpuset. Note that a cpuset is only effective if shrink_zone is called
from direct reclaim.
kswapd has a cpuset context that includes the whole machine and will
therefore not thr
Consider unreclaimable pages during dirty limit calculation
Tracking unreclaimable pages helps us to calculate the dirty ratio
the right way. If a large number of unreclaimable pages are allocated
(through the slab or through huge pages) then write throttling will
no longer work since the limit ca
pdflush: Allow the passing of a nodemask parameter
If we want to support nodeset specific writeout then we need a way
to communicate the set of nodes that an operation should affect.
So add a nodemask_t parameter to the pdflush functions and also
store the nodemask in the pdflush control structur
Dynamically reduce the size of the nodemask_t in struct inode
The nodemask_t in struct inode can potentially waste a lot of memory if
MAX_NUMNODES is high. For IA64 MAX_NUMNODES is 1024 by default which
results in 128 bytes to be used for the nodemask. This means that the
memory use for inodes may
Add a dirty map to the inode
In a NUMA system it is helpful to know where the dirty pages of a mapping
are located. That way we will be able to implement writeout for applications
that are constrained to a portion of the memory of the system as required by
cpusets.
Two functions are introduced to
Direct reclaim: cpuset aware writeout
During direct reclaim we traverse down a zonelist and are carefully
checking each zone if its a member of the active cpuset. But then we call
pdflush without enforcing the same restrictions. In a larger system this
may have the effect of a massive amount of pa
Currently cpusets are not able to do proper writeback since
dirty ratio calculations and writeback are all done for the system
as a whole. This may result in a large percentage of a cpuset
to become dirty without writeout being triggered. Under NFS
this can lead to OOM conditions.
Writeback will o
Replace highest_possible_node_id() with nr_node_ids
highest_possible_node_id() is used to calculate the last possible node id
so that the network subsystem can figure out how to size per node arrays.
I think having the ability to determine the maximum amount of nodes in
a system at runtime is use
On Mon, 15 Jan 2007 17:54:50 -0800
Nate Diller <[EMAIL PROTECTED]> wrote:
> Remove unused arg from socket operations
>
> The sendmsg and recvmsg socket operations take a kiocb pointer, but none of
> the functions actually use it. There's really no need even theoretically,
> it's really quite ugl
On 1/15/07, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
On Mon, Jan 15, 2007 at 05:54:50PM -0800, Nate Diller wrote:
> Convert code using iocb->ki_left to use the more generic iov_length() call.
No way. We need to reduce the numer of iovec traversals, not adding
more of them.
ok, I can work
On Mon, Jan 15, 2007 at 07:55:16PM +0300, Oleg Nesterov wrote:
> > What if 'singlethread_cpu' dies?
>
> Still can't understand you. Probably you missed what singlethread_cpu is.
oops yes ..I had mistakenly thought that create_workqueue_thread() will
bind worker thread to singlethread_cpu for sing
On Mon, 2007-01-15 at 16:43 -0500, Kristian Høgsberg wrote:
> On 1/15/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > again the best way is for you to provide an mmap method... you can then
> > fill in the pages and keep that in some sort of array; this is for
> > example also what the DRI/DRM
Patch looks good - thanks, Bob.
Signed-off-by: Paul Jackson <[EMAIL PROTECTED]>
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To unsubscribe from this list: send the lin
On 1/15/07, Christoph Hellwig <[EMAIL PROTECTED]> wrote:
On Mon, Jan 15, 2007 at 05:54:50PM -0800, Nate Diller wrote:
> This series is an attempt to generalize the async I/O paths to be
> implementation agnostic. It completely eliminates knowledge of
> the kiocb structure in the generic code and
Christoph wrote:
> Cpusets is your thing so I think you could fix this the right way.
But wasn't it your patch that broke ...
Actually, I'd have blessed Bob Picco's patch, as it's done the right
way, with a cpuset_* macro hook, defined twice in cpuset.h, with and
without CONFIG_CPUSET, where the
On Mon, 15 Jan 2007, Paul Jackson wrote:
> You're right about this problemI think that Christoph Lameter
> (added to cc list) is working on a fix for this.
Cpusets is your thing so I think you could fix this the right way. There
are already two different patches fixing this. Just make it the way
On Jan 15, 2007, at 1:54 PM, Andrew Walrond wrote:
Olaf Hering wrote:
Why do you need /sbin/hotplug anyway, just for firmware loading for a
non-modular kernel?
I guess this is unusual, but FWIW...
I have a custom distro and I was just looking for the easiest way
to create a bootable rescue
On Fri, 12 January 2007 00:19:45 +0800, Aubrey wrote:
>
> Yes for desktop, server, but maybe not for embedded system, specially
> for no-mmu linux. In many embedded system cases, the whole system is
> running in the ram, including file system. So it's not necessary using
> page cache anymore. Page
From: ahendry <[EMAIL PROTECTED]>
Date: Tue, 09 Jan 2007 09:32:17 +1100
> __x25_find_socket does a sock_hold.
> This adds a missing sock_put in x25_receive_data.
>
> Signed-off-by: Andrew Hendry <[EMAIL PROTECTED]>
Applied, thanks a lot.
-
To unsubscribe from this list: send the line "unsubscrib
On Mon, Jan 15, 2007 at 05:54:50PM -0800, Nate Diller wrote:
> This series is an attempt to generalize the async I/O paths to be
> implementation agnostic. It completely eliminates knowledge of
> the kiocb structure in the generic code and makes it private within the
> current aio code. Things ge
> > +
> > + err = xenbus_printf(xbt, dev->nodename,
> > + "ring-ref","%u", info->ring_ref);
>
> why do you need your own printf?
xenbus_printf isn't a printf replacement - it is used for writing a formatted
string into XenStore (which contains VM configuration data in a
Björn Steinbrink wrote:
It should be correct the way it is - that check is trying to prevent
ATAPI commands from using DMA until the slave_config function has been
called to set up the DMA parameters properly. When the
NV_ADMA_ATAPI_SETUP_COMPLETE flag is not set, this returns 1 which
disallow
On Sat, Jan 13, 2007 at 01:20:23PM -0800, Andrew Morton wrote:
>
> Seeing the code helps.
But there was a subtle problem with hold time instrumentation here.
The code assumed the critical section exiting through
spin_unlock_irq entered critical section with spin_lock_irq, but that
might not be t
From: YOSHIFUJI Hideaki <[EMAIL PROTECTED]>
Date: Tue, 16 Jan 2007 11:06:30 +0900 (JST)
> In article <[EMAIL PROTECTED]> (at Tue, 16 Jan 2007 03:01:56 +0100), Gabriel
> C <[EMAIL PROTECTED]> says:
>
> > Should be the fix from http://bugzilla.kernel.org/show_bug.cgi?id=7817
>
> I've resent the p
You're right about this problemI think that Christoph Lameter
(added to cc list) is working on a fix for this.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[EMAIL PROTECTED]> 1.925.600.0401
-
To unsubscrib
The possible cause is a bug in kswapd thread, or shrink_all_memory
cannot be called in kswapd thread.
On 1/15/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
Roy Huang wrote:
> A patch provide a interface to limit total page cache in
> /proc/sys/vm/pagecache_ratio. The default value is 9
On Tuesday 16 January 2007 06:43, Kristian Høgsberg wrote:
> On 1/15/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> > there is a lot of pain involved with doing things this way, it is a TON
> > better if YOU provide the memory via a custom mmap handler for a device
> > driver.
> > (there are a l
Remove unused arg from socket operations
The sendmsg and recvmsg socket operations take a kiocb pointer, but none of
the functions actually use it. There's really no need even theoretically,
it's really quite ugly having it there at all. Also, removing it will pave
the way for a more generic com
This converts the _locking variant of blockdev_direct_IO to use a generic
endio function, and updates all the FS callsites.
---
Documentation/filesystems/Locking |5 +++--
Documentation/filesystems/vfs.txt |5 +++--
fs/block_dev.c|9 -
fs/ext2/inode.c
Hi Balbir,
Thanks for your comment.
On 1/15/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
wakeup_kswapd and shrink_all_memory use swappiness to determine what to reclaim
(mapped pages or page cache). This patch does not ensure that only
page cache is
reclaimed/limited. If the swappiness value i
Hello!
This is a updated version of the earlier RCU-boosting patch
(http://lkml.org/lkml/2007/1/2/347). It boosts the priority of RCU
read-side critical sections in -rt kernels, and the context diff is
almost 300 lines shorter than its predecessor. Simplifications were
inspired by the act of att
On Mon, Jan 15, 2007 at 05:54:50PM -0800, Nate Diller wrote:
> Convert code using iocb->ki_left to use the more generic iov_length() call.
No way. We need to reduce the numer of iovec traversals, not adding
more of them.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
This converts the internals of __blockdev_direct_IO in fs/direct-io.c to use
a generic endio function, instead of directly calling aio_complete. It also
changes the semantics of dio_iodone to be more friendly to its only users,
xfs and ocfs2. This allows the caller to know how to release locks an
This removes the aio implementation from the usb gadget file system. Aside
from making very creative (!) use of the aio retry path, it can't be of any
use performance-wise because it always kmalloc()s a bounce buffer for the
*whole* I/O size. Perhaps the only reason to keep it around is the abili
In article <[EMAIL PROTECTED]> (at Tue, 16 Jan 2007 03:01:56 +0100), Gabriel C
<[EMAIL PROTECTED]> says:
> Greg KH schrieb:
> > On Sun, Jan 14, 2007 at 09:30:08PM -0800, David Miller wrote:
> >
> >> From: David Stevens <[EMAIL PROTECTED]>
> >> Date: Sun, 14 Jan 2007 19:47:49 -0800
> >>
> >>
Convert code using iocb->ki_left to use the more generic iov_length() call.
---
diff -urpN -X dontdiff a/fs/ocfs2/file.c b/fs/ocfs2/file.c
--- a/fs/ocfs2/file.c 2007-01-10 11:50:26.0 -0800
+++ b/fs/ocfs2/file.c 2007-01-10 12:42:09.0 -0800
@@ -1157,7 +1157,7 @@ static ssize_t
This converts the iternals of nfs's directIO support to use a generic endio
function, instead of directly calling aio_complete. It's pretty easy
because it already has a pretty abstracted completion path.
---
diff -urpN -X dontdiff a/fs/nfs/direct.c b/fs/nfs/direct.c
--- a/fs/nfs/direct.c 2007
Define a new function typedef for I/O completion at the file/iovec level --
typedef void (file_endio_t)(void *endio_data, ssize_t count, int err);
and convert aio_complete and all its callers to this new prototype.
---
drivers/usb/gadget/inode.c | 24 +++---
fs/aio.c
Convert the internals of blkdev_direct_IO to use a generic endio function,
instead of directly calling aio_complete. This may also fix some bugs/races
in this code, for instance it checks bio->bi_size instead of assuming it's
zero, and it atomically accumulates the bytes_done counter (assuming tha
this patch removes struct sock_iocb
Its purpose seems to have dwindled to a mere container for struct
scm_cookie, and all of the users of scm_cookie seem to require
re-initializing it each time anyway. Besides, keeping such data around from
one call to the next seems to me like a layering violati
This series is an attempt to generalize the async I/O paths to be
implementation agnostic. It completely eliminates knowledge of
the kiocb structure in the generic code and makes it private within the
current aio code. Things get noticeably cleaner without that layering
violation.
The new interf
Greg KH schrieb:
> On Sun, Jan 14, 2007 at 09:30:08PM -0800, David Miller wrote:
>
>> From: David Stevens <[EMAIL PROTECTED]>
>> Date: Sun, 14 Jan 2007 19:47:49 -0800
>>
>>
>>> I think it's better to add the fix than withdraw this patch, since
>>> the original bug is a crash.
>>>
>>
Robert Hancock wrote:
I'll try your stress test when I get a chance, but I doubt I'll run into
the same problem and I haven't seen any similar reports. Perhaps it's
some kind of wierd timing issue or incompatibility between the
controller and that drive when running in ADMA mode? I seem to reme
Robert Hancock wrote:
Note that the ATA-7 spec for FLUSH CACHE says that "This command may
take longer than 30 s to complete."
Yep...
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
Jens Axboe wrote:
On Mon, Jan 15 2007, Jeff Garzik wrote:
Jens Axboe wrote:
I'd be surprised if the device would not obey the 7 second timeout rule
that seems to be set in stone and not allow more dirty in-drive cache
than it could flush out in approximately that time.
AFAIK Windows flush-cache
from: Kevin Lloyd <[EMAIL PROTECTED]>
This patch ensures that the device is turned on when inserted into the
system (which mostly affects the EM5725 and MC5720. It also adds more
VID/PIDs and matches the N_OUT_URB with the airprime driver.
Signed-off-by: Kevin Lloyd <[EMAIL PROTECTED]>
---
Hi...
I run the (almost) latest -mm kernel (2.6.20-rc3-mm1), and see some strange
behaviour
with POSIX threads (glibc-2.4).
I have downgraded my test to a simple textboox example for a SMP-safe spool
queue, it's just a circular queue with a mutex and a condition variable for in
and out. I have se
On 2007.01.15 18:34:43 -0600, Robert Hancock wrote:
> Björn Steinbrink wrote:
> >>My latest bisection attempt actually led to your sata_nv ADMA commit. [1]
> >>I've now backed out that patch from 2.6.20-rc5 and have my stress test
> >>running for 20 minutes now ("record" for a bad kernel surviving
Hi there,
I've been curious enough to try 2.6.20-rc5 with nfs4/kerberos.
It was working fine before. I was using 2.6.18.1 on the client and
2.6.20-rc3-git4 on server and today i tried 2.6.20-rc5 on both client
and server. (both running up to date debian/sid)
Trying to mount a nfs4 or nfs3 share w
On Mon, Jan 15 2007, Thomas Gleixner wrote:
> On Mon, 2007-01-15 at 09:08 +0100, Thomas Gleixner wrote:
> > > Thomas saw something similar yesterday and he the partial results that
> > > git.block (between rc2-mm1 and rc4-mm1) breaks certain disk drivers or
> > > filesystems drivers. For me it wo
On Mon, Jan 15 2007, Linas Vepstas wrote:
>
> Hi Chris, Jens,
> Can you look at this, and push upstream if this looks reasonable
> to you? It fixes a bug I've been tripping over.
>
> --linas
>
>
> A flag was recently added to the elevator code to avoid
> performing an unplug when reuests are be
On Sun, Jan 14 2007, Ricardo Correia wrote:
> Hi, (please CC: to my email address, I'm not subscribed)
>
> Quick question: how can I flush the disk write cache from userspace?
>
> Long question:
>
> I'm porting the Solaris ZFS filesystem to the FUSE/Linux filesystem
> framework. This is a copy-
Jens Axboe wrote:
On Mon, Jan 15 2007, Jeff Garzik wrote:
Jens Axboe wrote:
I'd be surprised if the device would not obey the 7 second timeout rule
that seems to be set in stone and not allow more dirty in-drive cache
than it could flush out in approximately that time.
AFAIK Windows flush-cache
Björn Steinbrink wrote:
My latest bisection attempt actually led to your sata_nv ADMA commit. [1]
I've now backed out that patch from 2.6.20-rc5 and have my stress test
running for 20 minutes now ("record" for a bad kernel surviving that
test is about 40 minutes IIRC). I'll keep it running for at
Christoph Anton Mitterer wrote:
Sorry, as always I've forgot some things... *g*
Robert Hancock wrote:
If this is related to some problem with using the GART IOMMU with memory
hole remapping enabled
What is that GART thing exactly? Is this the hardware IOMMU? I've always
thought GART was some
On Mon, Jan 15 2007, Jeff Garzik wrote:
> Jens Axboe wrote:
> >I'd be surprised if the device would not obey the 7 second timeout rule
> >that seems to be set in stone and not allow more dirty in-drive cache
> >than it could flush out in approximately that time.
>
> AFAIK Windows flush-cache timeo
On Mon, Jan 15, 2007 at 11:14:52PM +, Alan wrote:
> If you pull the drive and test it in another box does it show the same ?
I'm going to try that. The prolem requires 3-7 days to appear, so I
won't know immediatly.
> And what does a scsi verify have to say ?
Running, looks like it's gonna
On Mon, Jan 15, 2007 at 23:55:15 +0200, Sami Farin wrote:
> I know this may be entirely my fault but I have tried reversing
> all of my _own_ patches I applied to 2.6.19.2 but can't find what broke this.
> I did three times "netcat 127.0.0.69 42", notice the different
> port numbers.
Hmm... when
On Mon, Jan 15 2007, Ingo Molnar wrote:
>
> * Jens Axboe <[EMAIL PROTECTED]> wrote:
>
> > > In a previous write invoked by: fsck.ext3(1896): WRITE block 8552 on
> > > sdb1 end_buffer_async_write() is invoked.
> > >
> > > sdb1 is not a part of a raid device.
> >
> > When I briefly tested this b
On 2007.01.15 22:17:24 +0100, Björn Steinbrink wrote:
> On 2007.01.14 17:43:53 -0600, Robert Hancock wrote:
> > Björn Steinbrink wrote:
> > >Hi,
> > >
> > >with 2.6.20-rc{2,4,5} (no other tested yet) I see SATA exceptions quite
> > >often, with 2.6.19 there are no such exceptions. dmesg and lspci -
On Tue, Jan 16, 2007 at 12:27:17AM +0100, Stefan Richter wrote:
> On 15 Jan, Olivier Galibert wrote:
> > sd 0:0:0:0: SCSI error: return code = 0x0802
> > sda: Current: sense key: Hardware Error
> > ASC=0x42 ASCQ=0x0
>
> The Additional Sense Code means "power-on or self-test failure" FWIW.
current->mems_allowed is defined for CONFIG_CPUSETS. This broke !CPUSETS
build. I compiled and linked tested both variants.
Signed-off-by: Bob Picco <[EMAIL PROTECTED]>
include/linux/cpuset.h |6 ++
mm/mempolicy.c |2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
Index
On 15 Jan, Olivier Galibert wrote:
> sd 0:0:0:0: SCSI error: return code = 0x0802
> sda: Current: sense key: Hardware Error
> ASC=0x42 ASCQ=0x0
The Additional Sense Code means "power-on or self-test failure" FWIW.
(SPC-4 annex D)
--
Stefan Richter
-=-=-=== ---= =
http://arcgraph.d
Hi,
Tim Ryan has reported the following bug at the Gentoo bugzilla:
https://bugs.gentoo.org/show_bug.cgi?id=162199
His home dir is mounted over NFS. 2.6.18 worked OK but 2.6.19 is very
slow to load the desktop environment. NFS is suspected here as the
problem does not exist for users with loc
Sorry, as always I've forgot some things... *g*
Robert Hancock wrote:
> If this is related to some problem with using the GART IOMMU with memory
> hole remapping enabled
What is that GART thing exactly? Is this the hardware IOMMU? I've always
thought GART was something graphics card related,..
> Both smart and the internal blade diagnostics say "everything is a-ok
> with the drive, there hasn't been any error ever except a bunch of
> corrected ECC ones, and no more than with a similar drive in another
> working blade". Hence my initial post. "Hardware error" is kinda
> imprecise, so I
Hi everybody.
Sorry again for my late reply...
Robert gave us the following interesting information some days ago:
Robert Hancock wrote:
> If this is related to some problem with using the GART IOMMU with memory
> hole remapping enabled, then 2.6.20-rc kernels may avoid this problem on
> nForc
Jiri Kosina ([EMAIL PROTECTED]) wrote:
> On Mon, 15 Jan 2007, Simon Budig wrote:
> > Is it possible that there is a regression in the hid-debug stuff? The
> > mapping does not seem to appear in the dmesg-output. I unfortunately
> > don't have an earlier kernel available right now to verify, but now
On Mon, 15 Jan 2007 09:37:35 +0100
Haavard Skinnemoen <[EMAIL PROTECTED]> wrote:
>
> On Mon, 15 Jan 2007 14:48:57 +1100
> Ben Nizette <[EMAIL PROTECTED]> wrote:
>
>> Remove an unwanted remnant of the recent revert of AVR32/AT91 SPI
patches in -mm. Without this patch, the AVR32 build of
2.6.20-r
Attached is an updated patch that addresses Michael Ellerman's comments.
One comment made by Michael has not yet been addressed:
The comment was in regard to the for-loop in
spufs/sched.c:notify_spus_active(). He wondered if the scheduler can
swap a context from one node to another. If so, th
On Mon, 15 Jan 2007 18:26:42 +, Frederik Deweerdt wrote
> On Mon, Jan 15, 2007 at 06:54:50PM +0200, ris wrote:
> > I have motherboard with nforce 590 SLI (MCP55) chipset.
> > On other systems all its ok.
> >
> > But i tried a lot o kernels, configurations and always get cpu at 100% when
> > co
Hi.
Some days ago I received the following message from "Sunny Days". I
think he did not send it lkml so I forward it now:
Sunny Days wrote:
> hello,
>
> i have done some extensive testing on this.
>
> various opterons, always single socket
> various dimms 1 and 2gb modules
> and hitachi+seagate
Compile-tested.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
drivers/char/toshiba.c | 35 +--
1 file changed, 25 insertions(+), 10 deletions(-)
--- a/drivers/char/toshiba.c
+++ b/drivers/char/toshiba.c
@@ -68,6 +68,7 @@ #include
#include
#include
On Mon, Jan 15, 2007 at 04:24:17PM -0500, Rob Landley wrote:
> Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
Acked-by: Sam Ravnborg <[EMAIL PROTECTED]>
PS
My dev machine is broke and need a new one before kbuild.git will
be alive again.
Considering an AMD Athlon 64 X2 based one with Nvidia GeForc
[I've rearranged this to avoid a horrid mix of top and bottom posting]
On Sun, 14 Jan 2007, Tigran Aivazian wrote:
> On Sun, 14 Jan 2007, Tigran Aivazian wrote:
> > On Sun, 14 Jan 2007, Tigran Aivazian wrote:
> > > I think I may have found a bug --- on one of my machines the umask value
> > > is i
I know this may be entirely my fault but I have tried reversing
all of my _own_ patches I applied to 2.6.19.2 but can't find what broke this.
I did three times "netcat 127.0.0.69 42", notice the different
port numbers.
First, if someone could attempt this on 2.6.19.2 or 2.6.20-rc* ,
and tell it wo
Compile-tested.
Signed-off-by: Alexey Dobriyan <[EMAIL PROTECTED]>
---
fs/coda/sysctl.c | 76 ---
1 file changed, 39 insertions(+), 37 deletions(-)
--- a/fs/coda/sysctl.c
+++ b/fs/coda/sysctl.c
@@ -15,6 +15,7 @@ #include
#include
#includ
Hi Chris, Jens,
Can you look at this, and push upstream if this looks reasonable
to you? It fixes a bug I've been tripping over.
--linas
A flag was recently added to the elevator code to avoid
performing an unplug when reuests are being re-queued.
The goal of this flag was to avoid a deep recur
On Mon, Jan 15, 2007 at 06:45:40PM +, Alan wrote:
> On Mon, 15 Jan 2007 18:16:02 +0100
> Olivier Galibert <[EMAIL PROTECTED]> wrote:
>
> > sd 0:0:0:0: SCSI error: return code = 0x0802
> > sda: Current: sense key: Hardware Error
> > ASC=0x42 ASCQ=0x0
>
> I'll give you a clue: The words
On 1/15/07, Arjan van de Ven <[EMAIL PROTECTED]> wrote:
> However, what I'd really like to do is to leave it to user space to
> allocate the memory as David describes. In the transmit case, user
> space allocates memory (malloc or mmap) and loads the payload into
> that buffer.
there is a lot
> However, what I'd really like to do is to leave it to user space to
> allocate the memory as David describes. In the transmit case, user
> space allocates memory (malloc or mmap) and loads the payload into
> that buffer.
there is a lot of pain involved with doing things this way, it is a TON
b
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
Use "awk" instead of "gawk".
--
There's a symlink from awk to gawk if you're using the gnu tools, but no
symlink from gawk to awk if you're using BusyBox or some such. (There's a
reason for the existence of standard names. Can we use them please?
On 2007.01.14 17:43:53 -0600, Robert Hancock wrote:
> Björn Steinbrink wrote:
> >Hi,
> >
> >with 2.6.20-rc{2,4,5} (no other tested yet) I see SATA exceptions quite
> >often, with 2.6.19 there are no such exceptions. dmesg and lspci -v
> >output follows. In the meantime, I'll start bisecting.
>
> .
On Mon, 15 Jan 2007, Simon Budig wrote:
> Is it possible that there is a regression in the hid-debug stuff? The
> mapping does not seem to appear in the dmesg-output. I unfortunately
> don't have an earlier kernel available right now to verify, but now the
> output on plugging in the device looks
1 - 100 of 258 matches
Mail list logo
