Ravikiran G Thirumalai wrote:
On Sat, Jan 13, 2007 at 03:39:45PM +1100, Nick Piggin wrote:
What is the "CS time"?
Critical Section :). This is the maximal time interval I measured from
t2 above to the time point we release the spin lock. This is the hold
time I guess.
It would be
On Fri, Jan 12, 2007 at 05:11:16PM -0800, Andrew Morton wrote:
> On Fri, 12 Jan 2007 17:00:39 -0800
> Ravikiran G Thirumalai <[EMAIL PROTECTED]> wrote:
>
> > But is
> > lru_lock an issue is another question.
>
> I doubt it, although there might be changes we can make in there to
> work around
On Sat, Jan 13, 2007 at 03:39:45PM +1100, Nick Piggin wrote:
> Ravikiran G Thirumalai wrote:
> >Hi,
> >We noticed high interrupt hold off times while running some memory
> >intensive
> >tests on a Sun x4600 8 socket 16 core x86_64 box. We noticed softlockups,
>
> [...]
>
> >We did not use any
On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.20-rc3-mm1:
>...
> git-dvb.patch
>...
> git trees
>...
drivers/media/video/sn9c102/sn9c102_pas202bca.c is no longer used or
built but still shipped.
cu
Adrian
--
"Is there not promise of rain?"
On Fri, Jan 12, 2007 at 03:58:08PM -0600, Kumar Gala wrote:
> I'm working on an embedded PPC setup with 64M of memory and no swap.
> I'm trying to figure out how best to tune the VM for an OOM situation
> I'm running into.
>
> I'm running a 2.6.16.35 kernel and have a bittorrent app that
On Sat, 2007-01-13 at 10:55 +0900, Tejun Heo wrote:
> Soeren Sonnenburg wrote:
> > It is true it detects a removal and newly plugged devices immediately...
> > However it still prints warnings and errors that it could not
> > synchronize SCSI cache for the disks. Then it prints regular 'rejects
>
This email lists some known regressions in 2.6.20-rc5 compared to 2.6.19
with patches available.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any
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.
>
> Not that there will be any, right? You all behave now!
>...
On Fri, Jan 12, 2007 at 09:59:40AM +, Alan wrote:
> On Fri, 12 Jan 2007 07:02:13 +0100
> Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > Just noticed this while looking at a bug.
> > Avoid an expensive integer divide 3 times per CPU per tick.
>
> Integer divide is cheap on some modern
Am Freitag, 12. Januar 2007 18:42 schrieb Takashi Iwai:
> At Fri, 12 Jan 2007 14:49:57 +0100,
> Oliver Neukum wrote:
> >
> > + } else {
> > +if (idx < snd_ecards_limit) {
> > + if (snd_cards_lock & (1 << idx))
> > + err = -EBUSY; /*
Running fsx-linux (akpm ext3-tools version) on reiserfs,
2.6.20-rc5 on x86_64.
[ 4496.964604] [ cut here ]
[ 4496.964614] Kernel BUG at 880b4499 [verbose debug info unavailable]
[ 4496.964621] invalid opcode: [1] SMP
[ 4496.964629] CPU 2
[ 4496.964635]
Justin Piszcz wrote:
> On Sat, 13 Jan 2007, Al Boldi wrote:
> > Justin Piszcz wrote:
> > > Btw, max sectors did improve my performance a little bit but
> > > stripe_cache+read_ahead were the main optimizations that made
> > > everything go faster by about ~1.5x. I have individual bonnie++
> > >
On Friday 12 January 2007 10:50, Mark Hounschell wrote:
> Mark Hounschell wrote:
> > I have a Tyan S4881 Thunder K8QW 4 processor (8 cores). Kernel 2.6.16.37
> > boots
> > and runs fine.
> > However kernel 2.6.17 and up doesn't. Here is my boot error msg.
> >
> >
> > kernel /vmlinuz-2.6.17-smp
From: Jeff Chua <[EMAIL PROTECTED]>
CC [M] drivers/kvm/vmx.o
{standard input}: Assembler messages:
{standard input}:3257: Error: bad register name `%sil'
make[2]: *** [drivers/kvm/vmx.o] Error 1
make[1]: *** [drivers/kvm] Error 2
make: *** [drivers] Error 2
I'm not using the kernel
13 Oca 2007 Cts 03:12 tarihinde, Tejun Heo şunları yazmıştı:
> Hello,
Hello,
Thanks for the response.
> [...]
> Does everything else work okay?
> Can you access devices attached to
> ahci?
Yes. While the machine is on, there seems to be no problem at all. Everything
works great.
> What
Hi Richard,
* Richard J Moore ([EMAIL PROTECTED]) wrote:
>
>
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote on 20/12/2006
> 23:52:16:
>
> > Hi,
> >
> > You will find, in the following posts, the latest revision of the Linux
> Kernel
> > Markers. Due to the need some tracing projects (LTTng,
Here's a line fix to ignore the "video device notify" message ...
--- linux/drivers/acpi/video.c.org 2007-01-12 23:05:23 +0800
+++ linux/drivers/acpi/video.c 2007-01-12 23:05:29 +0800
@@ -1771,1 +1771,1 @@
- printk("video device notify\n");
+ //printk("video device
On Fri, Jan 12, 2007 at 02:26:45PM -0800, Andrew Morton wrote:
> On Fri, 12 Jan 2007 14:27:48 -0500 (EST)
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> >
> > Ok, there it is, in all its shining glory.
>
> It still doesn't run Excel.
>...
It should work with CrossOver.
cu
Adrian
--
Kumar Gala wrote:
I'm working on an embedded PPC setup with 64M of memory and no swap.
I'm trying to figure out how best to tune the VM for an OOM situation
I'm running into.
I'm running a 2.6.16.35 kernel and have a bittorrent app that appears
to be initializing a large file for it to
Bill Davidsen wrote:
The point is that if you want to be able to allocate at all, sometimes
you will have to write dirty pages, garbage collect, and move or swap
programs. The hardware is just too limited to do something less painful,
and the user can't see memory to do things better. Linus
Ravikiran G Thirumalai wrote:
Hi,
We noticed high interrupt hold off times while running some memory intensive
tests on a Sun x4600 8 socket 16 core x86_64 box. We noticed softlockups,
[...]
We did not use any lock debugging options and used plain old rdtsc to
measure cycles. (We disable
On Sat, 13 Jan 2007 03:58:19 +0100 Von Wolher wrote:
> Hi,
>
> I just build a 2.6.19.1 vanilla kernel based on the previous config
> (make oldconfig) but for some reason it is not starting. Despite
> following the usual procedure with lilo like many times before it seems
> that lilo tries to
Hi,
this patch fills in the portions for ia64 kexec.
I'm actually not sure what options are required for the dump-capture
kernel, but "init 1 irqpoll maxcpus=1" has been working fine for me.
Or more to the point, I'm not sure if irqpoll is needed or not.
This patch requires the documentation
On Fri, Jan 12, 2007 at 11:46:39AM -0800, Jay Lan wrote:
> Horms wrote:
> > Hi,
> >
> > this patch fills in the portions for ia64 kexec.
> >
> > I'm actually not sure what options are required for the dump-capture
> > kernel, but "init 1 irqpoll maxcpus=1" has been working fine for me.
> > Or
On Sat, Jan 13, 2007 at 04:05:28 +0100, Tino Keitel wrote:
[...]
> I think I found the problem. In 2.6.18, I had a slightly different
> config. With 2.6.20-rc4, I had sucessful suspend/resume cycles without
> the USB DVB-T box attached. I tweaked the USB options a bit and
> activated some
On 1/13/07, Jeff Chua <[EMAIL PROTECTED]> wrote:
On 1/13/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Jan 2007 14:27:48 -0500 (EST)
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
CC [M] drivers/kvm/vmx.o
{standard input}: Assembler messages:
{standard input}:3257: Error: bad
On Fri, 12 Jan 2007 10:03:49 EST, Lennart Sorensen said:
>
> I would expect any distribution should work on these (as long as the
> kernel they use isn't too old.). Of course if it is a Mac, you need a
> distribution that supports their firmware (which is of course not a PC
> bios). As long as
On 1/13/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Fri, 12 Jan 2007 14:27:48 -0500 (EST)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
http://userweb.kernel.org/~akpm/2.6.20-rc5-mm-fixes
The KVM and direct-io changes are significant, so if people are testing
those things, please be sure to
Hi,
I just build a 2.6.19.1 vanilla kernel based on the previous config
(make oldconfig) but for some reason it is not starting. Despite
following the usual procedure with lilo like many times before it seems
that lilo tries to boot it and jumps back to the menu screen.
But selecting the old
Nonlinear mappings are (AFAIKS) simply a virtual memory concept that
encodes the virtual address -> file offset differently from linear
mappings.
I can't see why the filesystem/pagecache code should need to know anything
about it, except for the fact that the ->nopage handler didn't quite pass
Remove legacy filemap_nopage and all of the .populate API cruft.
This patch is optional and can be left out (eg. for a cleaner merge with -mm),
and rebased after the previous patches go upstream.
include/linux/mm.h |9 --
mm/filemap.c | 195
Remove ->nopfn and reimplement the only existing handler using ->fault
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/drivers/char/mspec.c
===
--- linux-2.6.orig/drivers/char/mspec.c
+++
Add a vm_insert_pfn helper, so that ->fault handlers can have nopfn
functionality by installing their own pte and returning NULL.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/include/linux/mm.h
===
---
Fix the race between invalidate_inode_pages and do_no_page.
Andrea Arcangeli identified a subtle race between invalidation of
pages from pagecache with userspace mappings, and do_no_page.
The issue is that invalidation has to shoot down all mappings to the
page, before it can be discarded from
Add a bugcheck for Andrea's pagefault vs invalidate race. This is triggerable
for both linear and nonlinear pages with a userspace test harness (using
direct IO and truncate, respectively).
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/mm/filemap.c
The following set of patches fix the fault vs invalidate and fault
vs truncate_range race for filemap_nopage mappings, plus those and
fault vs truncate race for nonlinear mappings.
Hasn't changed since I last submitted it, when it was rejected because
it made one of the buffered write deadlocks
Identical block is duplicated twice: contrary to the comment, we have been
re-reading the page *twice* in filemap_nopage rather than once.
If any retry logic or anything is needed, it belongs in lower levels anyway.
Only retry once. Linus agrees.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
From: Andrew Morton <[EMAIL PROTECTED]>
Clean up buffered write code. Rename some variables and fix some types.
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/mm/filemap.c
If prepare_write fails with AOP_TRUNCATED_PAGE, or if commit_write fails, then
we may have failed the write operation despite prepare_write having
instantiated blocks past i_size. Fix this, and consolidate the trimming into
one place.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index:
Modify the core write() code so that it won't take a pagefault while holding a
lock on the pagecache page. There are a number of different deadlocks possible
if we try to do such a thing:
1. generic_buffered_write
2. lock_page
3.prepare_write
4. unlock_page+vmtruncate
5.
Hide some of the open-coded nr_segs tests into the iovec helpers. This is
all to simplify generic_file_buffered_write, because that gets more complex
in the next patch.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/mm/filemap.h
No need to do the confusing switch of variables from copied into status.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/mm/filemap.c
===
--- linux-2.6.orig/mm/filemap.c
+++ linux-2.6/mm/filemap.c
@@ -1898,28
Allow CONFIG_DEBUG_VM to switch off the prefaulting logic, to simulate the
difficult race where the page may be unmapped before calling copy_from_user.
Makes the race much easier to hit.
This is useful for demonstration and testing purposes, but is removed in a
subsequent patch.
Signed-off-by:
Quite a bit of code is used in maintaining these "cached pages" that are
probably pretty unlikely to get used. It would require a narrow race where
the page is inserted concurrently while this process is allocating a page
in order to create the spare page. Then a multi-page write into an uncached
From: Andrew Morton <[EMAIL PROTECTED]>
Revert 6527c2bdf1f833cc18e8f42bd97973d583e4aa83
This patch fixed the following bug:
When prefaulting in the pages in generic_file_buffered_write(), we only
faulted in the pages for the firts segment of the iovec. If the second of
successive segment
From: Andrew Morton <[EMAIL PROTECTED]>
Revert 81b0c8713385ce1b1b9058e916edcf9561ad76d6.
This was a bugfix against 6527c2bdf1f833cc18e8f42bd97973d583e4aa83, which we
also revert.
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index:
simple_prepare_write and nobh_prepare_write leak uninitialised kernel data.
Fix the former, make a note of the latter. Several other filesystems seem
to be iffy here, too.
Signed-off-by: Nick Piggin <[EMAIL PROTECTED]>
Index: linux-2.6/fs/libfs.c
The following set of patches attempt to fix the buffered write
locking problems (and there are a couple of peripheral patches
and cleanups there too).
This does pass the write deadlock tests that otherwise fail.
Has survived a few hours of fsx-linux on ext2 and 3.
Patches against 2.6.20-rc4. I
On Fri, Jan 12, 2007 at 14:50:25 +, Pavel Machek wrote:
> Hi!
>
> > > >> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > > >> > 2.6.20-rc3.
> > > >>
> > > >> Is this issue still present in -rc4?
> > > >
> > > >I used 2.6.20-rc4 in single user mode, and applied 2
Hi.
On Fri, 2007-01-12 at 14:26 -0800, Andrew Morton wrote:
> On Fri, 12 Jan 2007 14:27:48 -0500 (EST)
> Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> >
> > Ok, there it is, in all its shining glory.
> >
>
> It still doesn't run Excel.
Heretic!
:)
-
To unsubscribe from this list: send the
On Sat, Jan 13, 2007 at 06:43:07AM +1100, Neil Brown wrote:
>
> Ok, thanks. I must have missed something else wrong in the code..
>
> Probably this 'break' in the wrong place...
>
> Could you try this patch instead please - or just move the 'break' to
> where it should be.
Now it worked
Alan wrote:
> I'm currently hacking on the speed handling code a bit
>
> I'd like to do the following unless anyone has any objections
>
> - Remove post_set_mode and make drivers wrap the guts of the existing
> set_mode() function. This allows a driver to wrap and see success/failure
> while
On , [EMAIL PROTECTED] said:
> On Thu, 04 Jan 2007 22:02:00 PST, Andrew Morton said:
>
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc3-mm1/
Still seeing this in -rc4-mm1..
> With git-block.patch applied, my system locks up *hard* at system
Greg KH wrote:
> On Fri, Jan 12, 2007 at 10:32:10PM +0300, Michael Tokarev wrote:
>> (No patch at this time, -- just asking about an.. idea ;)
>
> Let's see what such a patch looks like to see if it would be workable or
> not.
Umm.. it's definitely workable, and even almost trivial.
Just
Soeren Sonnenburg wrote:
> It is true it detects a removal and newly plugged devices immediately...
> However it still prints warnings and errors that it could not
> synchronize SCSI cache for the disks. Then it prints regular 'rejects
> I/O to dead device' warning messages and on replugging the
Am Freitag, den 12.01.2007, 22:42 -0200 schrieb Mauro Carvalho Chehab:
> Em Qui, 2007-01-11 às 00:41 +0100, hermann pitton escreveu:
> > Am Mittwoch, den 10.01.2007, 09:58 +0100 schrieb Gerd Hoffmann:
> > > Hi,
> > >
> > > We have a DMA32 zone now, lets use it to make sure the card
> > > can
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote on 20/12/2006
23:52:16:
> Hi,
>
> You will find, in the following posts, the latest revision of the Linux
Kernel
> Markers. Due to the need some tracing projects (LTTng, SystemTAP) has of
this
> kind of mechanism, it could be nice to consider it for
Hello,
Faik Uygur wrote:
> We have a Sony PCG-6H1M laptop. It started failing to poweroff with our
> switch
> from 2.6.16 stable series kernels to 2.6.18 stable series. Rebooting works.
>
> While searching for the cause, I have found these reported bug reports in the
> kernel bugzilla which
On Fri, 12 Jan 2007 17:00:39 -0800
Ravikiran G Thirumalai <[EMAIL PROTECTED]> wrote:
> But is
> lru_lock an issue is another question.
I doubt it, although there might be changes we can make in there to
work around it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Fri, Jan 12, 2007 at 01:45:43PM -0800, Christoph Lameter wrote:
> On Fri, 12 Jan 2007, Ravikiran G Thirumalai wrote:
>
> Moreover mostatomic operations are to remote memory which is also
> increasing the problem by making the atomic ops take longer. Typically
> mature NUMA system have
Mark Wagner wrote:
> The sil24-connected sata drives are external and connected to their own
> power supply.
>
> I've replaced the sil24-based card with a Promise SATA300 TX4 controller
> card and everything seems to work now.
Hmmm... sil24 fares well with four ports occupied. Weird. Care to
Pallipadi, Venkatesh wrote:
> Darrick,
>
> I tried 2.6.20-rc4 on a Dempsey system here in my lab and it worked
> fine. No watchdog lockups.
> Can you try idle routine with hlt instead of mwait. There is no boot
> option for this in x86_64, but you can change
>
On Fri, Jan 12, 2007 at 10:32:10PM +0300, Michael Tokarev wrote:
>
> (No patch at this time, -- just asking about an.. idea ;)
Let's see what such a patch looks like to see if it would be workable or
not.
And no one forces you to use udev, I have machines with a static /dev
that work just fine
On Sat, Jan 13, 2007 at 01:08:46AM +0100, Michal Piotrowski wrote:
> Jiri Slaby napisał(a):
> > Frederik Deweerdt wrote:
> >> On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote:
> >>> On Friday 12 January 2007 05:20, Frederik Deweerdt wrote:
> On Thu, Jan 11, 2007 at 10:26:27PM -0800,
Jiri Slaby wrote:
>> On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote:
>>> What do you see if on failure you also print out the params, like below?
[...]
> ACPI: acpi_table_parse(17, ) HPET NULL handler!
After re-enabling HPET, it disappeared.
regards,
--
Em Qui, 2007-01-11 às 00:41 +0100, hermann pitton escreveu:
> Am Mittwoch, den 10.01.2007, 09:58 +0100 schrieb Gerd Hoffmann:
> > Hi,
> >
> > We have a DMA32 zone now, lets use it to make sure the card
> > can reach the memory we have allocated for the video frame
> > buffers.
> >
> > please
On Fri, Jan 12, 2007 at 07:27:30PM -0500, Lee Revell wrote:
> On Sat, 2007-01-13 at 00:34 +0100, Karl Kiniger wrote:
> > how to track this down?
>
> Reproduce it with an untainted kernel (no nvidia or vmware modules) and
> repost.
How about big fat advice in every tainted oops to bugger off?
-
On Sat, 2007-01-13 at 00:34 +0100, Karl Kiniger wrote:
> how to track this down?
Reproduce it with an untainted kernel (no nvidia or vmware modules) and
repost.
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Darrick,
I tried 2.6.20-rc4 on a Dempsey system here in my lab and it worked
fine. No watchdog lockups.
Can you try idle routine with hlt instead of mwait. There is no boot
option for this in x86_64, but you can change
arch/x86_64/kernel/process.c:select_idle_routine() not to enable mwait.
With
Jiri Slaby napisał(a):
> Frederik Deweerdt wrote:
>> On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote:
>>> On Friday 12 January 2007 05:20, Frederik Deweerdt wrote:
On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
>
>
Hi,
these trigger about 1-2 times per week at random times. I dont see a
pattern, one time it happened after plugging in the USB headphone, another
time it happened while the machine was more or less idle.
machine does not reboot automatically ( /proc/sys/kernel/panic is set to 20)
most of the
On Tue, Jan 09, 2007 at 12:01:28PM +0300, Dmitriy Monakhov wrote:
> ata pci drivers have to return correct error code during resume stage in
> case of errors.
...
> @@ -6246,8 +6253,10 @@ int ata_pci_device_suspend(struct pci_de
> int ata_pci_device_resume(struct pci_dev *pdev)
> {
>
mxser_new, fix sparc compile error
On sparc B400 is not defined. Use B200 for special baudrate, which
is defined on all platforms.
Signed-off-by: Jiri Slaby <[EMAIL PROTECTED]>
---
commit 2826e3a35f34046890c84a77bc2784a184f9bf6a
tree fcfd15b000e703d91361f2b2c3c1bafb0d18b05d
parent
Frederik Deweerdt wrote:
> On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote:
>> On Friday 12 January 2007 05:20, Frederik Deweerdt wrote:
>>> On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
On Fri, 2007-01-12 at 15:25 -0800, Dor Laor wrote:
> This is great news for PV guests.
>
> Never-the-less we still need to improve our full virtualized guest
> support.
Full virtualized guests, which have their own dyntick support, are fine
as long as we provide local apic emulation for them.
> Trying to understand, should I set CPUSETS=y
You don't need CPUSETS for this small a system.
But setting it is harmless - for example at least
one major commercial distribution enables CPUSETS
on almost all their product, most of which is running
on PC's less powerful than yours.
CPUSETS
>* Ingo Molnar <[EMAIL PROTECTED]> wrote:
>
>> > dyntick-enabled guest:
>> > - reduce the load on the host when the guest is idling
>> > (currently an idle guest consumes a few percent cpu)
>>
>> yeah. KVM under -rt already works with dynticks enabled on both the
>> host and the guest. (but it's
On 1/12/07, Lennart Sorensen <[EMAIL PROTECTED]> wrote:
I would expect any distribution should work on these (as long as the
kernel they use isn't too old.). Of course if it is a Mac, you need a
distribution that supports their firmware (which is of course not a PC
bios). As long as you can
On Fri, Jan 12, 2007 at 05:53:08PM -0500, Len Brown wrote:
> On Friday 12 January 2007 05:20, Frederik Deweerdt wrote:
> > On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
> > >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/
>
Le 06.01.2007 19:58, Vladimir V. Saveliev a écrit :
Hello
On Saturday 06 January 2007 13:58, Laurent Riffard wrote:
Hello,
got this with 2.6.20-rc3-mm1:
===
SysRq : Show Blocked State
freesibling
task PC
On Friday 12 January 2007 05:20, Frederik Deweerdt wrote:
> On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
> >
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.20-rc3/2.6.20-rc4-mm1/
> >
> Hi,
>
> The git-acpi.patch replaces earlier "if(!handler)
==> Regarding Re: [patch] raw: don't allow the creation of a raw device with
minor number 0; Jan Engelhardt <[EMAIL PROTECTED]> adds:
jengelh> On Jan 12 2007 11:32, Jeff Moyer wrote:
>> Date: Fri, 12 Jan 2007 11:32:11 -0500
>> From: Jeff Moyer <[EMAIL PROTECTED]>
>> To: Linux Kernel Mailing
On Fri, 12 Jan 2007 15:35:09 -0700
Erik Andersen <[EMAIL PROTECTED]> wrote:
> On Fri Jan 12, 2007 at 05:09:09PM -0500, Linus Torvalds wrote:
> > I suspect a lot of people actually have other reasons to avoid caches.
> >
> > For example, the reason to do O_DIRECT may well not be that you want to
On Jan 12 2007 11:32, Jeff Moyer wrote:
>Date: Fri, 12 Jan 2007 11:32:11 -0500
>From: Jeff Moyer <[EMAIL PROTECTED]>
>To: Linux Kernel Mailing List
>Cc: Steven Fernandez <[EMAIL PROTECTED]>, Andrew Morton <[EMAIL PROTECTED]>
>Subject: [patch] raw: don't allow the creation of a raw device with
Eric Sandeen wrote:
> Alex Tomas wrote:
>
>> yes, but it shouldn't allow to re-link such inode back, IMHO.
>> a filesystem may start some non-revertable activity in its
>> unlink method.
>>
>> thanks, Alex
>>
>
> I tend to agree, chatting w/ Al I think he does too. :) I'll test
> a
On Fri Jan 12, 2007 at 05:09:09PM -0500, Linus Torvalds wrote:
> I suspect a lot of people actually have other reasons to avoid caches.
>
> For example, the reason to do O_DIRECT may well not be that you want to
> avoid caching per se, but simply because you want to limit page cache
>
On Jan 12 2007 09:27, linux-os (Dick Johnson) wrote:
>
>First, since file-operations require process context, and the kernel
>is not a process, you need to create a kernel thread to handle your file
>I/O.
Not always. If you do file I/O as part of a device driver, you are fine.
quad_dsp is such
On Fri, 12 Jan 2007 14:27:48 -0500 (EST)
Linus Torvalds <[EMAIL PROTECTED]> wrote:
>
> Ok, there it is, in all its shining glory.
>
It still doesn't run Excel.
> A lot of developers (including me) will be gone next week for
> Linux.Conf.Au,
me too.
> so you have a week of rest and quiet to
Linus Torvalds wrote:
>
> On Sat, 13 Jan 2007, Michael Tokarev wrote:
>>> At that point, O_DIRECT would be a way of saying "we're going to do
>>> uncached accesses to this pre-allocated file". Which is a half-way
>>> sensible thing to do.
>> Half-way?
>
> I suspect a lot of people actually
Hi!
> You were right, even after making the changes, it seems to be
> telling lies:
>
> # mount
> /dev/hda2 on / type ext2 (rw,usrquota)
> [...]
>
> However, I think I am still not mounting as ext2:
>
> # dmesg | grep 'Kernel command'
> Kernel command line: ro root=/dev/hda2 rootfstype=ext2
Hi!
> > >> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > >> > 2.6.20-rc3.
> > >>
> > >> Is this issue still present in -rc4?
> > >
> > >I used 2.6.20-rc4 in single user mode, and applied 2 patches from
> > >netdev to get wake on LAN support. This way I was able to
On Sat, 13 Jan 2007, Michael Tokarev wrote:
> >
> > At that point, O_DIRECT would be a way of saying "we're going to do
> > uncached accesses to this pre-allocated file". Which is a half-way
> > sensible thing to do.
>
> Half-way?
I suspect a lot of people actually have other reasons to
On Fri, 12 Jan 2007 14:00:16 -0800 (PST)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Fri, 12 Jan 2007, Paul Jackson wrote:
>
> > It might look clearer to someone who is focused on that particular
> > change, but it adds unnecessary noise for the other 90% of the readers
> > of that code
Zan Lynx wrote:
> On Sat, 2007-01-13 at 00:03 +0300, Michael Tokarev wrote:
> [snip]
>> And sure thing, withOUT O_DIRECT, the whole system is almost dead under this
>> load - because everything is thrown away from the cache, even caches of /bin
>> /usr/bin etc... ;) (For that, fadvise() seems to
Christoph wrote:
> If this is hidden in a macro then it may be overlooked.
Sooner or later, every line of code is important.
Shouting any one of them in #ifdef brackets creates
a noisier environment, increasing the chance of missing
another.
And besides ... the other umpteen cpuset hooks all
> Eric Sandeen (ES) writes:
ES> Al says "no" and I'm not arguing. :)
ES> Apparently this may be OK with some filesystems, and Al says he doesn't
ES> want to know about i_nlink in the vfs in any case.
well, generic_drop_inode() uses i_nlink ...
ES> But I suppose there may be other
On Fri, 2007-01-12 at 12:04 -0500, Jeff Garzik wrote:
> Soeren Sonnenburg wrote:
> > Dear all,
> >
> > I'd like to try out SATA hotplugging using a SIL3114. Though I was
> > harvesting the web, I could not find any useful information how this is
> > done in practice.
> >
> > Well I realized that
Subject: Enable SPU switch notification to detect currently active SPU tasks.
From: Maynard Johnson <[EMAIL PROTECTED]>
This patch adds to the capability of spu_switch_event_register so that the
caller is also notified of currently active SPU tasks. It also exports
spu_switch_event_register
On Fri, 12 Jan 2007 13:44:05 -0800 Andrew Morton wrote:
> On Fri, 12 Jan 2007 21:00:15 +
> Russell King <[EMAIL PROTECTED]> wrote:
>
> > Could we please have this (or a proper fix) in before 2.6.20 to resolve
> > the regression please?
> >
> >
> > ...
> >
> > --- a/drivers/hid/Kconfig
> >
Alex Tomas wrote:
>> Eric Sandeen (ES) writes:
> ES> I tend to agree, chatting w/ Al I think he does too. :) I'll test
> ES> a patch that kicks out ext3_link() with -ENOENT at the top, and resubmit
> ES> that if things go well.
>
> shouldn't VFS do that?
Al says "no" and I'm not
1 - 100 of 520 matches
Mail list logo
