* Roman Zippel <[EMAIL PROTECTED]> wrote:
> > 4544 roman 20 0 1796 520 432 S 32.1 0.4 0:21.08 lt
> > 4545 roman 20 0 1796 344 256 R 32.1 0.3 0:21.07 lt
> > 4546 roman 20 0 1796 344 256 R 31.7 0.3 0:21.07 lt
> > 4547 roman 20 0 1532 272 216 R 3.3
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc2/2.6.23-rc2-mm2/
- Various problems from 2.6.23-rc2-mm1 were fixed
Boilerplate:
- See the `hot-fixes' directory for any important updates to this patchset.
- To fetch an -mm tree using git, use (for example)
> >> > This is needed to be able to correctly implement open-unlink-fsetattr
> >> > semantics in some filesystem such as sshfs, without having to resort
> >> > to "silly-renaming".
> >>
> >> How do you plan to do that?
> >
> > Easy: the SFTP protocol has stateful opens and defines an FSTAT call.
Dear Auke
Sorry I sent the wrong patch.
I resubmit the patch.
Tomohiro Kusumi
Signed-off-by: Tomohiro Kusumi <[EMAIL PROTECTED]>
---
diff -Nurp linux-2.6.22.org/drivers/net/e1000/e1000.h
linux-2.6.22/drivers/net/e1000/e1000.h
--- linux-2.6.22.org/drivers/net/e1000/e1000.h 2007-07-09
Andrew Morton wrote:
> On Fri, 10 Aug 2007 01:23:07 +0200
> Mariusz Kozlowski <[EMAIL PROTECTED]> wrote:
>
>> Hello,
>>
>> This probably doesn't have great impact ;) but ...
>> To reproduce: run torture tests for RCU and then sysrq+q.
>>
>> SysRq : Show Pending Timers
>> Timer List Version:
The following changes are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/christoph/slab.git to-linus
Christoph Lameter (2):
SLUB: Remove checks for MAX_PARTIAL from kmem_cache_shrink
SLUB: Fix dynamic dma kmalloc cache creation
Jesper Juhl (1):
Dear Auke
http://lkml.org/lkml/2007/5/16/275
> I'm ok with the bottom part of the patch, but I do not like the modification
> of
> the pci device ID table in this way. As Arjan van der Ven previously commented
> as well, this makes it hard for future device ID's to be bound to the driver.
>
> On
if one thread set its current->flag with PF_NOFREEZE, then it means
this thread is unfreezable,does this mean, when the system entered
into a suspended state, even though all the other threads have already
gone sleep, this thread still keeps awaken?
One thing I am very confused is, if all the
On 8/9/07, Andi Kleen <[EMAIL PROTECTED]> wrote:
>
> Hallo,
>
> I thought a bit about the zero page problem. I really would prefer to not
> having it used in a boot loader right now because it's not extensible anymore
> when external users start (ab)using it.
>
> When I asked for separate
On Friday August 10, [EMAIL PROTECTED] wrote:
> On 8/1/07, Neil Brown <[EMAIL PROTECTED]> wrote:
>
> > No, this does not use indefinite stack.
> >
> > loop will schedule each request to be handled by a kernel thread, so
> > requests to 'loop' are serialised, never stacked.
> >
> > In 2.6.22,
On 8/1/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> No, this does not use indefinite stack.
>
> loop will schedule each request to be handled by a kernel thread, so
> requests to 'loop' are serialised, never stacked.
>
> In 2.6.22, generic_make_request detects and serialises recursive calls,
> so
KAMEZAWA Hiroyuki wrote:
> On Wed, 8 Aug 2007 12:51:39 +0900
> KAMEZAWA Hiroyuki <[EMAIL PROTECTED]> wrote:
>
>> On Sat, 28 Jul 2007 01:39:37 +0530
>> Balbir Singh <[EMAIL PROTECTED]> wrote:
>>> At OLS, the resource management BOF, it was discussed that we need to manage
>>> RSS and unmapped
Greg KH wrote:
On Tue, Aug 07, 2007 at 10:26:15PM +0200, Niels wrote:
Hi,
I'm having problems with a new 500 GB USB disk. It works, but sometimes I
get these in dmesg:
usb 1-3: reset high speed USB device using ehci_hcd and address 2
usb 5-1: USB disconnect, address 2
H. Peter Anvin wrote:
Jan Engelhardt wrote:
Hi,
with the old rtc.ko module, there was a /proc/sys/dev/rtc/max-user-freq
that could be set. With rtc_cmos.ko (or the new rtc infrastructure in
general), I am missing this file. Where can I set the max-user-freq now,
or is this obsolete now?
Hi,
I'm kind of lost in my debugging. Hope someone out there can help me
figure out the problem.
I am loading 4 modules-> class driver, device controller, interface
layer(working on a dual-core) abstraction layer.
Device has to work as a mass storage class. After doing some file
transfer and
Andi Kleen wrote:
richard kennedy <[EMAIL PROTECTED]> writes:
This is on a standard desktop machine so there are lots of other
processes running on it, and although there is a degree of variability
in the numbers,they are very repeatable and your patch always out
performs the stock mm2.
looks
Hi, I get the following error when doing an 'rsync -avz --progress.' Any
help would be appreciated.
Unable to handle kernel NULL pointer dereference at RIP:
[] __rmqueue+0x6c/0x140
PGD 7b24f067 PUD 71ab9067 PMD 0
Oops: [1] SMP
CPU 1
Modules linked in: rfcomm snd_seq
[EMAIL PROTECTED] wrote:
On Sun, 5 Aug 2007, Diego Calleja wrote:
El Sun, 5 Aug 2007 09:13:20 +0200, Ingo Molnar <[EMAIL PROTECTED]> escribió:
Measurements show that noatime helps 20-30% on regular desktop
workloads, easily 50% for kernel builds and much more than that (in
excess of 100%)
On Mon, 2007-08-06 at 18:15 +0200, Ingo Molnar wrote:
> randconfig testing on .23-rc2 triggered the following build error:
When building NOR flash support, you have compile-time options for the
bus width and the number of individual chips which are interleaved
together onto that bus. The code to
On Thu, 9 Aug 2007, Daniel Phillips wrote:
> If you believe that the deadlock problems we address here can be
> better fixed by making reclaim more intelligent then please post a
> patch and we will test it. I am highly skeptical, but the proof is in
> the patch.
Then please test the patch that
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
I have a python script to convert 00-INDEX files into index.html files, and a
second script to show 404 errors in the result as well as files/directories
nothing links to. (It's not very useful yet, but in case you're wondering
Hi guys,
I'm trying to lock some piece of the code in memory using mlock(). I did
a simple program to test it and to certify I using my own simple page
fault notifier [0]. The program is below.
-- cut --
#include
#include
#define SIZE 1
int mlock_all = 0;
int
f(void)
{
int
On 8/9/07, Christoph Lameter <[EMAIL PROTECTED]> wrote:
> The allocations problems that this patch addresses can be fixed by making
> reclaim
> more intelligent.
If you believe that the deadlock problems we address here can be
better fixed by making reclaim more intelligent then please post a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Once ext4 will not implement fragment, it is believed it will never be implement
in future. Therefore fragment related source code in ext4 should be obsoleted --
no one will use it.
This patch obsolete fragment from ext4.
Another patch posted on
In message <[EMAIL PROTECTED]>, Adrian Bunk writes:
> On Thu, Aug 09, 2007 at 10:38:18PM -0400, Erez Zadok wrote:
> > I'm getting an error modprobing jffs2 due to mtdsuper failing to insmod:
> >...
> > Does anyone know what am I missing?
>
> You miss that 2.6.23-rc2 with this bug fixed has
On Thu, Aug 09, 2007 at 10:38:18PM -0400, Erez Zadok wrote:
> I'm getting an error modprobing jffs2 due to mtdsuper failing to insmod:
>...
> Does anyone know what am I missing?
You miss that 2.6.23-rc2 with this bug fixed has already been released.
> Thanks,
> Erez.
cu
Adrian
--
"Is
I'm getting an error modprobing jffs2 due to mtdsuper failing to insmod:
# modprobe jffs2
WARNING: Error inserting mtdsuper
(/lib/modules/2.6.23-rc1/kernel/drivers/mtd/mtdsuper.ko):
Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting jffs2
YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
> Hello.
>
> In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007
> 14:09:29 -0600), [EMAIL PROTECTED] (Eric W. Biederman) says:
>
>> After going through the kernels sysctl tables several times it has
>> become clear that code review and testing
YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
> In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007
> 20:23:16 -0600), [EMAIL PROTECTED] (Eric W. Biederman) says:
>
>> YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
>>
>> > Would you explain why it does not work properly
>> > for
YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
> Hello.
>
> In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007
> 14:09:29 -0600), [EMAIL PROTECTED] (Eric W. Biederman) says:
>
>> After going through the kernels sysctl tables several times it has
>> become clear that code review and testing
In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007 20:23:16 -0600), [EMAIL
PROTECTED] (Eric W. Biederman) says:
> YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
>
> > Would you explain why it does not work properly
> > for those cases?
>
> Mostly no appropriate strategy routine was
YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]> writes:
> Would you explain why it does not work properly
> for those cases?
Mostly no appropriate strategy routine was setup to
report the data to the caller of sys_sysctl.
Eric
-
To unsubscribe from this list: send the line "unsubscribe
On Thu, Aug 09, 2007 at 07:00:40PM -0700, Paul E. McKenney wrote:
> On Fri, Aug 10, 2007 at 03:31:46AM +0200, Adrian Bunk wrote:
> > On Thu, Aug 09, 2007 at 01:51:06AM -0700, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.23-rc2-mm1:
> > >...
> > >
In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007 18:56:09 -0600), [EMAIL
PROTECTED] (Eric W. Biederman) says:
>
> - In ipv6 ndisc_ifinfo_syctl_change so it doesn't depend on binary
> sysctl names for a function that works with proc.
:
Well, retrans_time_ms and base_reachable_time_ms
Andrew Morton <[EMAIL PROTECTED]> writes:
> But it is good to remove bad interfaces, if we possibly can.
>
> It is worth making the attempt. Does anyone know of anything which will
> break? I fed NET_NEIGH_ANYCAST_DELAY at random into
> http://www.google.com/codesearch and came up with
In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007 18:49:21 -0700 (PDT)),
David Miller <[EMAIL PROTECTED]> says:
> From: YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]>
> Date: Fri, 10 Aug 2007 10:47:10 +0900 (JST)
>
> > I disagree. It is bad to remove existing interface.
> > Ditto for other
On Thu, 09 Aug 2007 18:58:09 -0700 Josh Triplett <[EMAIL PROTECTED]> wrote:
> - * We can use khz divisor instead of mhz to keep a better percision, since
> + * We can use khz divisor instead of mhz to keep a better precision, since
I have an arbitrary i-dont-do-typos policy (unless they're in
On Thu, 9 Aug 2007 19:00:40 -0700 "Paul E. McKenney" <[EMAIL PROTECTED]> wrote:
> On Fri, Aug 10, 2007 at 03:31:46AM +0200, Adrian Bunk wrote:
> > On Thu, Aug 09, 2007 at 01:51:06AM -0700, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.23-rc2-mm1:
> > >...
> > >
On Thu, 9 Aug 2007, Daniel Phillips wrote:
> No matter how you look at this problem, you still need to have _some_
> sort of reserve, and limit access to it. We extend existing methods,
The reserve is in the memory in the zone and reclaim can guarantee that
there are a sufficient number of
On Fri, Aug 10, 2007 at 03:31:46AM +0200, Adrian Bunk wrote:
> On Thu, Aug 09, 2007 at 01:51:06AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.23-rc2-mm1:
> >...
> > +allow-rcutorture-to-handle-synchronize_sched.patch
> >...
> > 2.6.23 queue
> >...
>
> All drivers were converted to
Hello.
In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007 14:09:29 -0600), [EMAIL
PROTECTED] (Eric W. Biederman) says:
> After going through the kernels sysctl tables several times it has
> become clear that code review and testing is just not effective in
> prevent problematic sysctl tables
Signed-off-by: Josh Triplett <[EMAIL PROTECTED]>
---
arch/i386/kernel/tsc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/i386/kernel/tsc.c b/arch/i386/kernel/tsc.c
index debd7db..8a58d30 100644
--- a/arch/i386/kernel/tsc.c
+++ b/arch/i386/kernel/tsc.c
@@ -80,7
On Fri, 10 Aug 2007 10:47:10 +0900 (JST) YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL
PROTECTED]> wrote:
> Hello.
>
> In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007 18:56:09 -0600), [EMAIL
> PROTECTED] (Eric W. Biederman) says:
>
> >
> > - In ipv6 ndisc_ifinfo_syctl_change so it doesn't depend on
On 8/8/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> On Wed, 8 Aug 2007 10:57:13 -0700 (PDT)
> Christoph Lameter <[EMAIL PROTECTED]> wrote:
>
> > I think in general irq context reclaim is doable. Cannot see obvious
> > issues on a first superficial pass through rmap.c. The irq holdoff would
> >
From: YOSHIFUJI Hideaki / 吉藤英明 <[EMAIL PROTECTED]>
Date: Fri, 10 Aug 2007 10:47:10 +0900 (JST)
> I disagree. It is bad to remove existing interface.
> Ditto for other patches.
I think perhaps you misunderstand what Eric is doing.
sys_sysctl() isn't working properly for these cases and it is
On Thu, 9 Aug 2007, Daniel Phillips wrote:
> You can fix reclaim as much as you want and the basic deadlock will
> still not go away. When you finally do get to writing something out,
> memory consumers in the writeout path are going to cause problems,
> which this patch set fixes.
We currently
Zachary Amsden wrote:
Avi Kivity wrote:
We haven't seen any issue with the 2.6.22 boot decompressor. Which
of the four (fs, gs, ldt, or tr) were proving problematic and why?
It was tr that was affecting Workstation, since we boot through normal
BIOS path, and only a 16-bit task was loaded
Hello.
In article <[EMAIL PROTECTED]> (at Thu, 09 Aug 2007 18:56:09 -0600), [EMAIL
PROTECTED] (Eric W. Biederman) says:
>
> - In ipv6 ndisc_ifinfo_syctl_change so it doesn't depend on binary
> sysctl names for a function that works with proc.
>
> - In neighbour.c reorder the table to put
On Fri, 10 Aug 2007, Mel Gorman wrote:
> > > +#if defined(CONFIG_SMP) && INTERNODE_CACHE_SHIFT > ZONES_SHIFT
> >
> > Is this necessary? ZONES_SHIFT is always <= 2 so it will work with
> > any pointer. Why disable this for UP?
> >
>
> Caution in case the number of zones increases. There was
On Thu, Aug 09, 2007 at 01:51:06AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.23-rc2-mm1:
>...
> +allow-rcutorture-to-handle-synchronize_sched.patch
>...
> 2.6.23 queue
>...
All drivers were converted to no longer use xtime directly since it
might be quite outdated, but this patch
On Thu, Aug 09, 2007 at 03:24:40PM -0400, Chris Snook wrote:
> Paul E. McKenney wrote:
> >On Thu, Aug 09, 2007 at 02:13:52PM -0400, Chris Snook wrote:
> >>Paul E. McKenney wrote:
> >>>On Thu, Aug 09, 2007 at 01:14:35PM -0400, Chris Snook wrote:
> If you're
This patch provides cross partition access to user memory (XPMEM) when
running multiple partitions on a single SGI Altix.
Signed-off-by: Dean Nelson <[EMAIL PROTECTED]>
xpmem-module.v002.bz2
Description: BZip2 compressed data
This patch exports zap_page_range as it is needed by XPMEM.
Signed-off-by: Dean Nelson <[EMAIL PROTECTED]>
---
XPMEM would have used sys_madvise() except that madvise_dontneed()
madvise_dontneed() returns an -EINVAL if VM_PFNMAP is set, which is
always true for the pages XPMEM imports from
This patch exports __put_task_struct as it is needed by XPMEM.
Signed-off-by: Dean Nelson <[EMAIL PROTECTED]>
---
One struct file_operations registered by XPMEM, xpmem_open(), calls
'get_task_struct(current->group_leader)' and another, xpmem_flush(), calls
'put_task_struct(tg->group_leader)'.
Terminology
The term 'partition', adopted by the SGI hardware designers and which
perculated up into the software, is used in reference to a single SSI
when multiple SSIs are running on a single Altix. An Altix running
multiple SSIs is said to be 'partitioned', whereas one that is running
This is debug code so no need to support binary sysctl,
and the binary sysctls as they were written were not
consistent with what showed up in /proc so remove
the binary sysctl support.
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
net/sunrpc/sysctl.c |4
1 files changed, 0
On 8/1/07, Alan Cox <[EMAIL PROTECTED]> wrote:
> On Wed, 1 Aug 2007 15:33:58 +0200
> Andrea Arcangeli <[EMAIL PROTECTED]> wrote:
> > Tweaking kernel ptes is prohibitive during clone() because that's
> > kernel memory and it would require a flush tlb all with IPIs that
> > won't scale (IPIs are
aio-nr, aio-max-nr, acpi_video_flags are unsigned long values
which sysctl does not handle properly with a 64bit kernel
and a 32bit user space.
Since no one is likely to be using the binary sysctl values
and the ascii interface still works, this patch just removes
support for the binary sysctl
Currently tcp_available_congestion_control does not even
attempt being read from sys_sysctl, and ipfrag_max_dist
while it works allows setting of invalid values using
sys_sysctl.
So just kill the binary sys_sysctl support for these
sysctls. If the support is not important enough to
test and get
The binary interface for the cdrom sysctls can't possilby work.
So remove the binary sysctls and update the test for finding
out which sysctl table entry we are dealy with to use the procname
and not the ctl_name (which I am removing).
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
arch/x86_64/ia32/ia32_binfmt.c |1 -
arch/x86_64/kernel/vsyscall.c | 10 +-
2 files changed, 1 insertions(+), 10 deletions(-)
diff --git a/arch/x86_64/ia32/ia32_binfmt.c b/arch/x86_64/ia32/ia32_binfmt.c
index
>From ddf280c9de903f1fb5d4ecf9c68df0c479d7c7d2 Mon Sep 17 00:00:00 2001
From: Eric W. Biederman <[EMAIL PROTECTED]>
Date: Thu, 9 Aug 2007 16:00:00 -0600
Subject:
This is debug code so no need to support binary sysctl,
and the binary sysctls as they were written were not
consistent with what
We don't preoperly support the sysctl binary path for flushing
the ipv6 routes. So remove support for a binary path.
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
net/ipv6/route.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/net/ipv6/route.c
- In ipv6 ndisc_ifinfo_syctl_change so it doesn't depend on binary
sysctl names for a function that works with proc.
- In neighbour.c reorder the table to put the possibly unused entries
at the end so we can remove them by terminating the table early.
- In neighbour.c kill the entries with
These functions all of wrapper functions for the proc interface
that are needed for them to work correctly.
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
kernel/sysctl.c |7 ---
1 files changed, 0 insertions(+), 7 deletions(-)
diff --git a/kernel/sysctl.c b/kernel/sysctl.c
Because of a conflict with FS_INODE_NR none of the binary
sysctl numbers use by mqueue, were available to user space.
So just remove them.
Signed-off-by: Eric W. Biederman <[EMAIL PROTECTED]>
---
ipc/mqueue.c | 10 --
1 files changed, 0 insertions(+), 10 deletions(-)
diff --git
Well it turns out after I dug into the problems a
little more I was returning a few false positives
so this patch updates my logic to remove them.
- Don't complain about 0 ctl_names in sysctl_check_binary_path
It is valid for someone to remove the sysctl binary interface
and still keep the
On Fri, Aug 03, 2007 at 07:15:31PM -0700, Dan Williams wrote:
> On 7/25/07, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> > On Wed, Jul 25, 2007 at 04:03:04AM -0700, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.22-rc6-mm1:
> > >...
> > > +dma-arch-fix.patch
> > >
> > > Fix git-dma.patch
> >
On 8/9/07, Lucio Correia <[EMAIL PROTECTED]> wrote:
> On Wed, 2007-08-08 at 23:10 +0200, Arnd Bergmann wrote:
> > On Wednesday 08 August 2007, Lucio Correia wrote:
> > > DMA 0 ->12288
> > > Normal 12288 ->12288
> > > early_node_map[2] active PFN ranges
> > > 0:
On Thu, Aug 09, 2007 at 04:37:35PM +0100, Hugh Dickins wrote:
> On Thu, 9 Aug 2007, Mariusz Kozlowski wrote:
> > Hello,
> >
> > Nothing unusual happening, allmodconfig compiling etc.
> > Not sure why it says kernel was tainted though ... hmmm.
> >
> > [ cut here ]
> >
On 8/9/07, Arnd Bergmann <[EMAIL PROTECTED]> wrote:
> On Wednesday 08 August 2007, Lucio Correia wrote:
> > DMA 0 -> 12288
> > Normal 12288 -> 12288
> > early_node_map[2] active PFN ranges
> > 0: 0 -> 2560
> > 1: 12287 -> 12288
>
> As Christoph found, this memory map is really strange. Other
Andrew Morton wrote:
On Wed, 08 Aug 2007 14:10:15 -0700
"Martin J. Bligh" <[EMAIL PROTECTED]> wrote:
Why isn't this easily fixable by just adding an additional dirty
flag that says atime has changed? Then we only cause a write
when we remove the inode from the inode cache, if only atime
is
On 08/10/2007 12:27 AM, Francois Romieu wrote:
Andi Kleen <[EMAIL PROTECTED]> :
[...]
I don't think that is used by Linuxdoc. Try a make pdfdocs and see for
yourself.
It reminds me of an old PII but it does not really make clear how html to
pdf conversion would improve the situation.
On 8/9/07, Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Thu, 9 Aug 2007, Daniel Phillips wrote:
> > On 8/8/07, Christoph Lameter <[EMAIL PROTECTED]> wrote:
> > > On Wed, 8 Aug 2007, Daniel Phillips wrote:
> > > Maybe we need to kill PF_MEMALLOC
> > Shrink_caches needs to be able to
On Fri, 10 Aug 2007 01:23:07 +0200
Mariusz Kozlowski <[EMAIL PROTECTED]> wrote:
> Hello,
>
> This probably doesn't have great impact ;) but ...
> To reproduce: run torture tests for RCU and then sysrq+q.
>
> SysRq : Show Pending Timers
> Timer List Version: v0.3
> HRTIMER_MAX_CLOCK_BASES:
On Fri, Aug 10, 2007 at 01:44:24AM +0200, shacky wrote:
> > You snipped the most important part. Even a digital photo of the
> > crash would be more useful than what we have above.
> > So far, there's not really much to go on.
>
> Could you tell me what is the most important part, so I try
On Aug 8 2007 18:28, Michal Piotrowski wrote:
>
>Hi Brian,
>
>Brian J. Murrell pisze:
>> I am using Ubuntu Gutsy, which is the in-development branch heading for
>> their next stable release.
>
>You forgot about message subject, so no one has read this report.
Actually, given the volume on LKML,
Hello,
=
[ INFO: inconsistent lock state ]
2.6.23-rc2-mm1 #7
-
inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
ifconfig/5492 [HC0[0]:SC0[0]:HE1:SE1] takes:
(>lock){+...}, at: [] rtl8139_interrupt+0x27/0x46b [8139too]
On Friday 10 August 2007, Alan Cox wrote:
> On Thu, 9 Aug 2007 23:19:34 +0200
> Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
>
> >
> > Maximum supported UDMA mode for AEC6280[R] is UDMA5 (not UDMA4)
> > and for AEC6880[R] it is UDMA6 (not UDMA5):
> >
> > * Fix the problem by adding
> You snipped the most important part. Even a digital photo of the
> crash would be more useful than what we have above.
> So far, there's not really much to go on.
Could you tell me what is the most important part, so I try to rewrite
it by hand?
I don't think a digital photo will be much
Avi Kivity wrote:
We haven't seen any issue with the 2.6.22 boot decompressor. Which of
the four (fs, gs, ldt, or tr) were proving problematic and why?
It was tr that was affecting Workstation, since we boot through normal
BIOS path, and only a 16-bit task was loaded at this point.
Just
On Fri, Aug 10, 2007 at 01:17:14AM +0200, shacky wrote:
> [87.935473] BUG: unable to handle kernel paging request at virtual
> address 6d207972
> [...] printing eip:
> [...] 6d207972
> [...] *pde =
> [...] Oops: 000 [#2]
> [...] SMP
>
On Thu, Aug 09, 2007 at 04:20:01PM -0700, Kristen Carlson Accardi wrote:
> On Fri, 10 Aug 2007 01:04:36 +0200
> Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Aug 09, 2007 at 03:47:02PM -0700, Kristen Carlson Accardi wrote:
> > >
> > > fine by me - let's NAK this patch (and all future ones
On 08/09/2007 07:16 PM, Andi Kleen wrote:
>
> I tested it. Even on a box without spin lock debugging I get a hard
> hang after
>
> double fault, gdt at c1404000 [255 bytes]
>
> even though it should have printed the registers.
> So it looks like there is more broken in the DF handler than just
Alan Cox wrote:
>>> [ 28.828484] :00:1f.1: cannot adjust BAR0 (not I/O)
>>> [ 28.828487] :00:1f.1: cannot adjust BAR1 (not I/O)
>>> [ 28.828489] :00:1f.1: cannot adjust BAR2 (not I/O)
>>> [ 28.828491] :00:1f.1: cannot adjust BAR3 (not I/O)
>
> This means it didn't do
On (09/08/07 14:37), Christoph Lameter didst pronounce:
> On Thu, 9 Aug 2007, Mel Gorman wrote:
>
> > }
> >
> > +#if defined(CONFIG_SMP) && INTERNODE_CACHE_SHIFT > ZONES_SHIFT
>
> Is this necessary? ZONES_SHIFT is always <= 2 so it will work with
> any pointer. Why disable this for UP?
>
Hello,
This probably doesn't have great impact ;) but ...
To reproduce: run torture tests for RCU and then sysrq+q.
SysRq : Show Pending Timers
Timer List Version: v0.3
HRTIMER_MAX_CLOCK_BASES: 2
now at 1764338760370 nsecs
cpu: 0
clock 0:
.index: 0
.resolution: 1 nsecs
> Silly is in the eye of the beholder. I don't want to take this patch
> because it needs to be reviewed by someone who really knows the intent
> of the driver. Seems silly to me to blindly take patches.
For unmaintained code we usually work on wackipedia theory ("its probably
right but if not
How about we just remove the RDMA stack altogether? I am not at all
kidding. If you guys can't stay in your sand box and need to cause
problems for the normal network stack, it's unacceptable. We were
told all along the if RDMA went into the tree none of this kind of
stuff would be an issue.
On Fri, 10 Aug 2007 01:04:36 +0200
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 09, 2007 at 03:47:02PM -0700, Kristen Carlson Accardi wrote:
> >
> > fine by me - let's NAK this patch (and all future ones for this driver)
> > until
> > someone with hardware steps up to maintain this
On Fri, 10 Aug 2007 01:04:36 +0200
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> We have tons of unmaintained drivers and none of them has such a silly
> auto-NAK policy.
>
> cu
> Adrian
Silly is in the eye of the beholder. I don't want to take this patch
because it needs to be reviewed by someone
Hi.
I installed Ubuntu 7.04 and then upgraded to the future 7.10 on my
system based on an Asus Pundit barebone with 512 mb RAM and 120 Gb IDE
hard disk.
The system works without any problem, but when I try to shutdown or
restart the system, after a while during the shutdown process, the
system
On Thu, Aug 09, 2007 at 02:40:27PM -0400, Chuck Ebbert wrote:
> On 08/09/2007 01:49 PM, Andi Kleen wrote:
> > Chuck Ebbert <[EMAIL PROTECTED]> writes:
> >> Initializing FS in the doublefault_tss should fix it.
> >>
> >> Signed-off-by: Chuck Ebbert <[EMAIL PROTECTED]>
> >>
> >> ---
> >>
> >> NOTE:
> fine by me - let's NAK this patch (and all future ones for this driver) until
> someone with hardware steps up to maintain this driver. Eventually it
> will just die I guess.
If you want to NAK it perhaps you should become maintainer ;)
Alan
-
To unsubscribe from this list: send the line
Hi,
On Wed, 1 Aug 2007, Ingo Molnar wrote:
> just to make sure, how does 'top' output of the l + "lt 3" testcase look
> like now on your laptop? Yesterday it was this:
>
> 4544 roman 20 0 1796 520 432 S 32.1 0.4 0:21.08 lt
> 4545 roman 20 0 1796 344 256 R 32.1 0.3
On Thu, Aug 09, 2007 at 03:47:02PM -0700, Kristen Carlson Accardi wrote:
>
> fine by me - let's NAK this patch (and all future ones for this driver) until
> someone with hardware steps up to maintain this driver. Eventually it
> will just die I guess.
We have tons of unmaintained drivers and
So, why not use the well-defined alternative?
Because we don't need to, and it hurts performance.
It hurts performance by implementing 32-bit atomic reads in assembler?
No, I misunderstood the question. Implementing 32-bit atomic reads in
assembler is redundant, because any sane compiler,
> > +#if defined(CONFIG_ARCH_AT91RM9200)
> > at91_sys_write(AT91_SDRAMC_SRR, 1); /*
> > self-refresh mode */
> Why don't use:
> if (cpu_is_at91rm9200())
> at91_sys_write(AT91_SDRAMC_SRR, 1);
What is the benefit?
Will the optimizer remove the code if the CPU is not
On Thu, 9 Aug 2007 15:24:27 -0700
Greg KH <[EMAIL PROTECTED]> wrote:
[EMAIL PROTECTED]
> On Thu, Aug 09, 2007 at 02:51:40PM -0700, Kristen Carlson Accardi wrote:
> > On Mon, 23 Jul 2007 16:51:05 +0200
> > Adrian Bunk <[EMAIL PROTECTED]> wrote:
> >
> > > If !mem_node we did already return -ENOMEM
On Thu, 9 Aug 2007 23:19:34 +0200
Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> wrote:
>
> Maximum supported UDMA mode for AEC6280[R] is UDMA5 (not UDMA4)
> and for AEC6880[R] it is UDMA6 (not UDMA5):
>
> * Fix the problem by adding missing struct ata_port_info to artop_init_one().
>
> * Use
1 - 100 of 1142 matches
Mail list logo
