On Thu, 15 Nov 2007, Linus Torvalds wrote:
Unacceptable. We used to do exactly what your patch does, and it got fixed
once. We're not introducing that fundamentally broken concept again.
Examples of non-broken solutions:
(a) always use lowmem sizes (what we do now)
(b) always use total
There are a couple of things I don't understand on this one. And I
presume you thought the other two bug fixing patches I sent before this
were OK to go, since on my system
Thomas Gleixner wrote:
Still whitespace wreckage in your patches. I guess the kernel tree you
made your patches
Hi,
On Thursday 15 November 2007, Jonas Stare wrote:
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
Chuck Ebbert wrote:
On 11/15/2007 12:58 PM, Greg KH wrote:
On Thu, Nov 15, 2007 at 11:11:59AM -0500, Chuck Ebbert wrote:
On 11/15/2007 01:09 AM, Greg KH wrote:
-stable review patch. If anyone has any objections, please let us know.
--
From: Dave Young [EMAIL PROTECTED]
On Tue, Nov 13, 2007 at 10:34:37PM +, Russell King wrote:
On Tue, Nov 13, 2007 at 06:25:16PM +, Alan Cox wrote:
Given the wide range of ARM platforms today, it is utterly idiotic to
expect a single person to be able to provide responses for all ARM bugs.
I for one wish I'd never
Hi,
On Thu, 15 Nov 2007, Sam Ravnborg wrote:
Can we please can get some consistency in this?
We have a .config file for a reason, what's wrong with using it?
We need to set a selected few values in a few cases where we do
not have a .config file.
allmodconfig for x86 for instance. We
On Nov 15, 2007 6:36 PM, Jan Blunck [EMAIL PROTECTED] wrote:
On Wed, Nov 14, Torsten Kaiser wrote:
So I can create new directories, but not new files. Reading files works
normal.
The client is 2.6.24-rc2-mm1, the server 2.6.22-gentoo-r9.
I added Jan Blunck to the recipents,
On Thu, 15 Nov 2007, Linus Torvalds wrote:
The problem with HIGHMEM is that it causes various metadata (dentries,
inodes, page struct tables etc) to eat up memory prime real estate under
the same kind of conditions that also dirty a lot of memory. So the reason
we disallow HIGHMEM from
On Thu, 2007-11-15 at 13:14 -0800, Linus Torvalds wrote:
On Thu, 15 Nov 2007, Linus Torvalds wrote:
Unacceptable. We used to do exactly what your patch does, and it got fixed
once. We're not introducing that fundamentally broken concept again.
Examples of non-broken solutions:
(a)
On Thu, 15 Nov 2007, Micah Dowty wrote:
Yes, the Python test harness crashes, not the kernel. It's just
because on a kernel which exhibits this SMP balancer bug, within a
couple of test iterations I'll hit a case where cpu1 was almost
totally idle and the test harness divides by zero when
On Mon, Nov 12, 2007 at 09:08:10AM +0800, Zhu Yi wrote:
On Sat, 2007-11-10 at 20:49 +0100, Miguel Botón wrote:
Remove unnecesary code in iwl3945 and iwl4965 drivers.
final_mode variable is already initialized with the value of the
mode variable.
Signed-off-by: Miguel Boton [EMAIL
Am 12.11.2007 20:42 schrieb Alan Stern:
I don't like the second sentence very much. How about something like
this instead:
+If the device is disconnected or powered down while it is suspended,
+the disconnect method will be called instead of the resume or
+reset_resume method. This is
Hi Boris,
Actually the 19HS is the usa90 so it is included in the switch but
that isn't a problem.
I'm not familiar with the termios stuff on Linux so can you take a look
at the following modified code to see if this solves your NULL ptr problem?
Also,
Does cflag need to be set to anything
Problem identified by Miguel Botón [EMAIL PROTECTED], alternate
solution suggested by Zhu Yi [EMAIL PROTECTED], patch by me. :-)
Cc: Miguel Botón [EMAIL PROTECTED]
Cc: Zhu Yi [EMAIL PROTECTED]
Signed-off-by: John W. Linville [EMAIL PROTECTED]
---
drivers/net/wireless/iwlwifi/iwl3945-base.c |
On Thu, Nov 15, 2007 at 01:28:55PM -0800, Christoph Lameter wrote:
On Thu, 15 Nov 2007, Micah Dowty wrote:
Yes, the Python test harness crashes, not the kernel. It's just
because on a kernel which exhibits this SMP balancer bug, within a
couple of test iterations I'll hit a case where
On Thu, 15 Nov 2007 22:24:12 +0100
Torsten Kaiser [EMAIL PROTECTED] wrote:
The problem with the first bisect-try was, that everything between
bisect-good: r-o-bind-mounts-elevate-write-count-over-calls-to-vfs_rename
and
bisect-bad: use-struct-path-in-struct-svc_export
did not compile like
On Thu, 15 Nov 2007, Mark Knecht wrote:
On Nov 15, 2007 10:40 AM, Steven Rostedt [EMAIL PROTECTED] wrote:
Finally!
We are pleased to announce 2.6.24-rc2-rt1.
SNIP
Hi Steve,
snip!
As always thanks the the rt-kernel team for all you do.
On behalf of the rt-kernel team, you are
mark gross wrote:
On Wed, Nov 14, 2007 at 12:40:08PM -0800, Andrew Morton wrote:
On Wed, 14 Nov 2007 12:29:59 -0800 mark gross [EMAIL PROTECTED] wrote:
[ 102.366932] ===
[ 108.552031] printk: 31 messages suppressed.
All this BUG / WARNINGS are caused by *-qos*
Hi,
I started to look at this code when I was working on a project of
rewriting a dhcp-client.
I wanted to make the client use arp to determine if the offered
address was free or in use.
Thats when I noticed that linux machines responded in this, for me, odd way.
The problem is not really the
On Thu, 15 Nov 2007, Greg KH wrote:
This patch, as found by Dave Young, should fix the issue: I'll roll it
into my larger patchset so that Andrew will get it automatically next
release, but here it is for people to use now.
Hmm, something strange going on here. With this patch applied on
Boaz Harrosh wrote:
On Thu, Nov 15 2007 at 19:15 +0200, Matthew Dharm [EMAIL PROTECTED] wrote:
On Wed, Nov 14, 2007 at 10:23:09AM +0100, Gabriel C wrote:
Matthew Dharm wrote:
On Wed, Nov 14, 2007 at 06:33:39AM +0100, Gabriel C wrote:
Matthew Dharm wrote:
On Tue, Nov 13, 2007 at 07:49:24PM
The plot thickens - it looks like it might be some type
of problem interacting with the setup of my 4Gig DDR memory
and how I setup some translation windows in my MPC8548E
I realized this morning that I have an inbound/ output PEX window
Translation Setup for mapping all from/to PEX bus to
On Thu, 15 Nov 2007, Peter Zijlstra wrote:
But this problem is already an issue, Anton recently had a case where a
12GB highmem box locked up due to NTFS running out of lowmem - or
something like that.
Yeah. I always considered HIGHMEM to just be unusable. It's ok for
extending to 2-4GB
_PAGE_PCD maps a page with caching disabled, which is typically used
for mapping harware registers. Xen never allows it to be set on a
mapping, and unprivileged guests never need it since they can't see
the real underlying hardware. However, some uncached mappings are
made early when probing the
* Dave Hansen ([EMAIL PROTECTED]) wrote:
On Tue, 2007-11-13 at 14:33 -0500, Mathieu Desnoyers wrote:
linux-2.6-lttng/mm/page_io.c2007-11-13 09:49:35.0 -0500
@@ -114,6 +114,7 @@ int swap_writepage(struct page *page, st
rw |= (1 BIO_RW_SYNC);
On Thu, 15 Nov 2007 22:41:41 +0100 (CET)
Jiri Kosina [EMAIL PROTECTED] wrote:
On Thu, 15 Nov 2007, Greg KH wrote:
This patch, as found by Dave Young, should fix the issue: I'll roll it
into my larger patchset so that Andrew will get it automatically next
release, but here it is for
I'm looking at unifying asm-x86/pgalloc*.h, and so I'm trying to make
things as similar as possible between 32 and 64-bit.
Once difference is that 64-bit incrementally allocates all levels of the
pagetable, whereas 32-bit PAE preallocates the 4 pmds when it allocates
the pgd. What's the
On Thu, Nov 15, 2007 at 08:27:25AM -0800, Stephen Hemminger wrote:
I can't reproduce the users problem with the hardware I have. And
without the patch the dual
port board doesn't work. So it is a question of regression, versus
fixing pre-existing bugs.
I am okay with reverting the patch, as
The scenario that you've described is exactly what I have in mind as
well. The lack of this feature, which worked fine in 2.6.21, is
holding us back on updating the kernel in our LiveUSB distribution. I
think that this is a feature that would be more and more needed as
portable storage devices
On Thu, 15 Nov 2007, Andrew Morton wrote:
/dev/disk/by-id/scsi-SATA_HDS722516VLSA80_VN6D3ECDE5BD9D-part6: UNEXPECTED
INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Error writing block 1542 (Attempt to write block from filesystem resulted
in short write).
On Thu, Nov 15, 2007 at 10:24:05PM +0100, Roman Zippel wrote:
Hi,
On Thu, 15 Nov 2007, Sam Ravnborg wrote:
Can we please can get some consistency in this?
We have a .config file for a reason, what's wrong with using it?
We need to set a selected few values in a few cases where we
Jon Nelson wrote, On 11/15/2007 09:21 PM:
...
NOTE: to avoid list noise, I can make a bug out of this on
bugzilla.kernel.org and we can proceed from there if that is
preferred.
Why avoid list noise? These lists are made just for this. But, since
this case needs a lot of space for your
Linus Torvalds wrote:
So the _only_ explanation today for 12GB on a 32-bit machine is
(a) insanity
or
(b) being so lazy as to not bother to upgrade
and in either case, my personal reaction is I'm *not* crazy, and yes, I'm
lazy too, and I can't give a rats *ss about those problems.
How
On Mon, 12 Nov 2007 19:42:31 -0800 (PST)
Christoph Lameter [EMAIL PROTECTED] wrote:
x86_64: Make sparsemem/vmemmap the default memory model
Use sparsemem as the only memory model for UP, SMP and NUMA.
Measurements indicate that DISCONTIGMEM has a higher overhead
than sparsemem. And FLATMEMs
On Thu, 15 Nov 2007, Jeremy Fitzhardinge wrote:
Once difference is that 64-bit incrementally allocates all levels of the
pagetable, whereas 32-bit PAE preallocates the 4 pmds when it allocates
the pgd. What's the rationale for this? What pitfalls would there be
in making them
Morrison, Tom wrote:
The plot thickens - it looks like it might be some type
of problem interacting with the setup of my 4Gig DDR memory
and how I setup some translation windows in my MPC8548E
I realized this morning that I have an inbound/ output PEX window
Translation Setup for mapping all
Subject: [PATCH] x86: clean up nmi_32/64.c
clean up and make nmi_32/64.c more similar.
- white space and coding style clean up.
- nmi_cpu_busy is available on CONFIG_SMP.
- move functions __acpi_nmi_enable, acpi_nmi_enable,
__acpi_nmi_disable and acpi_nmi_disable.
- make variables name more
On Thu, 2007-11-15 at 16:51 -0500, Mathieu Desnoyers wrote:
* Dave Hansen ([EMAIL PROTECTED]) wrote:
On Tue, 2007-11-13 at 14:33 -0500, Mathieu Desnoyers wrote:
linux-2.6-lttng/mm/page_io.c2007-11-13 09:49:35.0 -0500
@@ -114,6 +114,7 @@ int swap_writepage(struct page
On Thu, 15 Nov 2007, David P. Reed wrote:
There are a couple of things I don't understand on this one. And I presume
you thought the other two bug fixing patches I sent before this were OK to go,
since on my system
I had to fix up all of them.
Thomas Gleixner wrote:
Still whitespace
Hello,
Fails to build here:
LD .tmp_vmlinux1
drivers/built-in.o: In function `acpi_timer_check_state':
/home/sp3fxc/linux/linux-2.6.24-rc2-mm1/drivers/acpi/processor_idle.c:305:
undefined reference to `local_apic_timer_c2_ok'
make: *** [.tmp_vmlinux1] Error 1
Regards,
On Thu, 15 Nov 2007, Chris Friesen wrote:
We've got some 32-bit 8GB boxes for which both of these would hold true.
Still not enough of a reason for me to care.
Remember - I'm the guy who refused to merge RH's 4G:4G patches because I
thought they were an unsupportable nightmare.
I care a
On Thu, 15 Nov 2007, Zach Brown wrote:
I think we can use this to pass per-syscall syslet data to the
scheduler.
Yes, I mentioned this to Ulrich as one of the things that would make
sense.
Uli doesn't care that much about async syscalls, but I think that from a
kernel standpoint, we'd
Hello,
Another parenthesis fix.
Regards,
Mariusz
Signed-off-by: Mariusz Kozlowski [EMAIL PROTECTED]
include/asm-parisc/pgalloc.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.24-rc2-mm1-a/include/asm-parisc/pgalloc.h 2007-11-15
11:36:44.0
On 2.6.23 it could happen even without loopback
Let's focus on this point, because we already know how the lockup
happens _with_ loopback and any other kind of bdi stacking.
Can you describe the setup? Or better still, can you reproduce it and
post the sysrq-t output?
Hi
The trace is
Hi!
Plus I guess it would be nice to add CPU HOTPLUG into MAINTAINERS
file:
There is a list of maintainers in the Documentation/cpu-hotplug.txt,
which includes maintainers for different platforms as well.
It's a good idea to add that info to the MAINTAINERS file as well.
On Tue, 13 Nov 2007 16:53:16 +
David Howells [EMAIL PROTECTED] wrote:
From: David Howells [EMAIL PROTECTED]
Fix the extern declaration of kallsyms_num_syms to indicate that the symbol
does not reside in the small-data storage space, and so may not be accessed
relative to the small data
Linus Torvalds wrote:
IIRC, the present bit is ignored in the magic 4-entry PGD. All entries
have to be present.
This is true, although you could point a PGD to an all-zero page if you
really wanted to. You have to re-load CR3 after modifying the top-level
entries.
What earlier CPU's
On Thu, 15 Nov 2007 14:40:07 -0800
Andrew Morton [EMAIL PROTECTED] wrote:
But it all strikes me as a bit fragile and grotty. Perhaps longer-term it
would be better if scripts/kallsyms.c were to also emit a header file which
declares all the things which that program emits the definitions of,
On Thursday 15 November 2007 17:25, Mariusz Kozlowski wrote:
local_apic_timer_c2_ok
hmm, looks like you're missing CONFIG_X86_LOCAL_APIC
so does this go away when you add CONFIG_SMP
or CONFIG_X86_UP_APIC?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
On Tue, 13 Nov 2007 18:30:30 +0100 (CET)
Tilman Schmidt [EMAIL PROTECTED] wrote:
From: Tilman Schmidt [EMAIL PROTECTED]
This patch adds basic suspend/resume support to the bas_gigaset ISDN
driver for the Siemens Gigaset SX255 series of ISDN DECT bases.
Only the USB aspects are handled so
Andrew Morton [EMAIL PROTECTED] wrote:
hm, OK, so it lines up with what scripts/kallsyms.c presently does.
I'm sure there's a way to pass the kallsyms_num_syms value directly by way of
the linker rather than consigning it to a bit of memory.
The immediately obvious way is to declare it to be
On Thu, Nov 15, 2007 at 11:19:50AM -0800, mark gross wrote:
On Wed, Nov 14, 2007 at 12:40:08PM -0800, Andrew Morton wrote:
On Wed, 14 Nov 2007 12:29:59 -0800 mark gross [EMAIL PROTECTED] wrote:
[ 102.366932] ===
[ 108.552031] printk: 31 messages suppressed.
What is left unspecified here is 'how' a child 'with its own profile' is
confined here. Are it is confined to just its own profile, it may that
the complicit process communication may need to be wider specified to
include this.
Sorry have to bring this up. cgroups why not? Assign
From: Divy Le Ray [EMAIL PROTECTED]
Date: Thu, 15 Nov 2007 03:38:57 -0800
From: Divy Le Ray [EMAIL PROTECTED]
eth_type_trans() now sets skb-dev.
Access skb-def after it gets set.
Signed-off-by: Divy Le Ray [EMAIL PROTECTED]
Patch applied, thanks.
-
To unsubscribe from this list: send
On Thu, 2007-11-15 at 20:30 +0530, Abhishek Sagar wrote:
On Nov 15, 2007 4:21 AM, Jim Keniston [EMAIL PROTECTED] wrote:
2. Simplify the task of correlating data (e.g., timestamps) between
function entry and function return.
Would adding of data and len fields in ri help? Instead of
On Thu, Nov 15, 2007 at 11:19:50AM -0800, mark gross wrote:
On Wed, Nov 14, 2007 at 12:40:08PM -0800, Andrew Morton wrote:
On Wed, 14 Nov 2007 12:29:59 -0800 mark gross [EMAIL PROTECTED] wrote:
[ 102.366932] ===
[ 108.552031] printk: 31 messages suppressed.
The normal situation on the memory is side is that most of the memory is
in use, but some pages are ready to be discarded, they're just kept
around because we have nothing better to do (yet) with that page.
Is there a tool to do something similar with file systems. I have a lot
of unimportant
That's my personal opinion, and I realize that some of the commercial
vendors may care about their insane customers' satisfaction, but I'm
simply not interested in insane users. If they have that much RAM (and
bought it a few years ago when a 64-bit CPU wasn't an option), they can't
be poor.
On Thu, 15 Nov 2007, Christian Kujau wrote:
Upon accessing the /data/sub part of the CIFS share, the client hung, waiting
for the server to respond (the [cifs] kernel thread on the client was
spinning, waiting for i/o). On the server, similar things as with the nfsd
processes happened
Turns
Ulrich Drepper wrote:
The following patches provide an alternative implementation of the
sys_indirect system call which has been discussed a few times.
This no system call allows us to extend existing system call
interfaces with adding more system calls.
I might quarrel with some details, but
Ingo Molnar wrote:
* Ingo Molnar [EMAIL PROTECTED] wrote:
pick up the latest latency tracer patch from:
sorry, wrong URLs, the correct links are:
http://redhat.com/~mingo/latency-tracing-patches/latency-tracer-v2.6.24-rc2-git5-combo.patch
2007年11月12日 16:23, Thomas Renninger wrote/a écrit:
On Mon, 2007-11-12 at 15:02 +0100, Eric Piel wrote:
:
Another way would be to
reorganise the initialisation code so that workqueue is initialised
before the cpufreq framework is started, do you think it's possible?
Making all this work with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Linus Torvalds wrote:
Uli doesn't care that much about async syscalls,
At the moment I just care a lot more about getting the API straightened
out. An asynchronous incomplete/unsafe API is still an
incomplete/unsafe API.
BTW, I've botched the
From: Christoph Lameter [EMAIL PROTECTED]
Date: Thu, 15 Nov 2007 10:49:37 -0800 (PST)
Well there is an LWN article now that also claims that the cpu_alloc
patchset requires a large bss space. Sigh. See
http://lwn.net/Articles/257828/
Not true! 44 bytes is reasonable.
Well, the first
No, the patch doesn't fix the problem.
I still have the black screen with the cursor when I close the
xsession, only the windowmanager is closed.
consolemessage:
xinit: Operation not permitted (errno 1): Can't kill X server
kernel has capabilities, xinit has no caps granted.
Chris
I'm setting
john cooper wrote:
The more daunting problem stems from limitations in the MIPS
ABI which makes the latency trace support problematic.
Rather than rehash the issue:
http://lists.linuxcoding.com/kernel/2005-q4/msg10163.html
Until we have a usable instrumentation solution in place,
This patch uses _trace_mark in lockdep.c and printk.c. I assume they should be
trace_mark (no '_' prefix).
Mike Mason
Mathieu Desnoyers wrote:
Core kernel events.
*not* present in this patch because they are architecture specific :
- syscall entry/exit
- traps
- kernel thread creation
Hello,
local_apic_timer_c2_ok
hmm, looks like you're missing CONFIG_X86_LOCAL_APIC
so does this go away when you add CONFIG_SMP
or CONFIG_X86_UP_APIC?
Yes it does. In both cases.
Regards,
Mariusz
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On Thu, Nov 15, 2007 at 10:36:13AM -0700, Alex Chiang wrote:
snip
Ok, so all that said, after re-implementing my ACPI-PCI slot
driver, we get all the correct answers, but with the additional
appearance of slots 1 and 2 (which aren't hotpluggable):
Yea, looks much better. Nice to see that
You have been awarded the sum of 250,000.00GBP by the
thunderballpromotions. contact this email.
[EMAIL PROTECTED]
phone:+447045708596
Thank you
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
BTW, I've botched the x86-on-x86_64 support. I have a patch but need to
patch it before I'll submit v3 of the patch set. If you want to work on
the patch and get syslet support going, let me know, I'll send the
latest version.
I probably won't come around to trying sys_indirect with
From: Jonas Danielsson [EMAIL PROTECTED]
Date: Thu, 15 Nov 2007 22:40:13 +0100
Is there a reason that the target hardware address isn't the target
hardware address?
Linux subscribes to the host based addressing model rather
than an interface based addressing model. Both approaches
are valid
The changelog for commit d6dd61c831226f9cd7750885da04d360d6455101 says
arch_dup_mmap, which is called when a new mmap is created at fork
Is there a reason that you're not tracking mm creation in exec?
Jeff
-
To unsubscribe from this list: send the line
Am 15.11.2007 23:50 schrieb Andrew Morton:
...
+if (atomic_read(cs-hw.bas-basstate) BS_SUSPEND) {
that's pretty peculiar. We'd only expect to see atomics being used in
conjunction with atomic_add/sub/inc/etc. Here the driver is using an
atomic_t as a state variable. And here's the
snip
+void list_modules(void *call_data)
+{
+/* Enumerate loaded modules */
+struct list_head*i;
+struct module*mod;
+unsigned long refcount = 0;
+
+mutex_lock(module_mutex);
+list_for_each(i, modules) {
+mod = list_entry(i, struct module, list);
On Thu, Nov 15, 2007 at 01:50:43PM +1100, Neil Brown wrote:
Virtual Folders.
I use VM mode in EMACS, but I believe some other mail readers have the
same functionality.
I have a virtual folder called nfs which shows me all mail in my
inbox which has the string 'nfs' or 'lockd' in a To, Cc,
On Wed, 14 Nov 2007 14:20:49 -0500
Jeff Dike [EMAIL PROTECTED] wrote:
This patch removes a variable which was not used in two functions.
Yet another code cleanup, nothing really significant.
Please note that I could not test this on x86_64. I don't have the
hardware for it.
[ jdike -
Jeff Dike wrote:
The changelog for commit d6dd61c831226f9cd7750885da04d360d6455101 says
arch_dup_mmap, which is called when a new mmap is created at fork
Is there a reason that you're not tracking mm creation in exec?
activate_mm() does that.
J
-
To unsubscribe from this list: send
On Thu, Nov 15, 2007 at 10:20:47PM +0100, Jan Kiszka wrote:
Chuck Ebbert wrote:
On 11/15/2007 12:58 PM, Greg KH wrote:
On Thu, Nov 15, 2007 at 11:11:59AM -0500, Chuck Ebbert wrote:
On 11/15/2007 01:09 AM, Greg KH wrote:
-stable review patch. If anyone has any objections, please let us
In the case of PCI (am no big expert on this)- I believe the code
allows you to address 32 bits at a time...you can see the the
effectve address resource address is some where around
0xea90 - but, if you have PHYS_64BIT PTE_64BIT -
you get resource_types of 64bits...that you can
On 11/14/2007 10:48 PM, Rafael J. Wysocki wrote:
On Wednesday, 14 of November 2007, Jiri Slaby wrote:
On 11/14/2007 02:59 AM, Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc2/2.6.24-rc2-mm1/
Doesn't suspend for me (neither
Vaidyanathan Srinivasan writes:
This patch fixed the problem. I am able to run and profile ebizzy on 128-way
PPC64. However this fix is not included in 2.6.24-rc2 as well.
I will watch for inclusion of this fix in 2.6.24.
It's upstream in Linus' tree now, so it will be in -rc3.
Paul.
-
To
On Thu, Nov 15, 2007 at 12:47:32PM -0800, Andrew Morton wrote:
On Thu, 15 Nov 2007 11:25:37 -0800
Greg KH [EMAIL PROTECTED] wrote:
I'll roll it into my larger patchset so that Andrew can get it
automatically for the next release.
hm, thanks.
Did we hunt down that warning I found?
On Thu, 15 Nov 2007 19:35:44 +0900
KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote:
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
-
On Thu, 15 Nov 2007 20:28:29 -0400
Kevin Winchester [EMAIL PROTECTED] wrote:
On November 15, 2007 06:02:09 am Andy Whitcroft wrote:
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
Linus Torvalds wrote:
IIRC, the present bit is ignored in the magic 4-entry PGD. All entries
have to be present.
On Thu, Nov 15, 2007 at 02:42:46PM -0800, H. Peter Anvin wrote:
This is true, although you could point a PGD to an all-zero page if you
really wanted to. You have to re-load
On Nov 16, 2007 3:23 AM, Greg KH [EMAIL PROTECTED] wrote:
On Wed, Nov 14, 2007 at 10:19:48AM -0800, Greg KH wrote:
On Wed, Nov 14, 2007 at 06:02:07PM +0100, Jiri Kosina wrote:
On Wed, 14 Nov 2007, Jiri Kosina wrote:
I'd suspect the driver tree. I think I'll need to do a quick -mm2
On November 15, 2007 06:02:09 am Andy Whitcroft wrote:
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
On Nov 15, 2007 5:24 PM, Stefan Monnier [EMAIL PROTECTED] wrote:
[ I realize this is probably better implemented outside of the kernel, but
it seems like it might be of interest here. Please redirect me to
a more appropriate place if you can think of one (other than
/dev/null that is).
On Thu, Nov 15, 2007 at 08:51:36AM +0100, Christian Kujau wrote:
[c040914c] mutex_lock_nested+0xcc/0x2c0
[c016dc64] do_lookup+0xa4/0x190
[c016f6f9] __link_path_walk+0x749/0xd10
[c016fd04] link_path_walk+0x44/0xc0
[c016fd98] path_walk+0x18/0x20
[c016ff98] do_path_lookup+0x78/0x1c0
On 13/11/2007, Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:
Jesper Juhl wrote:
In kernel/exit.c we have this code :
static void exit_mm(struct task_struct * tsk)
{
struct mm_struct *mm = tsk-mm;
mm_release(tsk, mm);
if (!mm)
return;
...
On Thu, Nov 15, 2007 at 03:31:22PM +0800, Herbert Xu wrote:
On Wed, Nov 14, 2007 at 11:00:39PM -0800, David Miller wrote:
I was just about to mention this and what I think we should do
instead is keep the SKB_WITH_OVERHEAD calculation fix in there
(it fixes a serious bug which users are
William Lee Irwin III wrote:
There may be bigger fish to fry in terms of per-process overhead, if
you're trying to cut that down. The trouble with trying to address
some of those is that there is mutual antagonism between compactness
and expansibility in the process address space layout, so
On Fri, Nov 16, 2007 at 12:59:41AM +0100, Jiri Slaby wrote:
On 11/14/2007 10:48 PM, Rafael J. Wysocki wrote:
On Wednesday, 14 of November 2007, Jiri Slaby wrote:
On 11/14/2007 02:59 AM, Andrew Morton wrote:
So the _only_ explanation today for 12GB on a 32-bit machine is
(a) insanity
or
(b) being so lazy as to not bother to upgrade
and in either case, my personal reaction is I'm *not* crazy, and yes, I'm
lazy too, and I can't give a rats *ss about those problems.
12GB-16GB worked well
Stefan Monnier wrote:
So I'd like to be able to say these areas of my file-system hold data
that you can discard whenever you need space. So I can freely fill up
my disk with such irrelevant data, safe in the knowledge that if I ever
need this disk space it'll be automatically reclaimed.
On Fri, Nov 16, 2007 at 08:39:12AM +0800, Dave Young wrote:
On Nov 16, 2007 3:23 AM, Greg KH [EMAIL PROTECTED] wrote:
On Wed, Nov 14, 2007 at 10:19:48AM -0800, Greg KH wrote:
On Wed, Nov 14, 2007 at 06:02:07PM +0100, Jiri Kosina wrote:
On Wed, 14 Nov 2007, Jiri Kosina wrote:
On Nov 16, 2007 8:49 AM, Greg KH [EMAIL PROTECTED] wrote:
On Fri, Nov 16, 2007 at 08:39:12AM +0800, Dave Young wrote:
On Nov 16, 2007 3:23 AM, Greg KH [EMAIL PROTECTED] wrote:
On Wed, Nov 14, 2007 at 10:19:48AM -0800, Greg KH wrote:
On Wed, Nov 14, 2007 at 06:02:07PM +0100, Jiri
Hi,
On Thu, 15 Nov 2007, Sam Ravnborg wrote:
You suggest just to check ARCH value and not apply your patch. This was
not my initial understanding as was hopefully obvious from my reply.
This patch only adds some extra features.
If user did NOT specify ARCH we should use the kernel
On Thu, 15 Nov 2007, Tim Bird wrote:
john cooper wrote:
The more daunting problem stems from limitations in the MIPS
ABI which makes the latency trace support problematic.
Rather than rehash the issue:
http://lists.linuxcoding.com/kernel/2005-q4/msg10163.html
Until we have a
701 - 800 of 890 matches
Mail list logo