Remove artificial maximum 256 loop device that can be created due to a
legacy device number limit. Searching through lkml archive, there are
several instances where users complained about the artificial limit
that the loop driver impose. There is no reason to have such limit.
This patch rid the
On 3/30/2007, "Guennadi Liakhovetski" <[EMAIL PROTECTED]> wrote:
>On Thu, 29 Mar 2007, Jeff Garzik wrote:
>
>> Guennadi Liakhovetski wrote:
>>> Jeff, might be worth getting the sk_buff leak fix in ppp from
>>> http://www.spinics.net/lists/netdev/msg27706.html in 2.6.21 too?
>>>
>>> Don't know how
On Thu, 2007-03-29 at 21:21 -0700, Jesse Brandeburg wrote:
> added netdev.
>
> On 3/29/07, Andrei Popa <[EMAIL PROTECTED]> wrote:
> > In a dual core 2 server with an intel motherboard and 5 network
> > cards(two onboard) and 1 pci express card with two slots and one pci-x
> > pci64 card the kernel
I just noticed this weird kernel message while looking through
/var/log/ , I have never noticed this error to occur before and below
is the only mention of it I could find in my log files:
netrek:/var/log# grep IRQ7 *
kern.log:Mar 29 23:44:36 netrek kernel: spurious 8259A interrupt: IRQ7.
kernel:
> > Even ARM prefers above kind of layout. For details please see the
> > definition of sys_arm_sync_file_range().
>
> This is a clean-looking option. Can s390 be changed to support seven-arg
> syscalls?
>
> > Option of loff_t => high u32 + low u32
> > --
> >
On Thu, Mar 29, 2007 at 10:10:10AM -0700, Andrew Morton wrote:
> > Platform: s390
> > --
> > s390 prefers following layout:
> >
> >int fallocate(int fd, loff_t offset, loff_t len, int mode)
> >
> > For details on why and how "int, int, loff_t, loff_t" is a problem on
> > s390, ple
On Friday 30 March 2007 05:49:14 Jan Engelhardt wrote:
> On Mar 30 2007 11:37, Conke Hu wrote:
> > Is it possible to use C++ in linux kernel module? how?
> > I've tested but failed, there is an unknown symbol in the .o file from
> > c++ source code.
>
> You answered it yourself. Linux does not have
On Thu, Mar 29, 2007 at 07:01:54PM +0200, Jan Engelhardt wrote:
> Hi,
>
> On Mar 29 2007 17:21, Amit K. Arora wrote:
> >
> >We need to come up with the best possible layout of arguments for the
> >fallocate() system call. Various architectures have different
> >requirements for how the arguments s
> in file mm/slab.c and routine kmem_cache_init() I found there
> is no checking for allocated memory on line:
>
> /* 4) Replace the bootstrap head arrays */
> {
> struct array_cache *ptr;
>
> ptr = kmalloc(sizeof(struct arraycache_init), GFP_KERNEL);
>
>
Dmitry Torokhov wrote:
> On Thursday 29 March 2007 23:06, Li Yu wrote:
>
>> Dmitry Torokhov wrote:
>>
>>> On 3/28/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
>>>
The crucial thing here is that all reports but the ones that the driver
registered to will be processed in a stan
Bill Davidsen wrote:
Starting a VM for Win98SE:
posidon:root> /usr/local/kvm-15/bin/qemu -m 128 -hda Win98SE-2.kvm
exception 13 (0)
rax f000ff53 rbx rcx 005a rdx
000e
rsi 001100c4 rdi 0002a002 rsp 00086650 rbp
0
On Thu, 2007-03-29 at 21:33 -0500, Matt Mackall wrote:
> > unsigned short gs, __gsh;
> > unsigned short ldt, __ldth;
> > unsigned short trace, io_bitmap_base;
> > +} __attribute__((packed));
> > +
> > +struct tss_struct {
> > + struct i386_hw_tss x86_tss;
> > +
> > /*
> >
On 3/30/07, Lee Revell <[EMAIL PROTECTED]> wrote:
On 3/29/07, Aubrey Li <[EMAIL PROTECTED]> wrote:
> When register serial driver as a console, the driver function
>
> my_remove()
> my_shutdown()
>
> seems be never called.
>
> So the driver can't reclaim resource when the command "reboot" is issue
On Wednesday 31 January 2007 06:20, Ivo van Doorn wrote:
> > Hope you will be resubmitting this.
>
> And here is the new version,
> I didn't make the name const as requested
> that field is being passed to the class_device_create
> method which requires a char* argument.
>
> But I have made the f
Input: polled device skeleton
Signed-off-by: Dmitry Torokhov <[EMAIL PROTECTED]>
---
drivers/input/misc/Kconfig | 11 ++
drivers/input/misc/Makefile|1
drivers/input/misc/input-polldev.c | 149 +
include/linux/input-polldev.h | 46
On Thu, Mar 29, 2007 at 11:29:05PM -0400, Bill Nottingham wrote:
> Greg KH ([EMAIL PROTECTED]) said:
> > > If interfaces have to change, so be it. But changing the rules for
> > > using them years after it's implemented and then claiming "you didn't
> > > read the instructions" is pretty lame.
> >
On 3/29/07, Russ Meyerriecks <[EMAIL PROTECTED]> wrote:
Hi all,
I've been hacking on the Linux kernel all semester for my OS:
Internals class. We are given full autonomy in picking our final
programming project and I would love for mine to be /useful/ for the
Linux kernel and not just a theoret
Andrew Morton <[EMAIL PROTECTED]> writes:
>
> config PROC_SYSCTL
> bool "Sysctl support (/proc/sys)" if EMBEDDED
> depends on PROC_FS
> select SYSCTL
> default y
>
> CONFIG_PROC_SYSCTL depends on CONFIG_PROC_FS
> CONFIG_PROC_SYSCTL selects CONFIG_SYSCTL
>
> So I don
On 3/29/07, Aubrey Li <[EMAIL PROTECTED]> wrote:
When register serial driver as a console, the driver function
my_remove()
my_shutdown()
seems be never called.
So the driver can't reclaim resource when the command "reboot" is issued.
Is it intended?
Please post your code for review and some
"Williams, Mitch A" <[EMAIL PROTECTED]> writes:
> Chuck Ebbert wrote:
>>Are you going to post one for 2.6.20 as well? Some people might be
>>interested...
>
> The first time I posted this patch, Greg KH indicated that he thought
> it was too intrusive to add to -stable, especially considering that
"Williams, Mitch A" <[EMAIL PROTECTED]> writes:
> Chuck Ebbert wrote:
>>Are you going to post one for 2.6.20 as well? Some people might be
>>interested...
>
> The first time I posted this patch, Greg KH indicated that he thought
> it was too intrusive to add to -stable, especially considering that
On Tue, Mar 06, 2007 at 17:44:47 +0100, Jan Kara wrote:
> Hello,
>
> the patches attached to six following emails implement some cleanup and
> fixes in the UDF code. The main two fixes are:
> 1) UDF now works correctly for files larger than 1GB.
Hi,
I tried 2.6.20 with your patches and got
On 3/29/07, Nick Piggin <[EMAIL PROTECTED]> wrote:
On Thu, Mar 29, 2007 at 10:06:41PM -0400, Lee Revell wrote:
> Until someone fixes all the places in the kernel where scheduling can
> be held off for tens of milliseconds, CONFIG_PREEMPT will be an
> absolute requirement for many applications lik
On 3/29/07, Elliott Johnson <[EMAIL PROTECTED]> wrote:
>What problem are you trying to solve? IOW, how do you know it's not
>just an artifact of diferent load average calculation between 2.4 and
>2.6?
>
>Are you actually seeing reduced throughput/performance? Or are you
>just looking at load av
On Thursday March 29, [EMAIL PROTECTED] wrote:
>
> >
> > Did you look at "cat /proc/mdstat" ?? What sort of speed was the check
> > running at?
> Around 44MB/s.
>
> I do use the following optimization, perhaps a bad idea if I want other
> processes to 'stay alive'?
>
> echo "Setting minimum res
On Thursday 29 March 2007 23:06, Li Yu wrote:
> Dmitry Torokhov wrote:
> > On 3/28/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
> >>
> >> The crucial thing here is that all reports but the ones that the driver
> >> registered to will be processed in a standard way by the generic hid bus
> >> layer, a
added netdev.
On 3/29/07, Andrei Popa <[EMAIL PROTECTED]> wrote:
In a dual core 2 server with an intel motherboard and 5 network
cards(two onboard) and 1 pci express card with two slots and one pci-x
pci64 card the kernel sees all of them in dmesg but in mii-tool are
misnumbered and one card is
It seems that there must be at least one node in mems
and at least one CPU in cpus in order to be able to assign
tasks to a cpuset. This makes sense. And I think it would
also make sense to include a mems setting in the basic usage
section of the documentation.
I also wonder if something logged to
On Thu, Mar 29, 2007 at 05:41:45PM -0700, Andrew Morton wrote:
> On Thu, 29 Mar 2007 12:30:59 +0900
> Simon Horman <[EMAIL PROTECTED]> wrote:
>
> > [PATCH] kdump/kexec: calculate note size at compile time
>
> i386 allmodconfig, gcc-4.1.0:
>
> In file included from init/initramfs.c:508:
> include
>What problem are you trying to solve? IOW, how do you know it's not
>just an artifact of diferent load average calculation between 2.4 and
>2.6?
>
>Are you actually seeing reduced throughput/performance? Or are you
>just looking at load average?
>
>Lee
Well the problem is apparent, we are havin
On 3/29/07, Wu, Bryan <[EMAIL PROTECTED]> wrote:
On architectures with MMU, malloc takes about the same speed,
indepentant of malloc size, while on the Blackfin (NOMMU), as the malloc
size increases, the time that malloc consumes grows
err, this is not the direction we wanted to go ... this
When register serial driver as a console, the driver function
my_remove()
my_shutdown()
seems be never called.
So the driver can't reclaim resource when the command "reboot" is issued.
Is it intended?
-Aubrey
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the bod
On Mar 30 2007 11:37, Conke Hu wrote:
>
> Is it possible to use C++ in linux kernel module? how?
> I've tested but failed, there is an unknown symbol in the .o file from
> c++ source code.
You answered it yourself. Linux does not have a C++ runtime.
It is possible to use a very limited set of C++
On architectures with MMU, malloc takes about the same speed,
indepentant of malloc size, while on the Blackfin (NOMMU), as the malloc
size increases, the time that malloc consumes grows
This small application, which does a bunch of mallocs, and times them
with gettimeofday():
===
Is it possible to use C++ in linux kernel module? how?
I've tested but failed, there is an unknown symbol in the .o file from
c++ source code.
Conke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
Greg KH ([EMAIL PROTECTED]) said:
> > If interfaces have to change, so be it. But changing the rules for
> > using them years after it's implemented and then claiming "you didn't
> > read the instructions" is pretty lame.
>
> That documentation has been in the kernel tree for almost a full year:
On Mar 28, 2007, at 16:14:54, Andrew Morton wrote:
On Wed, 28 Mar 2007 19:23:32 +0200 (CEST)
Jiri Kosina <[EMAIL PROTECTED]> wrote:
blockdev: bd_claim_by_kobject() could check value of unititalized
pointer
Fixes this warning:
fs/block_dev.c: In function `bd_claim_by_kobject':
fs/block_dev.c
On Thu, 2007-03-29 at 14:19 +0200, Andi Kleen wrote:
> On Thu, Mar 29, 2007 at 09:06:57PM +1000, Rusty Russell wrote:
[SNIP: processor-flags.h patch for i386 ]
> Ok. Can you do it for x86-64 too?
OK, here it is. Compiles, but -rc5-mm2 doesn't link for me on x86-64 at
the moment.
Something seem
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
arch/blackfin/mach-bf537/boards/eth_mac.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/blackfin/mach-bf537/boards/eth_mac.c
b/arch/blackfin/mach-bf537/boards/eth_mac.c
index 81544a1..e129a08 100644
--- a/arch/bl
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
arch/blackfin/mach-common/ints-priority-dc.c | 36 +++-
arch/blackfin/mach-common/ints-priority-sc.c | 38 +-
include/asm-blackfin/gpio.h |6 ++--
3 files changed, 63 insertions(+)
Dmitry Torokhov wrote:
> On 3/28/07, Jiri Kosina <[EMAIL PROTECTED]> wrote:
>>
>> The crucial thing here is that all reports but the ones that the driver
>> registered to will be processed in a standard way by the generic hid bus
>> layer, and those reports that the driver registered to will be
>>
On Wed, Mar 28, 2007 at 08:41:38PM -0400, Bill Nottingham wrote:
> Greg KH ([EMAIL PROTECTED]) said:
> > If you follow the rules in Documentation/ABI/testing/sysfs-class your
> > program will not have any problems.
>
> Oh, of *course*. We add interfaces and then claim years later,
> after code ha
On Fri, Mar 30, 2007 at 12:36:35PM +1000, Rusty Russell wrote:
> On Thu, 2007-03-29 at 13:16 +0200, Andi Kleen wrote:
> > Please clean it up properly with two structs.
>
> Not sure about this, now I've done it. Running it here.
>
> If you like it, I can do x86-64 as well.
>
> ==
> lguest define
On Fri, 30 Mar 2007, Nick Piggin wrote:
> > I slightly modified it to use cycles:
> >
> > http://www.xmailserver.org/qspins.c
>
> Slightly more than slightly ;)
>
> You want to have a delay _outside_ the critical section as well, for
> multi-thread tests, otherwise the releasing CPU often just
On Thu, 2007-03-29 at 13:16 +0200, Andi Kleen wrote:
> Please clean it up properly with two structs.
Not sure about this, now I've done it. Running it here.
If you like it, I can do x86-64 as well.
==
lguest defines its own TSS struct because the "struct tss_struct"
contains linux-specific addi
On Thu, Mar 29, 2007 at 10:06:41PM -0400, Lee Revell wrote:
> On 3/29/07, Davide Libenzi wrote:
> >On Thu, 29 Mar 2007, Oleg Nesterov wrote:
> >
> >> On 03/28, Nick Piggin wrote:
> >> >
> >> > Well with my queued spinlocks, all that lockbreak stuff can just come
> >out
> >> > of the spin_lock, br
On 3/29/07, Ed Sweetman <[EMAIL PROTECTED]> wrote:
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35
PST 2006
PCI: Setting latency timer of device :01:00.0 to 64
NVRM: loading NVIDIA UNIX x86_64 Kernel Module 1.0-9746 Fri Dec 15 10:19:35
PST 2006
**WARNING** I2
On 3/29/07, Elliott Johnson <[EMAIL PROTECTED]> wrote:
Hello,
I've been upgrading a few machines here at work and noticed some problems with
high system cpu usage on one machine. In trying to debug the problem I've come
across a few confusing stats that I was hoping could be cleared up by som
On 3/29/07, Davide Libenzi wrote:
On Thu, 29 Mar 2007, Oleg Nesterov wrote:
> On 03/28, Nick Piggin wrote:
> >
> > Well with my queued spinlocks, all that lockbreak stuff can just come out
> > of the spin_lock, break_lock out of the spinlock structure, and
> > need_lockbreak just becomes (lock-
On Thu, Mar 29, 2007 at 05:27:24PM -0700, Davide Libenzi wrote:
> On Thu, 29 Mar 2007, Nick Piggin wrote:
>
> > On Thu, Mar 29, 2007 at 03:36:52AM +0200, Nick Piggin wrote:
> > > In most cases, no. For the uncontended case they should be about the
> > > same. They have the same spinning behaviour.
On Thu, Mar 29, 2007 at 10:42:13PM +0400, Oleg Nesterov wrote:
> On 03/28, Nick Piggin wrote:
> >
> > Well with my queued spinlocks, all that lockbreak stuff can just come out
> > of the spin_lock, break_lock out of the spinlock structure, and
> > need_lockbreak just becomes (lock->qhead - lock->qt
On Friday 30 March 2007 03:09:14 David Brownell wrote:
> On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
> > On Friday 30 March 2007 00:33:35 David Brownell wrote:
> > > On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
>
> > > > So the only way out is to emulate RTC using HPET,
>
On Wed, Mar 28, 2007 at 09:05:03PM +0200, Andi Kleen wrote:
>
> > #include
> > #include
> > +#include
> Sorry no. system.h is the header from hell and putting it into a
> "basic" header like atomic_t will likely cause all kinds of
> problems.
OK, I'll figure out someplace else for it.
On Thu, Mar 29, 2007 at 02:36:43AM +0200, Blaisorblade wrote:
> > Sometimes you need to. I'd probably just remove the do_ubd check and
> > always recall the request function when handling completions, it's
> > easier and safe.
If I'm understanding this correctly, this is what happens now. There
i
>-Original Message-
>From: Darrick J. Wong [mailto:[EMAIL PROTECTED]
>Sent: Thursday, March 29, 2007 5:43 PM
>To: Pallipadi, Venkatesh
>Cc: linux-kernel@vger.kernel.org
>Subject: Dependent CPU core speed reporting not updated with
>CPUFREQ_SHARED_TYPE_HW?
>
>Hi Venki,
>
>I have a dual-
Hi Venki,
I have a dual-Woodcrest machine here with _PSD tables that specify that
cpufreq coordination between cores is done in hardware with
DOMAIN_COORD_TYPE_HW_ALL. On this particular machine, CPU 0 and CPU 2
are on the same package, and it looks like they have to be at the same
frequency.
Ho
On Thu, 29 Mar 2007 12:30:59 +0900
Simon Horman <[EMAIL PROTECTED]> wrote:
> [PATCH] kdump/kexec: calculate note size at compile time
i386 allmodconfig, gcc-4.1.0:
In file included from init/initramfs.c:508:
include/linux/kexec.h:148: error: variable-size type declared outside of any
function
-
On Thu, 29 Mar 2007, Nick Piggin wrote:
> On Thu, Mar 29, 2007 at 03:36:52AM +0200, Nick Piggin wrote:
> > In most cases, no. For the uncontended case they should be about the
> > same. They have the same spinning behaviour. However there is a little
> > window where they might be a bit slower I t
On Mar 29, 2007, at 20:09:11, Jan Engelhardt wrote:
On Mar 29 2007 18:54, Kyle Moffett wrote:
One thing that I think is fairly non-obvious to newcomers is that
Linux kernel development is not done at all the way they teach you
in your Large Scale Software Engineering classes. Many of those
On Mar 29 2007 18:54, Kyle Moffett wrote:
>
> One thing that I think is fairly non-obvious to newcomers is that Linux kernel
> development is not done at all the way they teach you in your Large Scale
> Software Engineering classes. Many of those classes talk much about careful
> design (whether
On Thursday 29 March 2007 4:29 pm, Maxim Levitsky wrote:
> On Friday 30 March 2007 00:33:35 David Brownell wrote:
> > On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> > > So the only way out is to emulate RTC using HPET,
> > > It is done this way in old rtc driver, rtc-cmos should do the sam
On Friday 30 March 2007 00:33:35 David Brownell wrote:
> On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> > On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
>
> > When HPET is active it eats RTC IRQ,
>
> Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode".
> In t
On Mar 29, 2007, at 16:59:36, Ahmed S. Darwish wrote:
On Thu, Mar 29, 2007 at 06:32:21PM +0800, Cong WANG wrote:
Second, in fact, I am also a college student and also want to find
a suitable and real task in linux kernel for me to work on. KJ
doesn't help much. ;-p
No, it really helps alot,
On Wednesday 28 March 2007 2:27 pm, Maxim wrote:
> On Wednesday 28 March 2007 22:59:26 David Brownell wrote:
> When HPET is active it eats RTC IRQ,
Only when HPET timers 0 and 1 are set up for "Legacy Replacement Mode".
In the more sensible "Standard Mode", they have their own IRQs.
>
Francois Romieu <[EMAIL PROTECTED]> :
[...]
BUG: spinlock already unlocked on CPU#0, swapper/0
Almost perfect...
---
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majo
On Fri, Mar 30, 2007 at 12:01:11AM +0200, J.A. Magallón wrote:
> On Thu, 29 Mar 2007 19:52:54 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote:
>
> > On Thu, Mar 29, 2007 at 01:18:38AM +0200, J.A. Magallón wrote:
> > > Hi all...
> > >
> > > I post this here as it can be of direct interest for kernel
Hello,
I've been upgrading a few machines here at work and noticed some problems with
high system cpu usage on one machine. In trying to debug the problem I've come
across a few confusing stats that I was hoping could be cleared up by someone
on this list.
Firstly some info about the system.
On Thursday 29 March 2007 3:06 pm, Randy Dunlap wrote:
> On Tue, 20 Feb 2007 01:06:54 +0100 Adrian Bunk wrote:
>
> > On Sun, Jan 14, 2007 at 06:36:10AM -0800, David Brownell wrote:
> > > On Sunday 14 January 2007 1:10 am, Adrian Bunk wrote:
> > > > <-- snip -->
> > >
> > > Waiting for Tony to s
On Thu, 29 Mar 2007 16:10:50 -0600 Eric W. Biederman wrote:
> Andrew Morton <[EMAIL PROTECTED]> writes:
> >
> > Ah. I assume you have CONFIG_SYSCTL=y, CONFIG_PROC_SYSCTL=n?
> >
> >
> >
> >
> > From: Andrew Morton <[EMAIL PROTECTED]>
> >
> > We're using #ifdef CONFIG_SYSCTL, but we should be using
On Thu, 29 Mar 2007 16:10:50 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Andrew Morton <[EMAIL PROTECTED]> writes:
> >
> > Ah. I assume you have CONFIG_SYSCTL=y, CONFIG_PROC_SYSCTL=n?
> >
> >
> >
> >
> > From: Andrew Morton <[EMAIL PROTECTED]>
> >
> > We're using #ifdef CONFIG_SYSCTL, bu
On Thu, 29 Mar 2007, Oleg Nesterov wrote:
> On 03/28, Nick Piggin wrote:
> >
> > Well with my queued spinlocks, all that lockbreak stuff can just come out
> > of the spin_lock, break_lock out of the spinlock structure, and
> > need_lockbreak just becomes (lock->qhead - lock->qtail > 1).
>
> Q: qu
Williams, Mitch A wrote:
> Chuck Ebbert wrote:
>> Are you going to post one for 2.6.20 as well? Some people might be
>> interested...
>
> The first time I posted this patch, Greg KH indicated that he thought
> it was too intrusive to add to -stable, especially considering that
> our MSI-X capable
Starting a VM for Win98SE:
posidon:root> /usr/local/kvm-15/bin/qemu -m 128 -hda Win98SE-2.kvm
exception 13 (0)
rax f000ff53 rbx rcx 005a rdx
000e
rsi 001100c4 rdi 0002a002 rsp 00086650 rbp
667a
r8
Andrew Morton <[EMAIL PROTECTED]> writes:
>
> Ah. I assume you have CONFIG_SYSCTL=y, CONFIG_PROC_SYSCTL=n?
>
>
>
>
> From: Andrew Morton <[EMAIL PROTECTED]>
>
> We're using #ifdef CONFIG_SYSCTL, but we should be using CONFIG_PROC_SYSCTL,
> so we get
I have no problem with the patch it is clearly
On Tue, 20 Feb 2007 01:06:54 +0100 Adrian Bunk wrote:
> On Sun, Jan 14, 2007 at 06:36:10AM -0800, David Brownell wrote:
> > On Sunday 14 January 2007 1:10 am, Adrian Bunk wrote:
> > > <-- snip -->
> >
> > Waiting for Tony to submit bugfixes to his driver...
>
> Still unfixed as of 2.6.20-mm1.
On Thursday 29 March 2007 23:16, Linus Torvalds wrote:
>
> On Thu, 29 Mar 2007, Andi Kleen wrote:
> >
> > Here's a patch. I don't have a system with C1E, so i only tested that
> > the apic timer still works on a older AMD box.
>
> I think this looks better than what we have now, but it would loo
On Thursday 29 March 2007 23:45, Andreas Mohr wrote:
> Hi,
>
> On Thu, Mar 29, 2007 at 02:16:54PM -0700, Linus Torvalds wrote:
> >
> >
> > On Thu, 29 Mar 2007, Andi Kleen wrote:
> > >
> > > Here's a patch. I don't have a system with C1E, so i only tested that
> > > the apic timer still works on
Chuck Ebbert wrote:
>Are you going to post one for 2.6.20 as well? Some people might be
>interested...
The first time I posted this patch, Greg KH indicated that he thought
it was too intrusive to add to -stable, especially considering that
our MSI-X capable hardware isn't in the field yet.
So th
On Thu, 29 Mar 2007 19:52:54 +0200, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Thu, Mar 29, 2007 at 01:18:38AM +0200, J.A. Magallón wrote:
> > Hi all...
> >
> > I post this here as it can be of direct interest for kernel development
> > (as I recall many discussions about inlining yes or no...).
Eric W. Biederman wrote:
>Do we still need the flush the set affinity routines?
>Shouldn't flush in mask and unmask should now be enough?
Yeah, I think you're right. I've removed that call, and
we're running some basic validation on the change. I'll
post a new patch tomorrow AM.
-Mitch
-
To un
On Thu, 29 Mar 2007, Andreas Mohr wrote:
>
> Please don't, this would break the interface logically.
> X86_FEATURE_xxx usually denotes a *feature*, not a "feature"
> (Micro$oft speak for "bug" ;).
Sure, we could make it positive instead, and I agree it would make code
nicer to read.
> Thus,
Hello,
sorry for the scarce technical information in this email. this is
mostly due to it being mentioned before. I experience problems with
the P5B-VM mainboard when using it with 4gb and Linux. When the Memory
remap is activated, the internal network card is unusable (disabled).
The system turn
On Thu, 29 Mar 2007 23:43:28 +0200, Grzegorz Chwesewicz wrote
> On Thu, 29 Mar 2007 22:49:37 +0200, Andi Kleen wrote
> > > Reviewed but not tested. Needs to be wrapped in an AMD specific
> > > call.
> >
> > Here's a patch. I don't have a system with C1E, so i only tested that
> > the apic timer s
Hi!
> >
> > (Machine was suspended/resumed before this).
> >
> > mount /dev/mmc1 /mnt
> >
>
> Driver? Reproducable? Vanilla git kernel?
It was driver for
15:00.2 Generic system peripheral [0805]: Ricoh Co Ltd R5C822
SD/SDIO/MMC/MS/MSPro Host Adapter
...but problem is either gone in -rc5,
Hi!
> Pavel,
> fixed in -rc5?
Yes, I did quick test and then some more testing, and it seems
gone.
> Subject: s2ram autowake regression (ACPI?)
> References : http://lkml.org/lkml/2007/3/20/96
> Submitter : Pavel Machek <[EMAIL PROTECTED]>
> Handled-By : Len Brown <[EMAIL PROTECTED]>
> St
Sorry, this wasn't supposed to happen. Already done...
Unsubscribed due to lack of a digest mail.
I wonder why people can't send their unsubscribe message to the same
address they sent their subscribe message to.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
Hmm. I've reproduced these problems with vanilla 2.6.21-rc5, so the
latest acpi-git changes are off the hook. I am currently trying to
reproduce the problems with 2.6.21-rc4. I'll let you know how it
turns out.
Miles
-
To unsubscribe from this list: send the line "unsubscribe linux-kern
> But when writing, what is the difference between queuing multiple tagged
> writes, and sending down multiple untagged cached writes that complete
> immediately and actually hit the disk later? Either way the host keeps
> sending writes to the disk until it's buffers are full, and the disk is
From: Jan Engelhardt <[EMAIL PROTECTED]>
Date: Thu, 29 Mar 2007 23:42:17 +0200 (MEST)
> > unsubscribe linux-kernel ..
>
> I wonder why people can't send their unsubscribe message to the same
> address they sent their subscribe message to.
People get frustrated that it doesn't work then start do
Hi,
On Thu, Mar 29, 2007 at 02:16:54PM -0700, Linus Torvalds wrote:
>
>
> On Thu, 29 Mar 2007, Andi Kleen wrote:
> >
> > Here's a patch. I don't have a system with C1E, so i only tested that
> > the apic timer still works on a older AMD box.
>
> I think this looks better than what we have now,
On Thu, 29 Mar 2007 22:49:37 +0200, Andi Kleen wrote
> > Reviewed but not tested. Needs to be wrapped in an AMD specific
> > call.
>
> Here's a patch. I don't have a system with C1E, so i only tested that
> the apic timer still works on a older AMD box.
>
> Would be good if someone with a Turion
>
> unsubscribe linux-kernel ..
I wonder why people can't send their unsubscribe message to the same
address they sent their subscribe message to.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http:
unsubscribe linux-kernel [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wed, 28 Mar 2007, Roland McGrath wrote:
> Sorry I've been slow in responding to your most recent version.
> I fell into a large hole and couldn't get out until I fixed some bugs.
That's okay; the same thing happens to everyone from time to time.
> > No, I'm not confused and neither are you.
On Thu, 29 Mar 2007 16:32:19 -0400
"Ryan Hope" <[EMAIL PROTECTED]> wrote:
> I was not able to boot 2.6.21-rc3-mm* so I can not tell if this problem
> exists in that series but with 2.6.21-rc4-mm* and 2.6.21-rc5-mm* I can not
> get into Xorg. I disabled frame buffer support but when X loads normal
Hello,
In a dual core 2 server with an intel motherboard and 5 network
cards(two onboard) and 1 pci express card with two slots and one pci-x
pci64 card the kernel sees all of them in dmesg but in mii-tool are
misnumbered and one card is missing.
(please CC as I am not subscribed to lkml)
from d
On Thu, 29 Mar 2007 20:20:20 +0200
Helge Hafting <[EMAIL PROTECTED]> wrote:
> I tried compiling this on x86-64, and got this compile error:
> CC init/version.o
> CC init/missing_syscalls.o
> In file included from init/missing_syscalls.c:97:
> init/missing_syscalls.h:279:2: warning: #
On Thu, 29 Mar 2007, Andi Kleen wrote:
>
> Here's a patch. I don't have a system with C1E, so i only tested that
> the apic timer still works on a older AMD box.
I think this looks better than what we have now, but it would look even
better if the core CPUID stuff was in arch/i386/kernel/cpu/a
On Thu, 29 Mar 2007 20:16:59 +0100
David Howells <[EMAIL PROTECTED]> wrote:
> Pavel Machek <[EMAIL PROTECTED]> wrote:
>
> > > Userland core dumper is useful because it is relatively easy to be
> > > customized, but its reliability highly depends on the application
> > > programs.
> >
> > Fix use
When the dump cannot occur most likely because of a full file system
and the page to be written is the zero page, the call to
page_cache_release() is missed.
Signed-off-by: Brian Pomerantz <[EMAIL PROTECTED]>
diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
index a2fceba..9cc4f0a 100644
--- a/fs/b
1 - 100 of 263 matches
Mail list logo
