On (15/11/07 02:39), Andrew Morton didst pronounce:
> On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
>
> > This patch is a fix for 2.6.24.
> >
> > Ordinarily the size of a pageblock is determined at compile-time based on
> > the
> > hugepage size. On PPC64, the
All of our machines with QLogics ISP1020 cards seem to have lost them on
boot with 2.6.24-rc1-mm1+hotfixes.
# lspci
:00:0a.0 SCSI storage controller: QLogic Corp. ISP1020 Fast-wide
SCSI (rev 05)
# lspci -n
:00:0a.0 0100: 1077:1020 (rev 05)
# lspci -v -v
:00:0a.0 SCSI storage
From: Ingo Molnar <[EMAIL PROTECTED]>
Date: Thu, 15 Nov 2007 11:43:32 +0100
> The crash logs contain this:
>
> VFS: Mounted root (ext3 filesystem) readonly.
> Freeing unused kernel memory: 396k freed
> Write protecting the kernel read-only data: 2056k
> udev: renamed network interface eth1
* David Miller <[EMAIL PROTECTED]> wrote:
> From: Matt Mackall <[EMAIL PROTECTED]>
> Date: Wed, 14 Nov 2007 17:37:13 -0600
>
> > No, the usual strategy for debugging problems -outside- SLOB is to
> > switch to another allocator with more extensive debugging facilities.
>
> Ok, so the thing we
From: Julia Lawall <[EMAIL PROTECTED]>
pci_get_class implicitly does a pci_dev_put on its second argument, so
pci_dev_put is only needed if there is a break out of the loop.
The semantic match detecting this problem is as follows:
//
@@
expression dev;
expression E;
@@
* pci_dev_put(dev)
On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
> This patch is a fix for 2.6.24.
>
> Ordinarily the size of a pageblock is determined at compile-time based on the
> hugepage size. On PPC64, the hugepage size is determined at runtime based on
> what is supported by the
From: Julia Lawall <[EMAIL PROTECTED]>
pci_get_class implicitly does a pci_dev_put on its second argument, so
pci_dev_put is only needed if there is a break out of the loop.
The semantic match detecting this problem is as follows:
//
@@
expression dev;
expression E;
@@
* pci_dev_put(dev)
Fixes section mismatch below.
WARNING: vmlinux.o(.text+0x946b5): Section mismatch: reference to .init.text:'
__alloc_bootmem_node (between 'vmemmap_alloc_block' and 'vmemmap_pgd_populate')
Changelog
- changed bootmem alloc wrapper function's name to be
__earlyonly_bootmem_alloc().
On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
> This patch is a fix for 2.6.24.
>
> Ordinarily the size of a pageblock is determined at compile-time based on the
> hugepage size. On PPC64, the hugepage size is determined at runtime based on
> what is supported by the
Changes __meminit to __init_refok.
==
WARNING: vmlinux.o(.text+0x1d07c): Section mismatch: reference to
.init.text:find_e820_area (between 'init_memory_mapping' and 'arch_add_memory')
==
Changelog:
* changes __init_refok from find_early_table_space() to
init_memory_mapping().
Signed-off-by:
memory hotplug fix against 2.6.23-rc2-mm1.
Changelog
- Divided into 3 patches
- dropped patch against mm/sparse.c ( This was my misunderstanding.)
- merged Andy's suggestion.
All patches are related to memory hotplug.
[1/3] ... export memory_add_physaddr_to_nid to acpi memory hotplug
[2/3]
Fix following reference error (when CONFIG_ACPI_HOTPLUG_MEMORY=m)
==
ERROR: "memory_add_physaddr_to_nid" [drivers/acpi/acpi_memhotplug.ko]
undefined!
==
Changelog:
- EXPORT_SYMBOL to EXPORT_SYMBOL_GPL.
Signed-off-by: KAMEZAWA Hiroyuki <[EMAIL PROTECTED]>
arch/x86/mm/srat_64.c |1 +
1
This patch is a fix for 2.6.24.
Ordinarily the size of a pageblock is determined at compile-time based on the
hugepage size. On PPC64, the hugepage size is determined at runtime based on
what is supported by the machine. With legacy machines such as iSeries that do
not support hugepages,
On Wed, 2007-11-14 at 22:42 +0100, Rafael J. Wysocki wrote:
> Perhaps it just can't find the root filesystem at all?
Indeed - thanks for the input.
My supposed "good" source config didn't match the running kernel. A
"work in progress" I had obviously forgotten about.
Apologies for having
On Thu, 15 Nov 2007 09:39:15 +
Andy Whitcroft <[EMAIL PROTECTED]> wrote:
> Can you explain "this is bug" for me. The routine was __init_refok and
> therefore ! __init and therefore always present. The logic there must
> guarentee it only calls the bootmem allocator in early boot, and the
When testing some of the later 2.6.24-rc2-mm1+hotfix combinations on three
of our test systems one job from each batch (1/4) failed. In each case the
machine appears to have booted normally all the way to a login: prompt.
However in the failed boots the networking though apparently initialised
On Thu, Nov 15, 2007 at 01:44:46AM -0800, Andrew Morton wrote:
> On Thu, 15 Nov 2007 12:11:58 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>
> > Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
> > (1) and during 2.6.24 cycle (2):
> >
> > kernel_restart
> >
On Thu, 15 Nov 2007 12:11:58 +0300 Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
> Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
> (1) and during 2.6.24 cycle (2):
>
> kernel_restart
> sys_reboot
> [garbage]
> Code: 8b 88 a8 00 00 00 85 c9 74 04 89
> EIP is
On 13-11-2007 19:57, Jon Nelson wrote:
> I'm not sure if this is the right place,
Me too. Looks more like acpi or pci problem. Did you try to experiment
with something like: pci=noacpi or acpi=off boot parameters? Probably
some point to your .config and dmesg should be useful too, so taking
it to
On Thu, Nov 15, 2007 at 01:29:19PM +0900, KAMEZAWA Hiroyuki wrote:
> Fixes for memory hotplug compile and .section handling.
>
> This patch fixes following bugs
> ==
> WARNING: vmlinux.o(.text+0x1d07c): Section mismatch: reference to .init.text:f
> ind_e820_area (between 'init_memory_mapping' and
remove dead config CONFIG_HAS_COMPAT_EPOLL_EVENT symbol
Signed-off-by: Jiri Olsa <[EMAIL PROTECTED]>
---
fs/compat.c| 49
include/linux/compat.h |8 ---
2 files changed, 0 insertions(+), 57 deletions(-)
diff --git
Grzegorz Kulewski wrote:
On Wed, 7 Feb 2007, Tejun Heo wrote:
Grzegorz Kulewski wrote:
It worked very well for half a year but with one disk (IIRC it was even
plugged into second channel but I wont bet on it). Now I have second
disk
(very similar) and it is always put into PIO4 mode:
[
Patric Karlsson wrote:
Grzegorz Kulewski wrote:
On Wed, 7 Feb 2007, Tejun Heo wrote:
Grzegorz Kulewski wrote:
It worked very well for half a year but with one disk (IIRC it was
even
plugged into second channel but I wont bet on it). Now I have
second disk
(very similar) and it is always
On Thu, 15 Nov 2007 00:56:57 -0800
Andrew Morton <[EMAIL PROTECTED]> wrote:
> eek.
>
> What I now need to do with this patch is
>
> - Work out which patches in -mm it is actually fixing.
>
> - If that is more than one patch then split this patch up into multiple ones.
>
> - Stage the one or
Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
(1) and during 2.6.24 cycle (2):
kernel_restart
sys_reboot
[garbage]
Code: 8b 88 a8 00 00 00 85 c9 74 04 89
EIP is at device_shutdown+0x32/0x60
which corresponds to the following place:
c110659c :
On Thu, 15 Nov 2007 00:20:33 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> > > - gpio_direction_input()/gpio_direction_output() implicitly
> > > request the pins, if they weren't already requested.
> >
> > Eek, that's completely wrong. Allowing to access a resource _before_
> > it is
On Wednesday 14 November 2007, Nick Piggin wrote:
> > > > All this does is prevent constant and needless checking for
> > > > "do you want to preempt me now?" "now?" "now?" in "now?" the
> > > > middle "now?" of "now?" i/o "now?" loops.
> > >
> > > Actually that's wrong.
> >
> > Certainly it's
On Thu, 2007-11-15 at 16:14 +0800, Dave Young wrote:
> On Thu, Nov 15, 2007 at 03:38:13AM +0100, Kay Sievers wrote:
> > On Thu, 2007-11-15 at 09:01 +0800, Dave Young wrote:
> > > On Nov 15, 2007 5:27 AM, Kay Sievers <[EMAIL PROTECTED]> wrote:
> > > > On Wed, 2007-11-14 at 20:19 +0100, Jiri Kosina
Hi, thanks for the reply. :)
Bartlomiej Zolnierkiewicz wrote:
Hi,
On Monday 12 November 2007, Andrew Morton wrote:
On Fri, 09 Nov 2007 11:22:41 +0100 Jonas Stare <[EMAIL PROTECTED]> wrote:
Hi.
This week I ran into a strange hardware problem. During boot I got a 35
second delay while
On Thursday 15 November 2007 19:17, David Brownell wrote:
> On Wednesday 14 November 2007, Nick Piggin wrote:
> > > > > All this does is prevent constant and needless checking for
> > > > > "do you want to preempt me now?" "now?" "now?" in "now?" the
> > > > > middle "now?" of "now?" i/o "now?"
On Thu, 15 Nov 2007 13:29:19 +0900 KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
> Fixes for memory hotplug compile and .section handling.
>
> This patch fixes following bugs
> ==
> WARNING: vmlinux.o(.text+0x1d07c): Section mismatch: reference to .init.text:f
> ind_e820_area (between
Hello,
On Wed, Nov 14, 2007 at 08:20:22PM -0800, dean gaudet wrote:
> On Wed, 14 Nov 2007, Andi Kleen wrote:
>
> > Later a syscall might be needed with event multiplexing, but that seems
> > more like a far away non essential feature.
>
> actually multiplexing is the main feature i am in need
On Wed, 14 Nov 2007 22:50:17 -0800
David Brownell <[EMAIL PROTECTED]> wrote:
> > Since this is the code that runs under the lock
>
> No, there's more than that. This is what runs under it in
> the hot paths, yes, but the gpio request/free paths do
> more work than this. (That includes
On Thu, Nov 15 2007, Rusty Russell wrote:
> On Wednesday 14 November 2007 23:39:31 Jens Axboe wrote:
> > On Wed, Nov 14 2007, Rusty Russell wrote:
> > > Hi Jens,
> > >
> > > As you asked for some time ago. Of course, it turns out that the
> > > eject command ignores the error anyway, but it's
On Wednesday 14 November 2007, Thomas Gleixner wrote:
> On Wed, 14 Nov 2007, David Brownell wrote:
> > > The protection of the chip list can be converted to a mutex and
> > > does not need to be a spinlock at all.
> >
> > No, we still need to use a spinlock to protect table changes.
> > The
Herbert Xu <[EMAIL PROTECTED]> writes:
> That's strong static typing. Netlink is 90% strong static
> typing plus 10% strong dynamic typing. That is, it'll tell
> you at run-time if you give it the wrong netlink attribute.
Well it tells you EINVAL no matter what is wrong.
That's roughly
On Wed, Nov 14, 2007 at 06:29:17PM -0800, Denys Vlasenko wrote:
> On Wednesday 14 November 2007 09:08, Jesper Nilsson wrote:
> > /* Not true gettimeofday, only checks the jiffies (uptime) + useconds */
> > -void __INLINE__ do_gettimeofday_fast(struct fasttime_t *tv)
> > +inline void
Eric Dumazet <[EMAIL PROTECTED]> writes:
>
> http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/os/timers.c#1106
>
> I would say this code was OK 10 years ago.
I would have expected 1997 compilers to already do these standard muliplication
optimizations.
> Now that a
On Thu, Nov 15, 2007 at 03:38:13AM +0100, Kay Sievers wrote:
> On Thu, 2007-11-15 at 09:01 +0800, Dave Young wrote:
> > On Nov 15, 2007 5:27 AM, Kay Sievers <[EMAIL PROTECTED]> wrote:
> > > On Wed, 2007-11-14 at 20:19 +0100, Jiri Kosina wrote:
> > > > On Wed, 14 Nov 2007, Kay Sievers wrote:
> > >
On Wed, 14 Nov 2007 at 20:21 +, Russell Leighton wrote:
>
> Bryan Cantrill of Sun (ala DTrace) has a notion of perfect code:
>
> http://blogs.sun.com/bmc/entry/on_i_dreaming_in_code
>
> He also has some examples (from bottom comment section of above):
>
> >
> >
> >Can you list a
On Thursday 15 November 2007 06:19, Nick Piggin wrote:
> On Thursday 15 November 2007 19:17, David Brownell wrote:
> > On Wednesday 14 November 2007, Nick Piggin wrote:
> > > > > > All this does is prevent constant and needless checking for
> > > > > > "do you want to preempt me now?" "now?"
Hi,
On Thu, Nov 15, 2007 at 12:11:10PM +1100, Paul Mackerras wrote:
> David Miller writes:
>
> > From: Paul Mackerras <[EMAIL PROTECTED]>
> > Date: Thu, 15 Nov 2007 10:12:22 +1100
> >
> > > *I* never had a problem with a few extra system calls. I don't
> > > understand why you (apparently)
On Wed, 14 Nov 2007, Christian Kujau wrote:
Yes, the nfsd process only got stuck when I did ls(1) (with or without -l) on
a NFS share which contained a XFS partition.
Since NFS was not working (the nfsd processes were already in D state), to
mount a CIFS share from the very same server (and
On Thursday 15 November 2007 17:28, David Brownell wrote:
> On Tuesday 13 November 2007, Nick Piggin wrote:
> > > All this does is prevent constant and needless checking for
> > > "do you want to preempt me now?" "now?" "now?" in "now?" the
> > > middle "now?" of "now?" i/o "now?" loops.
> >
> >
Paul Mackerras <[EMAIL PROTECTED]> wrote:
>
> Well you must mean something different by "strong typing" from the
> rest of us. Strong typing means that the compiler can check that you
> have passed in the correct types of arguments, but the compiler
> doesn't have any visibility into what
Paul Mackerras [EMAIL PROTECTED] wrote:
Well you must mean something different by strong typing from the
rest of us. Strong typing means that the compiler can check that you
have passed in the correct types of arguments, but the compiler
doesn't have any visibility into what structures are
On Wed, 14 Nov 2007, Christian Kujau wrote:
Yes, the nfsd process only got stuck when I did ls(1) (with or without -l) on
a NFS share which contained a XFS partition.
Since NFS was not working (the nfsd processes were already in D state), to
mount a CIFS share from the very same server (and
On Thursday 15 November 2007 17:28, David Brownell wrote:
On Tuesday 13 November 2007, Nick Piggin wrote:
All this does is prevent constant and needless checking for
do you want to preempt me now? now? now? in now? the
middle now? of now? i/o now? loops.
Actually that's wrong.
On Thursday 15 November 2007 06:19, Nick Piggin wrote:
On Thursday 15 November 2007 19:17, David Brownell wrote:
On Wednesday 14 November 2007, Nick Piggin wrote:
All this does is prevent constant and needless checking for
do you want to preempt me now? now? now? in now? the
Hi,
On Thu, Nov 15, 2007 at 12:11:10PM +1100, Paul Mackerras wrote:
David Miller writes:
From: Paul Mackerras [EMAIL PROTECTED]
Date: Thu, 15 Nov 2007 10:12:22 +1100
*I* never had a problem with a few extra system calls. I don't
understand why you (apparently) do.
We're
On Wed, 14 Nov 2007 at 20:21 +, Russell Leighton wrote:
Bryan Cantrill of Sun (ala DTrace) has a notion of perfect code:
http://blogs.sun.com/bmc/entry/on_i_dreaming_in_code
He also has some examples (from bottom comment section of above):
Can you list a small number of
Eric Dumazet [EMAIL PROTECTED] writes:
http://cvs.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/os/timers.c#1106
I would say this code was OK 10 years ago.
I would have expected 1997 compilers to already do these standard muliplication
optimizations.
Now that a processor
On Thu, Nov 15, 2007 at 03:38:13AM +0100, Kay Sievers wrote:
On Thu, 2007-11-15 at 09:01 +0800, Dave Young wrote:
On Nov 15, 2007 5:27 AM, Kay Sievers [EMAIL PROTECTED] wrote:
On Wed, 2007-11-14 at 20:19 +0100, Jiri Kosina wrote:
On Wed, 14 Nov 2007, Kay Sievers wrote:
Could it
On Wed, Nov 14, 2007 at 06:29:17PM -0800, Denys Vlasenko wrote:
On Wednesday 14 November 2007 09:08, Jesper Nilsson wrote:
/* Not true gettimeofday, only checks the jiffies (uptime) + useconds */
-void __INLINE__ do_gettimeofday_fast(struct fasttime_t *tv)
+inline void
Herbert Xu [EMAIL PROTECTED] writes:
That's strong static typing. Netlink is 90% strong static
typing plus 10% strong dynamic typing. That is, it'll tell
you at run-time if you give it the wrong netlink attribute.
Well it tells you EINVAL no matter what is wrong.
That's roughly similar to
On Wednesday 14 November 2007, Thomas Gleixner wrote:
On Wed, 14 Nov 2007, David Brownell wrote:
The protection of the chip list can be converted to a mutex and
does not need to be a spinlock at all.
No, we still need to use a spinlock to protect table changes.
The reason for that is
On Wed, 14 Nov 2007 22:50:17 -0800
David Brownell [EMAIL PROTECTED] wrote:
Since this is the code that runs under the lock
No, there's more than that. This is what runs under it in
the hot paths, yes, but the gpio request/free paths do
more work than this. (That includes direction
On Thu, Nov 15 2007, Rusty Russell wrote:
On Wednesday 14 November 2007 23:39:31 Jens Axboe wrote:
On Wed, Nov 14 2007, Rusty Russell wrote:
Hi Jens,
As you asked for some time ago. Of course, it turns out that the
eject command ignores the error anyway, but it's nice that it
On Thu, 15 Nov 2007 13:29:19 +0900 KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote:
Fixes for memory hotplug compile and .section handling.
This patch fixes following bugs
==
WARNING: vmlinux.o(.text+0x1d07c): Section mismatch: reference to .init.text:f
ind_e820_area (between
Hello,
On Wed, Nov 14, 2007 at 08:20:22PM -0800, dean gaudet wrote:
On Wed, 14 Nov 2007, Andi Kleen wrote:
Later a syscall might be needed with event multiplexing, but that seems
more like a far away non essential feature.
actually multiplexing is the main feature i am in need of. there
On Thursday 15 November 2007 19:17, David Brownell wrote:
On Wednesday 14 November 2007, Nick Piggin wrote:
All this does is prevent constant and needless checking for
do you want to preempt me now? now? now? in now? the
middle now? of now? i/o now? loops.
Actually that's
Hi, thanks for the reply. :)
Bartlomiej Zolnierkiewicz wrote:
Hi,
On Monday 12 November 2007, Andrew Morton wrote:
On Fri, 09 Nov 2007 11:22:41 +0100 Jonas Stare [EMAIL PROTECTED] wrote:
Hi.
This week I ran into a strange hardware problem. During boot I got a 35
second delay while waiting
On Thu, 2007-11-15 at 16:14 +0800, Dave Young wrote:
On Thu, Nov 15, 2007 at 03:38:13AM +0100, Kay Sievers wrote:
On Thu, 2007-11-15 at 09:01 +0800, Dave Young wrote:
On Nov 15, 2007 5:27 AM, Kay Sievers [EMAIL PROTECTED] wrote:
On Wed, 2007-11-14 at 20:19 +0100, Jiri Kosina wrote:
On Wednesday 14 November 2007, Nick Piggin wrote:
All this does is prevent constant and needless checking for
do you want to preempt me now? now? now? in now? the
middle now? of now? i/o now? loops.
Actually that's wrong.
Certainly it's right for the mainstream kernel.
On Thu, 15 Nov 2007 00:20:33 -0800
David Brownell [EMAIL PROTECTED] wrote:
- gpio_direction_input()/gpio_direction_output() implicitly
request the pins, if they weren't already requested.
Eek, that's completely wrong. Allowing to access a resource _before_
it is assigned and
Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
(1) and during 2.6.24 cycle (2):
kernel_restart
sys_reboot
[garbage]
Code: 8b 88 a8 00 00 00 85 c9 74 04 89
EIP is at device_shutdown+0x32/0x60
which corresponds to the following place:
c110659c
On Thu, 15 Nov 2007 00:56:57 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
eek.
What I now need to do with this patch is
- Work out which patches in -mm it is actually fixing.
- If that is more than one patch then split this patch up into multiple ones.
- Stage the one or more fixup
Patric Karlsson wrote:
Grzegorz Kulewski wrote:
On Wed, 7 Feb 2007, Tejun Heo wrote:
Grzegorz Kulewski wrote:
It worked very well for half a year but with one disk (IIRC it was
even
plugged into second channel but I wont bet on it). Now I have
second disk
(very similar) and it is always
Grzegorz Kulewski wrote:
On Wed, 7 Feb 2007, Tejun Heo wrote:
Grzegorz Kulewski wrote:
It worked very well for half a year but with one disk (IIRC it was even
plugged into second channel but I wont bet on it). Now I have second
disk
(very similar) and it is always put into PIO4 mode:
[
remove dead config CONFIG_HAS_COMPAT_EPOLL_EVENT symbol
Signed-off-by: Jiri Olsa [EMAIL PROTECTED]
---
fs/compat.c| 49
include/linux/compat.h |8 ---
2 files changed, 0 insertions(+), 57 deletions(-)
diff --git
On Thu, Nov 15, 2007 at 01:29:19PM +0900, KAMEZAWA Hiroyuki wrote:
Fixes for memory hotplug compile and .section handling.
This patch fixes following bugs
==
WARNING: vmlinux.o(.text+0x1d07c): Section mismatch: reference to .init.text:f
ind_e820_area (between 'init_memory_mapping' and
On 13-11-2007 19:57, Jon Nelson wrote:
I'm not sure if this is the right place,
Me too. Looks more like acpi or pci problem. Did you try to experiment
with something like: pci=noacpi or acpi=off boot parameters? Probably
some point to your .config and dmesg should be useful too, so taking
it to
On Thu, 15 Nov 2007 12:11:58 +0300 Alexey Dobriyan [EMAIL PROTECTED] wrote:
Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
(1) and during 2.6.24 cycle (2):
kernel_restart
sys_reboot
[garbage]
Code: 8b 88 a8 00 00 00 85 c9 74 04 89
EIP is at
On Thu, Nov 15, 2007 at 01:44:46AM -0800, Andrew Morton wrote:
On Thu, 15 Nov 2007 12:11:58 +0300 Alexey Dobriyan [EMAIL PROTECTED] wrote:
Three boxes rarely oops during reboot or poweroff with 2.6.24-rc2-mm1
(1) and during 2.6.24 cycle (2):
kernel_restart
sys_reboot
When testing some of the later 2.6.24-rc2-mm1+hotfix combinations on three
of our test systems one job from each batch (1/4) failed. In each case the
machine appears to have booted normally all the way to a login: prompt.
However in the failed boots the networking though apparently initialised
On Thu, 15 Nov 2007 09:39:15 +
Andy Whitcroft [EMAIL PROTECTED] wrote:
Can you explain this is bug for me. The routine was __init_refok and
therefore ! __init and therefore always present. The logic there must
guarentee it only calls the bootmem allocator in early boot, and the logic
On Wed, 2007-11-14 at 22:42 +0100, Rafael J. Wysocki wrote:
Perhaps it just can't find the root filesystem at all?
Indeed - thanks for the input.
My supposed good source config didn't match the running kernel. A
work in progress I had obviously forgotten about.
Apologies for having disturbed
This patch is a fix for 2.6.24.
Ordinarily the size of a pageblock is determined at compile-time based on the
hugepage size. On PPC64, the hugepage size is determined at runtime based on
what is supported by the machine. With legacy machines such as iSeries that do
not support hugepages,
memory hotplug fix against 2.6.23-rc2-mm1.
Changelog
- Divided into 3 patches
- dropped patch against mm/sparse.c ( This was my misunderstanding.)
- merged Andy's suggestion.
All patches are related to memory hotplug.
[1/3] ... export memory_add_physaddr_to_nid to acpi memory hotplug
[2/3]
Fix following reference error (when CONFIG_ACPI_HOTPLUG_MEMORY=m)
==
ERROR: memory_add_physaddr_to_nid [drivers/acpi/acpi_memhotplug.ko]
undefined!
==
Changelog:
- EXPORT_SYMBOL to EXPORT_SYMBOL_GPL.
Signed-off-by: KAMEZAWA Hiroyuki [EMAIL PROTECTED]
arch/x86/mm/srat_64.c |1 +
1
On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
This patch is a fix for 2.6.24.
Ordinarily the size of a pageblock is determined at compile-time based on the
hugepage size. On PPC64, the hugepage size is determined at runtime based on
what is supported by the
Changes __meminit to __init_refok.
==
WARNING: vmlinux.o(.text+0x1d07c): Section mismatch: reference to
.init.text:find_e820_area (between 'init_memory_mapping' and 'arch_add_memory')
==
Changelog:
* changes __init_refok from find_early_table_space() to
init_memory_mapping().
Signed-off-by:
Fixes section mismatch below.
WARNING: vmlinux.o(.text+0x946b5): Section mismatch: reference to .init.text:'
__alloc_bootmem_node (between 'vmemmap_alloc_block' and 'vmemmap_pgd_populate')
Changelog
- changed bootmem alloc wrapper function's name to be
__earlyonly_bootmem_alloc().
On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
This patch is a fix for 2.6.24.
Ordinarily the size of a pageblock is determined at compile-time based on the
hugepage size. On PPC64, the hugepage size is determined at runtime based on
what is supported by the
From: Julia Lawall [EMAIL PROTECTED]
pci_get_class implicitly does a pci_dev_put on its second argument, so
pci_dev_put is only needed if there is a break out of the loop.
The semantic match detecting this problem is as follows:
// smpl
@@
expression dev;
expression E;
@@
* pci_dev_put(dev)
From: Julia Lawall [EMAIL PROTECTED]
pci_get_class implicitly does a pci_dev_put on its second argument, so
pci_dev_put is only needed if there is a break out of the loop.
The semantic match detecting this problem is as follows:
// smpl
@@
expression dev;
expression E;
@@
* pci_dev_put(dev)
* David Miller [EMAIL PROTECTED] wrote:
From: Matt Mackall [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 17:37:13 -0600
No, the usual strategy for debugging problems -outside- SLOB is to
switch to another allocator with more extensive debugging facilities.
Ok, so the thing we still can do
All of our machines with QLogics ISP1020 cards seem to have lost them on
boot with 2.6.24-rc1-mm1+hotfixes.
# lspci
:00:0a.0 SCSI storage controller: QLogic Corp. ISP1020 Fast-wide
SCSI (rev 05)
# lspci -n
:00:0a.0 0100: 1077:1020 (rev 05)
# lspci -v -v
:00:0a.0 SCSI storage
From: Ingo Molnar [EMAIL PROTECTED]
Date: Thu, 15 Nov 2007 11:43:32 +0100
The crash logs contain this:
VFS: Mounted root (ext3 filesystem) readonly.
Freeing unused kernel memory: 396k freed
Write protecting the kernel read-only data: 2056k
udev: renamed network interface eth1 to eth0
On (15/11/07 02:39), Andrew Morton didst pronounce:
On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
This patch is a fix for 2.6.24.
Ordinarily the size of a pageblock is determined at compile-time based on
the
hugepage size. On PPC64, the hugepage size is
On Thursday 15 November 2007 21:43, Ingo Molnar wrote:
* David Miller [EMAIL PROTECTED] wrote:
From: Matt Mackall [EMAIL PROTECTED]
Date: Wed, 14 Nov 2007 17:37:13 -0600
No, the usual strategy for debugging problems -outside- SLOB is to
switch to another allocator with more extensive
On Thu, 15 Nov 2007 10:52:38 + [EMAIL PROTECTED] (Mel Gorman) wrote:
Shouldn't this have been HUGETLB_PAGE_ORDER?
As a #define, possibly but as a static inline - definitly not.
In this context, the define is not used because set_pageblock_order()
is a no-op when
Signed-off-by: Uwe Kleine-König [EMAIL PROTECTED]
---
drivers/serial/Kconfig |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/serial/Kconfig b/drivers/serial/Kconfig
index d6ae38e..6d0c97a 100644
--- a/drivers/serial/Kconfig
+++ b/drivers/serial/Kconfig
@@
This is a documentation followup to 2e591bbc0d563e12f5a260fbbca0df7d5810910e
Signed-off-by: Uwe Kleine-König [EMAIL PROTECTED]
---
Documentation/initrd.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/Documentation/initrd.txt b/Documentation/initrd.txt
index
* David Miller [EMAIL PROTECTED] wrote:
Yeah I wish udev would just leave the damn devices alone.
It even does things like try to rename a network device to the same
name it already has, and other strange stuff.
But that log difference is a good clue.
Because udev can try to rename a
From: Ingo Molnar [EMAIL PROTECTED]
Date: Thu, 15 Nov 2007 12:03:25 +0100
now that it's reproducible again i'll try more direct debugging.
(Networking might not even be the cause of this - that was just a quick
first impression that i had.)
Btw., the .config is the result of automated
On Thursday 15 November 2007 16:37:51 Mathieu Desnoyers wrote:
* Rusty Russell ([EMAIL PROTECTED]) wrote:
On Thursday 15 November 2007 15:06:10 Mathieu Desnoyers wrote:
A - the NMI or MCE code calls any external kernel code (printk,
notify_die, spin_lock/unlock, die_nmi, lapic_wd_event
On (15/11/07 02:32), Andrew Morton didst pronounce:
On Thu, 15 Nov 2007 10:13:22 + [EMAIL PROTECTED] (Mel Gorman) wrote:
This patch is a fix for 2.6.24.
Ordinarily the size of a pageblock is determined at compile-time based on
the
hugepage size. On PPC64, the hugepage size is
Hi,
When I tryed to boot with qemu a 2.6.24-rc2-git5 with sysfs disabled,
the boot fails when trying to mount root partition:
VFS: Cannot open root device hda2 or unknown-block(0,0)
Please append a correct root= boot option; here are the available
partitions:
03002097152 hda0300
Alexey Dobriyan wrote:
On 11/15/07, Daniel Lezcano [EMAIL PROTECTED] wrote:
When I tryed to boot with qemu a 2.6.24-rc2-git5 with sysfs disabled,
the boot fails when trying to mount root partition:
VFS: Cannot open root device hda2 or unknown-block(0,0)
Please append a correct root= boot
401 - 500 of 890 matches
Mail list logo
