Hey all, more data on my bcm43xx problem report from a few weeks back.
By random chance I acquired a brain, and decided to rebuild my latest kernel
pull with as many debugging options on as I could stand. Got the below, plus
a dead keyboard (except for Magic SysRq) (but only if I let userspace
David Singleton writes:
Add variation of /proc/PID/smaps called /proc/PID/pagemaps.
Shows reference counts for individual pages instead of aggregate totals.
Allows more detailed memory usage information for memory analysis tools.
An example of the output shows the shared text VMA for ld.so and
No.
Other arch's arch_add_memory() and remove_memory() have been already
used for NUMA case too. But i386 didn't do it because just
contig_page_data is used.
Current NODE_DATA() macro is defined both case appropriately.
So, this #ifdef is redundant now.
Then I assume the
On Sun, Dec 10 2006, Elias Oltmanns wrote:
Hi Jens,
Elias Oltmanns [EMAIL PROTECTED] wrote:
So, here is a patch in which your remarks and suggestions have been
incorporated. Additionally, I've added the requested kernel doc file
and another sysfs attribute called protect_method. The
Prevent oops when an app tries to create a pipe while pipefs
is not mounted.
Signed-off-by: Chuck Ebbert [EMAIL PROTECTED]
--- 2.6.19.1-pre1-32.orig/fs/pipe.c
+++ 2.6.19.1-pre1-32/fs/pipe.c
@@ -839,9 +839,11 @@ static struct dentry_operations pipefs_d
static struct inode *
In-Reply-To: [EMAIL PROTECTED]
On Wed, 06 Dec 2006 13:58:00 +0100, Kasper Sandberg wrote:
Kasper, what problems (other that the annoying message) are you having?
if it had only been the messages i wouldnt have complained.
the thing is, when i get these messages, the app provoking them acts
On Mon, 11 Dec 2006 03:27:37 -0500
Chuck Ebbert [EMAIL PROTECTED] wrote:
Prevent oops when an app tries to create a pipe while pipefs
is not mounted.
Signed-off-by: Chuck Ebbert [EMAIL PROTECTED]
--- 2.6.19.1-pre1-32.orig/fs/pipe.c
+++ 2.6.19.1-pre1-32/fs/pipe.c
@@ -839,9 +839,11 @@
On Mon, Dec 11, 2006 at 03:27:37AM -0500, Chuck Ebbert wrote:
Prevent oops when an app tries to create a pipe while pipefs
is not mounted.
Signed-off-by: Chuck Ebbert [EMAIL PROTECTED]
That makes no sense at all. pipe_mnt is not created by userland
mount; it's created by init_pipe_fs() and
On Mon, 11 Dec 2006 00:55:57 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
I think the bug really is the running of populate_rootfs() before running
the initcalls, in init/main.c:init(). It's just more sensible to start
running userspace after the initcalls have been run. Statically-linked
Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Will appear later at
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.19/2.6.19-mm1/
- There's some new runtime debugging in kmap_atomic(). It catches one
buglet in in
On Mon, Dec 11, 2006 at 01:13:27AM -0800, Andrew Morton wrote:
On Mon, 11 Dec 2006 00:55:57 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
I think the bug really is the running of populate_rootfs() before running
the initcalls, in init/main.c:init(). It's just more sensible to start
CP == Cal Peake [EMAIL PROTECTED] writes:
CP I saw this with kernels v2.6.16, v2.6.17, and v2.6.18. Windows XP
CP however didn't seem to have any problems. So unless Windows
CP doesn't have window scaling on by default (or uses a workaround)
CP it could be a broken kernel.
XP doesn't do Window
On Sat, 2 Dec 2006, Karsten Weiss wrote:
On Sat, 2 Dec 2006, Christoph Anton Mitterer wrote:
I found a severe bug mainly by fortune because it occurs very rarely.
My test looks like the following: I have about 30GB of testing data on
This sounds very familiar! One of the Linux compute
From: Mauro Carvalho Chehab [EMAIL PROTECTED]
i2c defines two callbacks (inb/outb). On ia64, since it defines also two macros
with those names, it causes the following errors:
drivers/media/video/usbvision/usbvision-i2c.c:64:39: macro outb passed 4
arguments, but takes just 2
On Mon, Dec 11, 2006 at 01:25:45AM -0800, Andrew Morton wrote:
On Mon, 11 Dec 2006 09:21:30 +
Al Viro [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 01:13:27AM -0800, Andrew Morton wrote:
On Mon, 11 Dec 2006 00:55:57 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
I think
On Mon, 11 Dec 2006 09:21:30 +
Al Viro [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 01:13:27AM -0800, Andrew Morton wrote:
On Mon, 11 Dec 2006 00:55:57 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
I think the bug really is the running of populate_rootfs() before running
the
* Daniel Walker [EMAIL PROTECTED] wrote:
No functional changes, just broke up some long lines.
Although I didn't touch the long lines made up of strings.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
thanks, applied.
Ingo
-
To unsubscribe from this list: send the line
[EMAIL PROTECTED] wrote on 08-12-2006 14:58:24:
Jean-Paul Saman wrote:
[EMAIL PROTECTED] wrote on 06-12-2006 19:17:27:
Jean-Paul Saman wrote:
In populate_rootfs() the printk on line 554. It says Unpacking
initramfs.., which is confusing because if that line is reached
the
code
* Daniel Walker [EMAIL PROTECTED] wrote:
Sent this a long time ago, still exists.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
hm, what does this do, and why isnt it upstream?
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
On Sun, Dec 10, 2006 at 12:46:01AM +0100, Mike Galbraith wrote:
On Fri, 2006-12-08 at 17:42 +0100, Marc Haber wrote:
On Fri, Dec 08, 2006 at 10:38:12AM +0900, Fernando Luis Vázquez Cao wrote:
Does the patch below help?
http://marc.theaimsgroup.com/?l=linux-ext4m=116483980823714w=4
* Daniel Walker [EMAIL PROTECTED] wrote:
-#ifdef CONFIG_PREEMPT_RT
- if (irqs_disabled()) {
- msg = disabled hard interrupts;
- local_irq_enable();
- }
-#endif
thanks, applied.
Ingo
-
To unsubscribe from this list:
In-Reply-To: [EMAIL PROTECTED]
On Sun, 10 Dec 2006 22:19:04 -0600, Steve French wrote:
I don't remember any problems reported with plain text password
support on current cifs and I have certainly seen it negotiated with no
problem,
but I will double check with your reported flag
On 8/12/06 12:36, Jesper Juhl [EMAIL PROTECTED] wrote:
(please keep me on Cc when replying)
I have a server running Xen that regularly spews the following.
The box seems to survive fine regardless - just thought I'd let everyone know.
Harmless and not entirely unexpected. I'll add
In-Reply-To: [EMAIL PROTECTED]
On Mon, 11 Dec 2006 00:55:57 -0800, Andrew Morton wrote:
Prevent oops when an app tries to create a pipe while pipefs
is not mounted.
That's pretty lame. It means that pipes just won't work, so people who are
using pipes in their initramfs setups will just
Al Viro wrote:
On Mon, Dec 11, 2006 at 03:27:37AM -0500, Chuck Ebbert wrote:
Prevent oops when an app tries to create a pipe while pipefs
is not mounted.
[]
That makes no sense at all. pipe_mnt is not created by userland
mount; it's created by init_pipe_fs() and we'd bloody better
have it
On Mon, 11 Dec 2006 09:33:15 +
Al Viro [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 01:25:45AM -0800, Andrew Morton wrote:
On Mon, 11 Dec 2006 09:21:30 +
Al Viro [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 01:13:27AM -0800, Andrew Morton wrote:
On Mon, 11 Dec 2006
Emit a special VDSO_COOKIE for VDSO regions instead of simply marking
them as anon.
Signed-off-by: Amitabha Roy [EMAIL PROTECTED]
---
diff --git a/drivers/oprofile/buffer_sync.c b/drivers/oprofile/buffer_sync.c
index 78c2e6e..7f879db 100644
--- a/drivers/oprofile/buffer_sync.c
+++
On Dec 11 2006 10:26, Benny Amorsen wrote:
CP == Cal Peake [EMAIL PROTECTED] writes:
CP I saw this with kernels v2.6.16, v2.6.17, and v2.6.18. Windows XP
CP however didn't seem to have any problems. So unless Windows
CP doesn't have window scaling on by default (or uses a workaround)
CP it
this is against 2.6.19-git17
hope this correct
raz
On 12/11/06, Jens Axboe [EMAIL PROTECTED] wrote:
On Mon, Dec 11 2006, Raz Ben-Jehuda(caro) wrote:
On 12/11/06, Jens Axboe [EMAIL PROTECTED] wrote:
On Sun, Dec 10 2006, [EMAIL PROTECTED] wrote:
From: Raz Ben-Jehuda(caro) [EMAIL PROTECTED]
On Mon, Dec 11, 2006 at 01:47:27AM -0800, Andrew Morton wrote:
- populate_rootfs() puts stuff into the filesystem
- we then run initcalls.
- an initcall runs /sbin/hotplug.
We're now running userspace before all the initcalls have been executed.
Hence we're trying to run userspace when
On Mon, Dec 11 2006, Raz Ben-Jehuda(caro) wrote:
this is against 2.6.19-git17
hope this correct
Patch itself looks fine. Some general suggestions for the future:
- Don't top post on lkml
- Inline patches, and always include a description and a Signed-off-by
line.
-
On Mon, 11 Dec 2006 10:03:01 +
Al Viro [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 01:47:27AM -0800, Andrew Morton wrote:
- populate_rootfs() puts stuff into the filesystem
- we then run initcalls.
- an initcall runs /sbin/hotplug.
We're now running userspace before all
On Mon, Dec 11, 2006 at 02:17:18AM -0800, Andrew Morton wrote:
I think we should aim to have as many subsystems ready to go as possible -
ideally all of them. Right now we can potentially run userspace before
AIO, posix-timers, message-queues, BIO, networking, etc are ready to run.
It looks
On Mon, 11 Dec 2006 02:17:18 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
Said that, I think that pipes should be initialized early.
Judging by the comment there, the only reason we prepare the rootfs prior
to running initcalls is for firmware. So the sequence
run initcalls
This looks like a result of too many auto-merges. The
CONFIG_ARCH_VERSATILE case was handled a total of 6 times.
This kills 5 of them.
Signed-off-by: Paul Mundt [EMAIL PROTECTED]
--
drivers/net/smc91x.h | 90 ---
1 file changed, 90 deletions(-)
On Mon, 11 Dec 2006 10:22:07 +
Al Viro [EMAIL PROTECTED] wrote:
On Mon, Dec 11, 2006 at 02:17:18AM -0800, Andrew Morton wrote:
I think we should aim to have as many subsystems ready to go as possible -
ideally all of them. Right now we can potentially run userspace before
AIO,
OpenVZ team has discovered error inside generic_file_direct_write()
If generic_file_direct_IO() has fail (ENOSPC condition) it may have instantiated
a few blocks outside i_size. And fsck will complain about wrong i_size
(ext2, ext3 and reiserfs interpret i_size and biggest block difference as
On Mon, 11 Dec 2006, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run. It
looks like this, after dhclient finishes:
On Mon, Dec 11, 2006 at 02:27:46AM -0800, Andrew Morton wrote:
@@ -115,6 +115,11 @@ extern void setup_arch(char **);
#define device_initcall_sync(fn) __define_initcall(6s,fn,6s)
#define late_initcall(fn)__define_initcall(7,fn,7)
#define late_initcall_sync(fn)
Some tips of the design:
1. The prio_floor linked-list save all mutex is holded by each task in
time order. It is a stack data srtucture.
2. The prio_rmin member of the mutex_waiter is used for tracing current
minimum-value(highest) priority of this mutex.
3. It seem the
On Mon, Dec 11, 2006 at 02:34:36AM -0800, Andrew Morton wrote:
There are plenty of drivers in there using subsys_initcall, arch_initcall,
postcore_initcall, core_initcall and even one pure_initcall.
Heaven knows why. They're drivers :(
A heck of a lot of things can trigger an
On Mon, Dec 11, Chuck Ebbert wrote:
Why not create a new initcall category for things that must run before
early userspace?
Why do you want to continue with papering over the root cause?
Pick some janitor, let him write something that implements something
like make style dependencies for
On Mon, Dec 11, 2006 at 11:48:57AM +0100, Olaf Hering wrote:
On Mon, Dec 11, Chuck Ebbert wrote:
Why not create a new initcall category for things that must run before
early userspace?
Why do you want to continue with papering over the root cause?
Pick some janitor, let him write
As suggested by Andrew, we can use __attribute__((weak)) to get rid of
ARCH_HAVE_XTIME_LOCK
Please note I compiled, and boot tested on ia32 this patch, and it seems OK.
I compiled on x86_64 and got same resulting vmlinux image.
But I suspect some tools might have problems because vmlinux have
Andrew Morton wrote:
A heck of a lot of things can trigger an /sbin/hotplug run. It could well
be that Andrew's driver didn't want to run hotplug at all, but the kernel
did it anwyay. But as soon as the script appeared at /sbin/hotplug, and it
happened to use foo|bar: boom.
In fact, many
I 'm the maintainter of Trinity Rescue Kit (http://trinityhome.org/trk) ,
a live rescue distribution that tries (amongst many other features) to be
as generic as possible in terms of hardware detection. Therefore I include
all network and disk controller drivers in the kernel or as module.
I
Hi Geert, James, FBdev, MM folk,
Appended is my attempt to support the Hecuba/E-Ink display. I've added
some code to do deferred IO. This is there in order to hide the latency
associated with updating the display (500ms to 800ms). The method used
is to fake a framebuffer in memory. Then use
On Mon, 2006-12-11 12:06:08 +0100, Tom Kerremans [EMAIL PROTECTED] wrote:
I 'm the maintainter of Trinity Rescue Kit (http://trinityhome.org/trk) ,
a live rescue distribution that tries (amongst many other features) to be
as generic as possible in terms of hardware detection. Therefore I
On Sun, Dec 10, 2006 at 07:45:48PM +1300, Paul Collins wrote:
On my PowerBook when booting Linus's tree as of commit af1713e0 I get
something like this:
[blah blah]
ide0: Found Apple UniNorth ATA-6 controller, bus ID 3, irq 0
Probing IDE interface ide0...
hda: HTS541080G9AT00, ATA
Linus, please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/drzeus/mmc.git for-linus
to receive the following updates:
drivers/mmc/at91_mci.c | 346 +--
drivers/mmc/mmc_queue.c |4 -
drivers/mmc/sdhci.c |4 -
3 files
On 11/12/06, Keir Fraser [EMAIL PROTECTED] wrote:
On 8/12/06 12:36, Jesper Juhl [EMAIL PROTECTED] wrote:
(please keep me on Cc when replying)
I have a server running Xen that regularly spews the following.
The box seems to survive fine regardless - just thought I'd let everyone know.
I guess you forgot to add Andrew on CC.
Thanks,
Kirill
OpenVZ team has discovered error inside generic_file_direct_write()
If generic_file_direct_IO() has fail (ENOSPC condition) it may have
instantiated
a few blocks outside i_size. And fsck will complain about wrong i_size
(ext2, ext3 and
Mark the bit reversal functions as being const as they always return the same
output for any given input.
Signed-Off-By: David Howells [EMAIL PROTECTED]
---
include/linux/bitrev.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/bitrev.h
On Mon, Dec 11, 2006 at 01:42:48AM +, Sergio Monteiro Basto wrote:
On Sun, 2006-12-10 at 17:00 +0100, Adrian Bunk wrote:
+DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID,
quirk_via_irq);
This is back to state of kernel 2.6.16 final (without .x)
In kernel 2.6.17 final we got
On Mon, 2006-12-11 at 13:41 +0100, Adrian Bunk wrote:
On Mon, Dec 11, 2006 at 01:42:48AM +, Sergio Monteiro Basto wrote:
On Sun, 2006-12-10 at 17:00 +0100, Adrian Bunk wrote:
+DECLARE_PCI_FIXUP_ENABLE(PCI_VENDOR_ID_VIA, PCI_ANY_ID,
quirk_via_irq);
This is back to state of kernel
I am not able to compile latest kernel code in cygwin environment. It
fails for not ELF error always and exits. Any suggestions please?
Thanks.
--
Regards
Kalyan
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
On Sun, Dec 10, 2006 at 05:23:59PM -0800, Linus Torvalds wrote:
On Mon, 11 Dec 2006, Adrian Bunk wrote:
If life was that easy... ;-)
No. Life _is_ that easy.
If the 2.6.16 stable tree took a patch that was questionable, and we don't
know what the right answer to it is from the
David Howells wrote:
Mark the bit reversal functions as being const as they always return the same
output for any given input.
Signed-Off-By: David Howells [EMAIL PROTECTED]
---
include/linux/bitrev.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git
On Mon, Dec 11, 2006 at 12:48:10PM +, Sergio Monteiro Basto wrote:
On Mon, 2006-12-11 at 13:41 +0100, Adrian Bunk wrote:
On Mon, Dec 11, 2006 at 01:42:48AM +, Sergio Monteiro Basto wrote:
On Sun, 2006-12-10 at 17:00 +0100, Adrian Bunk wrote:
The code has been fixed to use kill_pid instead of kill_proc
fix the comments as well.
Signed-off-by: Eric W. Biederman [EMAIL PROTECTED]
---
drivers/char/vt_ioctl.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/char/vt_ioctl.c b/drivers/char/vt_ioctl.c
On 11/12/06, kalyan kumar [EMAIL PROTECTED] wrote:
I am not able to compile latest kernel code in cygwin environment. It
fails for not ELF error always and exits. Any suggestions please?
One suggestion: Don't do that.
That's not a supported way to build the kernel.
--
Jesper Juhl [EMAIL
I 'm the maintainer of Trinity Rescue Kit and I try to make kernels as
generic as possible, supporting the most possible hardware. So I compile
about any disk and nic driver. Processor arch is generic 586.
Here 's the command with which I made 2.6.19 crash.
'for i in *; do i=`echo $i | cut -d .
This patch converts the tracking of the user space watchdog process from
using a pid_t to use struct pid. This makes us safe from pid wrap around
issues and prepares the way for the pid namespace.
Signed-off-by: Eric W. Biederman [EMAIL PROTECTED]
---
fs/ncpfs/inode.c | 11
On Mon, Dec 11, 2006 at 12:35:36PM +, David Howells wrote:
diff --git a/include/linux/bitrev.h b/include/linux/bitrev.h
index 05e540d..032056b 100644
--- a/include/linux/bitrev.h
+++ b/include/linux/bitrev.h
@@ -5,11 +5,11 @@ #include linux/types.h
extern u8 const
On 12/3/06, Alessandro Suardi [EMAIL PROTECTED] wrote:
On 12/3/06, Alan [EMAIL PROTECTED] wrote:
ACPI: PCI Interrupt :00:1f.2[B] - Link [LNKB] - GSI 5 (level, low)
- IRQ5
PCI: Unable to reserve I/O region #1:[EMAIL PROTECTED] for device
:00:1f.2
ata_piix: probe of :00:1f.2
David Howells wrote:
Jeff Garzik [EMAIL PROTECTED] wrote:
* naked __attribute__ is ugly. define something short and memorable in
include/linux/compiler.h.
I'm not sure that's a good idea. You have to be careful not to cause confusion
with ordinary const.
It's all in the naming. You could
On Sun, Dec 10, 2006 at 11:46:44PM -0500, Chuck Ebbert wrote:
If your hardware can run the x86_64 kernel, try using that with your
i386 userspace. It works here...
Losing vm86() support can cause problems.
--
Matthew Garrett | [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line
Jeff Garzik [EMAIL PROTECTED] writes:
* another annotation to consider is C99 keyword 'restrict'.
This is useless as long as we compile with -fno-strict-aliasing (and I
don't think this will ever change).
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH,
This patch converts the tracking of the user space watchdog process from
using a pid_t to use struct pid. This makes us safe from pid wrap around
issues and prepares the way for the pid namespace.
Signed-off-by: Eric W. Biederman [EMAIL PROTECTED]
---
fs/ncpfs/inode.c | 11
* Oliver Bock [EMAIL PROTECTED] wrote:
Hi Ingo,
I tried to boot a vanilla 2.6.19 kernel with your 2.6.19-rt11 patch
but without success. However, the patch applied without a single error
and the vanilla kernel (without the patch) works fine so far. As my
screen just stays black and as
Andreas Schwab wrote:
Jeff Garzik [EMAIL PROTECTED] writes:
* another annotation to consider is C99 keyword 'restrict'.
This is useless as long as we compile with -fno-strict-aliasing (and I
don't think this will ever change).
Yes, just as useless as __attribute__((bitwise))... :)
calc_load() is called by timer interrupt to update avenrun[].
It currently calls nr_active() at each timer tick (HZ per second), while the
update of avenrun[] is done only once every 5 seconds. (LOAD_FREQ=5 Hz)
nr_active() is quite expensive on SMP machines, since it has to sum up
nr_running
On Fri, Dec 08 2006, Avantika Mathur wrote:
On Fri, 2006-12-08 at 13:05 +0100, Jens Axboe wrote:
On Thu, Dec 07 2006, Avantika Mathur wrote:
Hi Jens,
(you probably noticed now, but the [EMAIL PROTECTED] email is no longer
valid)
I saw that, thanks!
I've noticed a performance gap
On Mon, 11 Dec 2006 14:26:30 +0100
Alessandro Suardi [EMAIL PROTECTED] wrote:
I still have this problem in 2.6.19-git17. Is this expected behavior
or should it have been fixed by now ?
I don't currently have time to track the -git trees. Once 19rc1 appears
I'll take a look and send Linus
Akinobu Mita [EMAIL PROTECTED] wrote:
__attribute_pure__ ?
I'm not sure pure is better than const in this case. Although it *does* look
at a global variable (byte_rev_table), that variable is constant. In effect,
the functions output does only depend on its input. The R/O data it requires
is
Jeff Garzik [EMAIL PROTECTED] wrote:
I'm not sure that's a good idea. You have to be careful not to cause
confusion with ordinary const.
It's all in the naming. You could call it 'purefunc' or somesuch.
No, not pure. That's something else.
__attribute__ is very very ugly, an hinders
On Mon, Dec 11, 2006 at 02:47:55PM +1100, Benjamin Herrenschmidt wrote:
So at first, an unassigned resource has the IORESOURCE_UNSET flag set
(or is supposed to). pci_assign_resource() itself will clear that flag
if it succeeds.
However, pretty much nothing else checks that flag, so it's
[EMAIL PROTECTED] wrote:
Hi Guys,
I have a box running Fedora 2.6.5-1.358smp. Recently DNS and SMTP went
down on the box and both had to be restarted. I got the following
errors in the logs but dont have a clue what they mean.
Any help from you wonderful people would be most appreciated as
Jiri Kosina wrote:
On Mon, 11 Dec 2006, Andrew Morton wrote:
Temporarily at
http://userweb.kernel.org/~akpm/2.6.19-mm1/
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run. It
looks like this,
On Tue, 12 Dec 2006, Nick Piggin wrote:
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run.
It looks like this, after dhclient finishes:
Do you have CONFIG_DEBUG_VM turned on? I think we miss clearning
On Wed, 2006-11-29 at 14:21 -0800, Linus Torvalds wrote:
You could send me and the kernel mailing list a note about it anyway, of
course. (And perhaps pictures, if your dachshund is involved. Not that
we'd be interested, of course. No. Just so that we'd know to avoid it next
time).
Hi
Paul Mundt wrote:
This looks like a result of too many auto-merges. The
CONFIG_ARCH_VERSATILE case was handled a total of 6 times.
This kills 5 of them.
Signed-off-by: Paul Mundt [EMAIL PROTECTED]
applied
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
On Mon, Dec 11, 2006 at 12:58:07AM -0800, Andrew Morton wrote:
...
Changes since 2.6.19-rc6-mm2:
...
+x86_64-mm-i386-add-idle-notifier.patch
x86 tree update
...
This patch adds code and EXPORT_SYMBOL's that bloat the kernel for
everyone but are currently completely unused in the kernel
test.kernel.org testing seems to have shaken out a problem with the
kernel banner changing, introduced by this commit:
[PATCH] Fix linux banner utsname information
commit a2ee8649ba6d71416712e798276bf7c40b64e6e5
We first noticed it with 2.6.19-git13 as we use this version
Hi Aneesh,
I have posted a patch for that as well. You can check it at
http://lkml.org/lkml/2006/11/30/315.
BR,
Mauricio Lin.
On 12/10/06, Aneesh Kumar K.V [EMAIL PROTECTED] wrote:
Greg KH wrote:
On Tue, Nov 28, 2006 at 07:38:01PM +, Mauricio Lin wrote:
Hi Greg,
It is working now.
Hi there,
Well, after I was getting the error again, I now switched back to kernel
2.6.18.1, and going to check if I am getting the same errors. I'll keep
you posted about the progress. If a week have passed and no errors has
shown, I'll e-mail this again.
Thanks!
Jim.
Hi,
Well, that's
Jiri Kosina wrote:
On Tue, 12 Dec 2006, Nick Piggin wrote:
Am I the only one seeing something strange on ext3 with this kernel?
For example /etc/resolv.conf gets corrupted during the dhclient run.
It looks like this, after dhclient finishes:
Do you have CONFIG_DEBUG_VM turned on? I think
CFQ I/O scheduler does the following actions to
find out whether the request is sync:
rw = rq_data_dir(rq); = possible values for rw are 0 or 1
static inline pid_t cfq_queue_pid(struct task_struct *task, int rw)
{
if (rw == READ || rw == WRITE_SYNC) = second condition is always false
On Mon, 2006-12-11 at 10:27 +0100, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
Sent this a long time ago, still exists.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
hm, what does this do, and why isnt it upstream?
AFAIK, those locks are added in -rt . I'm not sure
On Mon, 11 Dec 2006, Chuck Ebbert wrote:
Prevent oops when an app tries to create a pipe while pipefs
is not mounted.
Have you actually seen this, or is this just from looking at code?
Quite frankly, if pipe_mnt is ever NULL, we're dead for lots of other
reasons.
In fact, pipe_mnt can't
* Daniel Walker [EMAIL PROTECTED] wrote:
On Mon, 2006-12-11 at 10:27 +0100, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
Sent this a long time ago, still exists.
Signed-Off-By: Daniel Walker [EMAIL PROTECTED]
hm, what does this do, and why isnt it upstream?
On Mon, 11 Dec 2006, Al Viro wrote:
On Mon, Dec 11, 2006 at 02:27:46AM -0800, Andrew Morton wrote:
@@ -115,6 +115,11 @@ extern void setup_arch(char **);
#define device_initcall_sync(fn) __define_initcall(6s,fn,6s)
#define late_initcall(fn) __define_initcall(7,fn,7)
On Tue, 12 Dec 2006, Nick Piggin wrote:
Do you have CONFIG_DEBUG_VM turned on? I think we miss clearning
BH_New in some places, thus causing an error path to zero the block
incorrectly if we hit an error that CONFIG_DEBUG_VM makes much more
likely.
Yes, I have. Will retry without it
On Mon, Dec 11, 2006 at 08:01:40AM -0800, Linus Torvalds wrote:
On Mon, 11 Dec 2006, Al Viro wrote:
On Mon, Dec 11, 2006 at 02:27:46AM -0800, Andrew Morton wrote:
@@ -115,6 +115,11 @@ extern void setup_arch(char **);
#define device_initcall_sync(fn) __define_initcall(6s,fn,6s)
Hi, [please CC me, as I am not subscribed]
after updating a RHEL4 box (EM64T based) to a plain 2.6.19 kernel, we
are seeing repeated occurences of the following messages (about every
45-50 minutes).
It is always the same server (a NetApp filer, mounted via the
user-space automounter amd) and
On Mon, 11 Dec 2006, David Howells wrote:
Mark the bit reversal functions as being const as they always return the same
output for any given input.
Well, we should mark the argument const too, no?
Does anythign actually improve from this? Also, we should actually use
__attribute_const__
On Mon, 2006-12-11 at 16:59 +0100, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
On Mon, 2006-12-11 at 10:27 +0100, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
Sent this a long time ago, still exists.
Signed-Off-By: Daniel Walker [EMAIL
On Mon, Dec 11 2006, Vasily Tarasov wrote:
CFQ I/O scheduler does the following actions to
find out whether the request is sync:
rw = rq_data_dir(rq); = possible values for rw are 0 or 1
static inline pid_t cfq_queue_pid(struct task_struct *task, int rw)
{
if (rw == READ || rw ==
Linus Torvalds [EMAIL PROTECTED] wrote:
Mark the bit reversal functions as being const as they always return the
same output for any given input.
Well, we should mark the argument const too, no?
The argument is just an integer; I'm not sure that marking it const actually
achieves
On Mon, 11 Dec 2006, David Howells wrote:
Ah. I thought that was just for supporting old versions of gcc. I didn't
realise it was for handling strange compilers.
I'm not sure how much (if at all) the Intel compiler is actually used, and
for all I know it may even support
1 - 100 of 739 matches
Mail list logo
