* Gene Heskett <[EMAIL PROTECTED]> wrote:
> Hi Ingo;
>
> Running 2.6.21-rc5 tonight.
>
> It appears that as of 2.6.21-rc5, (actually anything with a 2.6.21 in
> its version string) amanda is still a loser. [...]
here 'is a loser' means: "tries to back up way too much stuff instead of
doing
2007/4/1, Andrew Morton <[EMAIL PROTECTED]>:
On Sun, 1 Apr 2007 14:20:46 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
>
> >
> > Also, please always prepare patches in `patch -p1' form, as per
> > http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt, thanks.
> >
> >
>
> Sorry. I am confused
Am Mittwoch 28 März 2007 schrieb Prakash Punnoor:
> Am Mittwoch 28 März 2007 schrieb Con Kolivas:
> > I'm cautiously optimistic that we're at the thin edge of the bugfix wedge
> > now.
> >
> > ---
> > set_load_weight() should be performed after p->quota is set. This fixes a
> > large SMP
Pedram M wrote:
How about this one? Am I doing it right now?
If not, please try to explain more to me what I am
doing wrong.
You need a changelog entry (or explanation of what you're doing). You
need a signed-off-by line and your patch needs to apply to the root of
the kernel tree with -p1,
On Sun, 1 Apr 2007 14:20:46 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
>
> >
> > Also, please always prepare patches in `patch -p1' form, as per
> > http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt, thanks.
> >
> >
>
> Sorry. I am confused with this. Does that mean I should make
On Sun, 01 Apr 2007 00:15:51 -0600 [EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Does anyone know how to express the constraint of a 2M aligned number in
> Kconfig?
Nope, but we could make CONFIG_PHYSICAL_START be in units of 2MB, which
would be a bit hard to use.
Adding a BUILD_BUG_ON which
Alexey Starikovskiy wrote:
> Could you try to unload or disable hardware sensors and check if it
> helps?
> CONFIG_I2C=m
> CONFIG_I2C_ALGOBIT=m
> CONFIG_I2C_ALGOPCA=m
> CONFIG_I2C_I810=m
> CONFIG_I2C_PIIX4=m
> CONFIG_SENSORS_DS1337=m
> CONFIG_SENSORS_DS1374=m
> CONFIG_SENSORS_EEPROM=m
>
2007/4/1, Andrew Morton <[EMAIL PROTECTED]>:
On Sat, 31 Mar 2007 10:30:31 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
> Since kobject_add, sysfs_create_link and sysfs_create_file are marked
> as '__must_check', so we must always check their return values, or gcc
> will give us warnings.
>
>
Hi,
On Sat, Mar 31, 2007 at 10:24:12PM -0700, Pedram M wrote:
> How about this one? Am I doing it right now?
> If not, please try to explain more to me what I am
> doing wrong.
You have made several mistakes :
- you must select an appropriate subject for your mail. Nobody cares
that it is
[EMAIL PROTECTED] writes:
> I had the same with this .config from 2.6.21-rc3-mm2 after running 'make
> oldconfig' and answering N to all new questions. Then, I tweaked some
> items, mostly to see if there was an 'align kernel' item in there
> somewhere. Diff between _working_ 2.6.21-rc5-mm3
On Sat, 31 Mar 2007 13:09:29 -0700 Davide Libenzi
wrote:
> This patch wire the signalfd system call to the i386 architecture.
>
all your x86 syscall numbers got incremented due to lutiemsat().
The revoke sycalls got incremented by three.
-
To unsubscribe from this list: send the line
Andi Kleen wrote:
I think I would prefer you touch the generic code. This new hook is ugly.
What new hook? The hook has been there for sometime, and now we are
using it to fix a bug. I do not want to touch generic or arch code at
this point in the 2.6.21 release.
And the lazy mode is
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Sat, Mar 31, 2007 at 12:53:03AM -0700
> On Sat, 31 Mar 2007 09:12:20 +0200 Helge Hafting <[EMAIL PROTECTED]> wrote:
>
> > A new error for me:
> >
> > loading 2.6.21rc5mm3
> > Bios data check successful
> > Destination address not 2M aligned
> > --
Adrian Bunk wrote:
> Subject: ThinkPad X60: resume no longer works (PCI related?)
> References : http://lkml.org/lkml/2007/3/13/3
> Submitter : Dave Jones <[EMAIL PROTECTED]>
> Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> Caused-By : PCI merge
> commit
On Sat, 31 Mar 2007 10:30:31 +0800 "Cong WANG" <[EMAIL PROTECTED]> wrote:
> Since kobject_add, sysfs_create_link and sysfs_create_file are marked
> as '__must_check', so we must always check their return values, or gcc
> will give us warnings.
>
> Signed-off-by: Cong WANG <[EMAIL PROTECTED]>
>
On Sat, 31 Mar 2007 01:08:14 +0200 "Paolo 'Blaisorblade' Giarrusso" <[EMAIL
PROTECTED]> wrote:
> set_up_list3s is not __init and references initkmem_list3.
>
> Also, kmem_cache_create calls setup_cpu_cache which calls set_up_list3s. The
> state machine _may_ prevent the code from accessing this
How about this one? Am I doing it right now?
If not, please try to explain more to me what I am
doing wrong.
@@ -4760,7 +4760,7 @@
for (i = 0; i < NR_CARDS; i++) {
/* look for a Cyclades card by vendor and device id */
while ((device_id =
Hi Ingo;
Running 2.6.21-rc5 tonight.
It appears that as of 2.6.21-rc5, (actually anything with a 2.6.21 in its
version string) amanda is still a loser.
>From an amstatus report as the back up is just getting started,
and amanda has completed the estimates:
[EMAIL PROTECTED] Daily]# amstatus
> From: Andrew Morton
> Newsgroups: gmane.linux.kernel
> Subject: Re: [PATCH] Fix build error due to not including
> Date: Sun, 18 Mar 2007 22:01:48 -0800
>
> If is a bit of a pain to maintain CONFIG_SYSFS=n. But then, it's
> realtively easy to fix things when they do break, and sysfs does
On Sat, Mar 31, 2007 at 08:03:16PM -0700, Jim Paris wrote:
> Since it shows up under heavy load that includes unrelated devices, I
> think ruling out hardware problems is important. Some suggestions:
I've been able to narrow it down to the Realtek Ethernet card. I can't
reproduce the problem
On 3/31/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> Yes, the distros do, and they recommend it to their users a lot.
Thanks. In that case I think we should retain the max_loop module parameter
for now.
Ken, when you respin that patch could you restore max_loop, and make its
use trigger a
On Saturday 31 March 2007 8:13 pm, Jeff Chua wrote:
> On 4/1/07, David Brownell <[EMAIL PROTECTED]> wrote:
> > for those will all get grouped together ... suspended "very late" and
> > resumed "very early", regardless of when they get registered. Pretty
> > much the driver model parts of what
Aaron Lehmann wrote:
> I discovered a reproducible way of causing silent file corruption.
...
> 1. Heavy Ethernet load (nc remotehost < /dev/zero)
> 2. Heavy disk write load on any non-sata_sil drive (cat /dev/zero > /path)
> 3. Heavy disk read load on any other drive (tar c /path | cat >
On Sat, Mar 31, 2007 at 07:52:36PM -0700, Andrew Morton wrote:
> Are you able to provide us with some before-and-after data so we
> can see this corruption.
>
> See, if it's dropped-bits or shifted-data or eight-byte-aligned
> kernel addresses or whatever, that helps us generate theories..
Sure.
On 4/1/07, David Brownell <[EMAIL PROTECTED]> wrote:
for those will all get grouped together ... suspended "very late" and
resumed "very early", regardless of when they get registered. Pretty
much the driver model parts of what Linus was suggesting; clockevent
bits would still be needed.
I
On Saturday March 31, [EMAIL PROTECTED] wrote:
> hi list!
>
> in short:
> I created a partitioned raid6 array with 2 missing drives. Now, I want to add
> a device. It fails with:
> flockmock ~ # mdadm -a /dev/md_d4 /dev/sdb2
> mdadm: add new device failed for /dev/sdb2 as 4: Invalid argument
From: Daniel P. Engel <[EMAIL PROTECTED]>
Add the "Off-hook" and "Speaker" LED codes 0xb and 0xc to the hid-input
configuration,
mapping them to the 0x17 and 0x1e usages in the HID usage table.
Signed-off-by: Daniel P. Engel <[EMAIL PROTECTED]>
---
This patch is really being offered because
> On Sat, 31 Mar 2007 18:27:36 -0700 Aaron Lehmann <[EMAIL PROTECTED]> wrote:
> I have spent a lot of time trying to find a simpler test case. So far,
> as far as I can tell, there are three conditions that must be
> satisfied for corruption to occur:
>
> 1. Heavy Ethernet load (nc remotehost <
> From: Alan Cox
> Newsgroups: gmane.linux.kernel
> Subject: Re: broken device locking, sg vs. sg_io on block devices
> Date: Sun, 1 Apr 2007 01:14:52 +0100
>
[]
>> Again, it doesn't have to. It can pass the locking operations to the
>> related block device driver.
>
> No it can't. The driver has
Hello,
I discovered a reproducible way of causing silent file corruption.
Unfortunately, this method happens to me my backup procedure :(.
Background: I have five hard drives. sda and sdb are on a SiI 3112
card. sdc and sdd use onboard sata_via. hda uses onboard VIA VT8237
IDE. All filesystems
> On Sun, 1 Apr 2007 01:56:28 +0100 (BST) James Simmons <[EMAIL PROTECTED]>
> wrote:
>
> I can't seem to duplicate this error.
OK, I'll poke at it some more.
> Do you have any patches applied to
> the nvidia driver?
I don't think so - whatever's in -mm.
> On Mon, 26 Mar 2007, Andrew Morton
I can't seem to duplicate this error. Do you have any patches applied to
the nvidia driver?
On Mon, 26 Mar 2007, Andrew Morton wrote:
> On Tue, 20 Mar 2007 14:25:49 + (GMT) James Simmons <[EMAIL PROTECTED]>
> wrote:
>
> > This patch does several things to allow the underlying hardware to
Andrew Morton wrote:
On Sat, 31 Mar 2007 16:14:01 -0400 Stephen Clark <[EMAIL PROTECTED]> wrote:
Hello,
I have just tried booting the fc7-rc2 live cd on 2 of my laptops and it
failed on both.
Laptop 1 is an asus vbi s96f that get a panic that says exception in
interrupt routine
for
Hi
web.de> writes:
> Whenever you want to test some new kernel (feature), you may put you main
system at risk, exactly know what
> you`re doing - or - use UserModeLinux.
Why won't qemu work better in this case? I generally keep a debian testing
installation on disk and when I compile a new
hi list!
in short:
I created a partitioned raid6 array with 2 missing drives. Now, I want to add a
device. It fails with:
flockmock ~ # mdadm -a /dev/md_d4 /dev/sdb2
mdadm: add new device failed for /dev/sdb2 as 4: Invalid argument
I think it is the same problem as in:
On Saturday, 31 March 2007 23:23, Adrian Bunk wrote:
> On Sat, Mar 31, 2007 at 01:35:32PM -0700, Andrew Morton wrote:
> > On Sat, 31 Mar 2007 22:04:15 +0200 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> > wrote:
> >
> > > This patch appeard on LMKL six days ago and there have not been any
> > >
> > > The use of /dev/sg* is still common practice, its invention predates
> >
> > The /dev/sg interface cannot do the locking. If you use /dev/sg you are
>
> Again, it doesn't have to. It can pass the locking operations to the
> related block device driver.
No it can't. The driver has no idea
Hello !
i`m not very much into UML for the last months, but while playing around with
dm-loop i just got one idea i`d like to share.
Whenever you want to test some new kernel (feature), you may put you main
system at risk, exactly know what you`re doing - or - use UserModeLinux.
The "problem"
On Sat, 31 Mar 2007 21:35:19 +0200 (CEST), Jiri Kosina <[EMAIL PROTECTED]>
wrote:
> On Fri, 30 Mar 2007, Pete Zaitcev wrote:
> I think I see an issue here. Imagine that you boot a system initially with
> one keyboard connected (usb, ps/2, doesn't matter), and after some time
> you connect
On Fri, 30 Mar 2007, Dmitry Torokhov wrote:
> There should be one device and your driver should simply do:
> static void my_driver_hid_event(struct hid_device *hid, struct hid_field
> *field,
> struct hid_usage *usage, __s32 value)
> {
> if
#include
* Alan Cox [Sat, Mar 31 2007, 11:20:02PM]:
> > But the desktop needs some means to deal with that. AFAICS the only
> > feasible way for applications to communicate about device usage policy
> > is locking with O_EXCL. Many people do not realize that even read-only
>
> serial ports and
We've had various reports of some legacy "probe the hardware" style platform
drivers having nasty problems with hotplug support.
The core issue is that those legacy drivers don't fully conform to the driver
model. They assume a role that should be the responsibility of infrastructure
code:
Make note of the legacy "probe-the-hardware" drivers, and some APIs that are
mostly unused except by such drivers. We probably can't escape having legacy
drivers for a while (e.g. old ISA drivers), but we can at least discourage
this style code for new drivers, and unless it's unavoidable.
Location:
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/
git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.16.y.git
RSS feed of the git tree:
http://www.kernel.org/git/?p=linux/kernel/git/stable/linux-2.6.16.y.git;a=rss
Changes since 2.6.16.45:
Adrian Bunk (2):
Linux
On Saturday March 31, [EMAIL PROTECTED] wrote:
> On Sat, 31 Mar 2007 17:36:47 + Bernhard Rosenkraenzer <[EMAIL PROTECTED]>
> wrote:
>
> > I'm getting this Oops when booting an 2.6.21-rc5-mm1 or 2.6.21-rc5-mm2 on
> > an
> > Acer Aspire 1501 LMi in 32 bit mode (2.6.21-rc4-mm1 + hotfixes
On Sat, Mar 31, 2007 at 12:14:37PM +1000, Herbert Xu wrote:
> Indeed. That patch was buggy. Sorry for not catching this earlier.
Yep, thanks for the fix. I used the wrong length, then tested with a
case where nbytes would always be less than PAGE_SIZE, which doesn't hit
this problem.
On Sat, Mar 31, 2007 at 01:35:32PM -0700, Andrew Morton wrote:
> On Sat, 31 Mar 2007 22:04:15 +0200 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
>
> > This patch appeard on LMKL six days ago and there have not been any negative
> > comments since then, so I think I can try to make it
Adrian Bunk wrote:
> I have no strong opinion regarding this - if it's agreed upon that it's
> unlikely it will ever grow, I can also send an additional patch
> simplifying it.
I haven't got any response from the original person who submitted this
patch. It isn't clear to me whether this is a
> But the desktop needs some means to deal with that. AFAICS the only
> feasible way for applications to communicate about device usage policy
> is locking with O_EXCL. Many people do not realize that even read-only
serial ports and mail both use fcntl file locking , which is much more
flexible.
On Sat, Mar 31, 2007 at 02:05:23PM -0700, Jeremy Fitzhardinge wrote:
> Adrian Bunk wrote:
> > Instead of cleaning up this mess, please replace this patch with the
> > patch below.
> >
>
> Yeah, I considered that patch as a placeholder; I'd been wondering if it
> can be completely removed.
>
On Sat, 31 Mar 2007, Davide Libenzi wrote:
> +config SIGNALFD
> + bool "Eanble signalfd() system call" if EMBEDDED
^^
Alright ...
- Davide
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Adrian Bunk wrote:
> Instead of cleaning up this mess, please replace this patch with the
> patch below.
>
Yeah, I considered that patch as a placeholder; I'd been wondering if it
can be completely removed.
But this patch looks fine, though I'd go further - the lookup table of
pci ids is
On Sat, Mar 31, 2007 at 01:46:10PM -0700, Andrew Morton wrote:
> On Sat, 31 Mar 2007 16:14:01 -0400 Stephen Clark <[EMAIL PROTECTED]> wrote:
>...
> > Also it sets my hard
> > drive to udma/33 when it run find at udma/66 under 2.6.20.1.
>
> #3. Hopefully it's related to #2.
>...
No, this sounds
On Fri, Mar 30, 2007 at 01:05:59AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc5-mm2:
>...
> +add-file-position-info-to-proc.patch
>
> /proc feature work
>...
This patch makes the needlessly global
struct proc_fdinfo_file_operations static.
Signed-off-by: Adrian Bunk <[EMAIL
On Fri, Mar 30, 2007 at 01:05:59AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc5-mm2:
>...
> git-netdev-all.patch
>...
> git trees
>...
This patch makes the needlessly global PHY_DEVICES[] static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
BTW: Why is the name
On Fri, Mar 30, 2007 at 01:05:59AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc5-mm2:
>...
> +x86_64-mm-clean-up-mach_reboot_fixups.patch
>...
> A few x86 updates
>...
OMG - I'll never understand how someone could initially start doing this
hiding of a small fixup behind a config
This patch makes two needleesly global functions static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/net/bonding/bond_main.c |5 +++--
drivers/net/bonding/bonding.h |2 --
2 files changed, 3 insertions(+), 4 deletions(-)
---
On Sat, 31 Mar 2007 16:14:01 -0400 Stephen Clark <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have just tried booting the fc7-rc2 live cd on 2 of my laptops and it
> failed on both.
>
> Laptop 1 is an asus vbi s96f that get a panic that says exception in
> interrupt routine
> for my rtl8139.
>
>
On Fri, Mar 30, 2007 at 01:05:59AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc5-mm2:
>...
> +testing-patch-for-ali-pata-fixes-hopefully-for-the-problems-with-atapi-dma.patch
>
> pata experiment
>...
This patch makes the needlesly global ali_tf_load() static.
Signed-off-by:
On Saturday, 31 March 2007 22:35, Andrew Morton wrote:
> On Sat, 31 Mar 2007 22:04:15 +0200 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
> wrote:
>
> > This patch appeard on LMKL six days ago and there have not been any negative
> > comments since then, so I think I can try to make it official.
> >
On Sat, 31 Mar 2007 20:44:58 +0200 Maciej Soltysiak <[EMAIL PROTECTED]> wrote:
> Hi,
>
> here's more...
>
> BUG: unable to handle kernel NULL pointer dereference at virtual address
>
> printing eip:
>
> *pde =
> Oops: [#1]
> Modules linked in: binfmt_misc sit
On Sat, 31 Mar 2007 22:04:15 +0200 "Rafael J. Wysocki" <[EMAIL PROTECTED]>
wrote:
> This patch appeard on LMKL six days ago and there have not been any negative
> comments since then, so I think I can try to make it official.
>
> ---
> From: Rafael J. Wysocki <[EMAIL PROTECTED]>
>
> Fix the
This patch series implements the new signalfd() system call.
I took part of the original Linus code (and you know how
badly it can be broken :), and I added even more breakage ;)
Signals are fetched from the same signal queue used by the process,
so signalfd will compete with standard kernel
This patch wire the timerfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/arch/x86_64/ia32/ia32entry.S
===
---
This patch wire the timerfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/arch/i386/kernel/syscall_table.S
===
---
Hello,
I have just tried booting the fc7-rc2 live cd on 2 of my laptops and it
failed on both.
Laptop 1 is an asus vbi s96f that get a panic that says exception in
interrupt routine
for my rtl8139.
This device works fine in 2.6.20.2
$ lspci -v
00:00.0 Host bridge: Intel Corporation Mobile
This is a very simple and light file descriptor, that can be used as
event wait/dispatch by userspace (both wait and dispatch) and by the
kernel (dispatch only). It can be used instead of pipe(2) in all cases
where those would simply be used to signal events. Their kernel overhead
is much lower
This patch implement the necessary compat code for the timerfd system call.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/fs/compat.c
===
--- linux-2.6.21-rc5.fds.orig/fs/compat.c 2007-03-31
This is an example about how to add eventfd support to the current KAIO code,
in order to enable KAIO to post readiness events to a pollable fd
(hence compatible with POSIX select/poll). The KAIO code simply signals
the eventfd fd when events are ready, and this triggers a POLLIN in the fd.
This
This patch wire the eventfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/arch/i386/kernel/syscall_table.S
===
---
This patch wire the eventfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/arch/x86_64/ia32/ia32entry.S
===
---
This patch wire the signalfd system call to the x86_64 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/include/asm-x86_64/unistd.h
===
--- linux-2.6.21-rc5.fds.orig/include/asm-x86_64/unistd.h
This patch introduces a new system call for timers events delivered
though file descriptors. This allows timer event to be used with
standard POSIX poll(2), select(2) and read(2). As a consequence of
supporting the Linux f_op->poll subsystem, they can be used with
epoll(2) too.
The system call is
This patch wire the signalfd system call to the i386 architecture.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/arch/i386/kernel/syscall_table.S
===
---
This patch add an anonymous inode source, to be used for files that need
and inode only in order to create a file*. We do not care of having an
inode for each file, and we do not even care of having different names in
the associated dentries (dentry names will be same for classes of file*).
This patch implement the necessary compat code for the signalfd system call.
Signed-off-by: Davide Libenzi
- Davide
Index: linux-2.6.21-rc5.fds/fs/compat.c
===
--- linux-2.6.21-rc5.fds.orig/fs/compat.c 2007-03-31
Hi,
This patch appeard on LMKL six days ago and there have not been any negative
comments since then, so I think I can try to make it official.
---
From: Rafael J. Wysocki <[EMAIL PROTECTED]>
Fix the regression resulting from the recent change of suspend code ordering
that causes systems based
On Sat, 31 Mar 2007, Andrew Morton wrote:
> Can we disable SLUB on i386 in Kconfig until it gets sorted out?
Yes just do not apply this patch. The first one disables SLUB on i386.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Sat, 31 Mar 2007 11:31:07 -0800 (PST) Christoph Lameter <[EMAIL PROTECTED]>
wrote:
> Fixup i386 arch for SLUB support
>
> i386 arch code currently uses the page struct of slabs for various purposes.
> This interferes with slub and so SLUB has been disabled for i386 by setting
>
On Fri, 30 Mar 2007, Andrew Morton wrote:
> On Fri, 30 Mar 2007 18:11:55 -0700 (PDT) Davide Libenzi
> wrote:
>
> >
> > > > + */
> > >
> > > So it is the caller's responsibility to ensure that *file refers to an
> > > eventfd file?
> >
> > In which function? I lost you ...
> >
>
>
On Fri, 30 Mar 2007, Andrew Morton wrote:
> On Fri, 30 Mar 2007 17:47:28 -0700 (PDT) Davide Libenzi
> wrote:
>
> > On Fri, 30 Mar 2007, Andrew Morton wrote:
> >
> > > > +struct timerfd_ctx {
> > > > + struct hrtimer tmr;
> > > > + ktime_t tintv;
> > > > + spinlock_t lock;
>
On Sat, 31 Mar 2007 17:36:47 + Bernhard Rosenkraenzer <[EMAIL PROTECTED]>
wrote:
> I'm getting this Oops when booting an 2.6.21-rc5-mm1 or 2.6.21-rc5-mm2 on an
> Acer Aspire 1501 LMi in 32 bit mode (2.6.21-rc4-mm1 + hotfixes works
> perfectly):
>
> xor: automatically using best
On Saturday 31 March 2007 11:18 am, David Brownell wrote:
> ( please remove obsolute [EMAIL PROTECTED] from further messages!! )
>
> On Saturday 31 March 2007 10:02 am, Ingo Molnar wrote:
> >
> > i dont think there's any particular problem here because suspend/resume
> > wont be done during
/*
* Slabinfo: Tool to get reports about slabs
*
* (C) 2007 sgi, Christoph Lameter <[EMAIL PROTECTED]>
*
* Compile by doing:
*
* gcc -o slabinfo slabinfo.c
*/
#include
#include
#include
#include
#include
#include
#include
char buffer[200];
int show_alias = 0;
int show_slab = 1;
Fixup i386 arch for SLUB support
i386 arch code currently uses the page struct of slabs for various purposes.
This interferes with slub and so SLUB has been disabled for i386 by setting
ARCH_USES_SLAB_PAGE_STRUCT.
This patch removes the use of page sized slabs for maintaining pgds and pmds.
[PATCH] SLUB The unqueued slab allocator v6
Note that the definition of the return type of ksize() is currently
different between mm and Linus' tree. Patch is conforming to mm.
This patch also needs sprint_symbol() support from mm.
V5->V6:
- Straighten out various coding issues u.a. to make the
On Fri, 30 Mar 2007, Pete Zaitcev wrote:
> @@ -1328,9 +1340,18 @@ static int hid_probe(struct usb_interface *intf, const
> struct usb_device_id *id)
> return -ENODEV;
> }
>
> - if ((hid->claimed & HID_CLAIMED_INPUT))
> + if ((hid->claimed & HID_CLAIMED_INPUT)) {
>
On Fri, Mar 30, 2007 at 01:05:59AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.21-rc5-mm2:
>...
> -drivers-net-vioc-possible-cleanups.patch
>...
> Merged into mainline or a subsystem tree.
>...
Please give me a clue:
- This patch is not merged into the netdev tree as included in -mm and
From: Christoph Hellwig <[EMAIL PROTECTED]>
Date: Sat, 31 Mar 2007 15:15:22 +0200
> Currently all avr32 and sparc64 don't support kretprobes unlike all
> other kprobes supporting architectures. This is not nice from the
> user interface point of view and from the ugly ifdefs point of view.
> Is
Hi,
here's more...
BUG: unable to handle kernel NULL pointer dereference at virtual address
printing eip:
*pde =
Oops: [#1]
Modules linked in: binfmt_misc sit nfs lockd nfs_acl sunrpc ipt_ECN
iptable_mangle w83627ehf i2c_isa i2c_viapro i2c_core via_agp agpgart
On Fri, 2007-03-30 at 15:21 -0700, Ed Lin wrote:
> After reset completed, the scsi error handler sends out START_STOP
> and TEST_UNIT_READY to the device. For 'normal' devices these
> commands will be handled by firmware. However, because the RAID
> console only interfaces to scsi mid layer, the
On 03/31/2007 08:47 AM, Jens Axboe wrote:
Try this.
diff --git a/drivers/cdrom/mcdx.c b/drivers/cdrom/mcdx.c
index f574962..7086313 100644
--- a/drivers/cdrom/mcdx.c
+++ b/drivers/cdrom/mcdx.c
@@ -577,6 +577,11 @@ static void do_mcdx_request(request_queue_t * q)
if (!req)
( please remove obsolute [EMAIL PROTECTED] from further messages!! )
On Saturday 31 March 2007 10:02 am, Ingo Molnar wrote:
>
> i dont think there's any particular problem here because suspend/resume
> wont be done during bootup - but we might need a way to move a device to
> earlier spots in
This email lists some known regressions in Linus' tree compared to 2.6.20
with patches available.
If you find your name in the Cc header, you are either submitter of one
of the bugs, maintainer of an affectected subsystem or driver, a patch
of you caused a breakage or I'm considering you in any
On Sat, 2007-03-31 at 19:17 +0200, Ingo Molnar wrote:
> yeah. There's some practical problems that need to be sorted out: much
> of the current GTOD code is irq-driven (and all GTOD locks are
> irq-safe), while the sysfs code needs to run in process-context level.
>
> Clocksources 'arrive'
On Saturday 31 March 2007 9:53 am, Linus Torvalds wrote:
>
> On Sat, 31 Mar 2007, Thomas Gleixner wrote:
> >
> > Right, but clock - sources/events need to be extremly late suspended and
> > early resumed. How can we ensure this ?
>
> Make them be at the top of the device tree by adding them
On Sat, 31 Mar 2007 10:07:43 -0700 Greg KH <[EMAIL PROTECTED]> wrote:
> On Fri, Mar 30, 2007 at 02:15:24PM -0700, Andrew Morton wrote:
> > On Fri, 30 Mar 2007 02:25:37 -0700
> > "Ken Chen" <[EMAIL PROTECTED]> wrote:
> >
> > > -module_param(max_loop, int, 0);
> > > -MODULE_PARM_DESC(max_loop,
* Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Umm.. WHy not make the device tree look like this:
>
> -- "clocksource" -- +-- HPET
> |
> +-- TSC
> |
> +-- i8259
>
On Sat, 31 Mar 2007, Maxim Levitsky wrote:
>
> So maybe I was right afrer all,
> Maybe it is better to add a suspend/resume hook to each clock source and call
> it from timekeeping_resume() ?
Umm.. WHy not make the device tree look like this:
-- "clocksource" -- +-- HPET
On Sat, Mar 31, 2007 at 09:53:43AM -0700, Linus Torvalds wrote:
> Make them be at the top of the device tree by adding them early. That's
> the whole point of the device tree after all - we have an ordering that is
> enforced by its topology, and that we sort by when things were added.
>
>
1 - 100 of 402 matches
Mail list logo
