On Tue, 12 Feb 2008, Roland Dreier wrote:
> I don't know anything about the T3 internals, but it's not clear that
> you could do this without a new chip design in general. Lot's of RDMA
> devices were designed expecting that when a packet arrives, the HW can
> look up the bus address for a given
On Tue, 12 Feb 2008, Paul Jackson wrote:
> I tend to agree with Lee on this one. If I recall correctly, Christoph
> said something similar, regarding the change of the 'policy' field
> of struct mempolicy from a short to an enum.
>
I've already made the change in my patchset as a result of
On Tue, Feb 12, 2008 at 05:01:17PM -0800, Christoph Lameter wrote:
> On Tue, 12 Feb 2008, Jason Gunthorpe wrote:
>
> > Well, certainly today the memfree IB devices store the page tables in
> > host memory so they are already designed to hang onto packets during
> > the page lookup over PCIE,
From: Stephen Hemminger <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 16:50:46 -0800
> All the users of hlist_for_each_entry_continue had to intialize pos
> before use; change API so pos is a pure temporary variable which matches
> the usage of other _for_each_entry routines.
>
> Signed-off-by:
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 16:53:50 -0800 (PST)
> The fact is, that "outlying code" is where we have all the bulk of the
> code, and it's also where we have all those developers who aren't on the
> "inside track". So we should help the outliers, not the core
On Tue, 12 Feb 2008, Greg KH wrote:
>
> Perhaps you need to switch to using quilt. This is the main reason why
> I use it.
Btw, on that note: if some quilt user can send an "annotated history file"
of their quilt usage, it's something that git really can do, and I'll see
if I can merge (or
On Tue, Feb 12, 2008 at 11:37:14PM +0100, Tomasz Chmielewski wrote:
> Wagner Ferenc wrote:
>
> >which are the "currently active Linux kernel versions" at any point in
> >time? The quote is taken from http://lkml.org/lkml/2008/2/11/29.
> >Or more precisely: which are the "stable" versions I can
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 12:07:07 -0800 (PST)
>
>
> On Tue, 12 Feb 2008, J. Bruce Fields wrote:
> >
> > But the "author" is still preserved, right? Why do you need the
> > committer name to be preserved? (I'm not denying that there could be
> > reasons,
On Tue, 12 Feb 2008 16:41:49 -0800 (PST)
David Miller <[EMAIL PROTECTED]> wrote:
> Here are some odd-the-cuff
> suggestions:
>
> 1) Make feature-removal-schedule a directory with files in it.
>Everyone touches that file, creating merge issues.
>
> 2) Let's move away from
On Tue, 12 Feb 2008, Andrew Morton wrote:
>
> So it would not be efficient for David to do all this queue-cleaning
> *prior* to putting the tree into linux-next, because more stuff will pop up
> anyway.
Well, what others have done is to have special "temporary branches".
This is what git
On Tue, 12 Feb 2008, Christian Bell wrote:
> I think there are very potential clients of the interface when an
> optimistic approach is used. Part of the trick, however, has to do
> with being able to re-start transfers instead of buffering the data
> or making guarantees about delivery that
From: Linus Torvalds <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 16:49:46 -0800 (PST)
> Btw, on that note: if some quilt user can send an "annotated history file"
> of their quilt usage, it's something that git really can do, and I'll see
> if I can merge (or rather, coax Junio to merge) the
On Tue, 12 Feb 2008, David Miller wrote:
>
> At 1500 changesets, a merge conflict shows up about once
> every day or two as 2.6.N nears it's release into final
> as bug fixes trickle in.
>
> I find using GIT to fixup merge errors on a tree of that
> scale to be really painful. And it only
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 16:47:26 -0800
> My usual way of fixing these things when they pop up is to just move
> the offending addition to some random position other than
> end-of-list. I must have done this hundreds of times and as yet I
> don't think
On 13-02-08 00:42, Jan Engelhardt wrote:
x86 MSDOS partition table layout starts counting with sector 1, which is
(not so intuitively) starting at 0x7e00 (and there's no sector 0,
probably for safety). Well, each ptable format with its own quirks.
I haven't followed this thread, but in case
On Tue, 12 Feb 2008 15:58:53 -0800 (PST)
David Miller <[EMAIL PROTECTED]> wrote:
> But right now I have to redo the include/linux/rcupdate.h that's in
> there because it has a bug.
Well there's a case in point. rcupdate.h is not a part of networking, and
it is random tree-wandering like this
neat. applied...
--
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/
Lee wrote:
> Why not leave it as an int. Will simplify this and subsequent patch.
I tend to agree with Lee on this one. If I recall correctly, Christoph
said something similar, regarding the change of the 'policy' field
of struct mempolicy from a short to an enum.
I'm inclined toward the
On Tue, Feb 12, 2008 at 04:37:54PM -0500, Mike Snitzer wrote:
> On Feb 12, 2008 4:18 PM, Ferenc Wagner <[EMAIL PROTECTED]> wrote:
> > Xavier Bestel <[EMAIL PROTECTED]> writes:
> >
> > > On mar, 2008-02-12 at 21:27 +0100, Wagner Ferenc wrote:
> > >
> > >> which are the "currently active Linux
Mike Frysinger wrote:
The warning issued by fs/binfmt_flat.c when the format handler is given a
non-FLAT and non-script executable is annoying to say the least when working
with FDPIC ELF objects. If you build a kernel that supports both FLAT and
FDPIC ELFs on no-mmu, every time you execute an
On Tue, Feb 12, 2008 at 04:15:06PM -0800, Greg KH wrote:
> Hi,
>
> I'm reworking the pci device list logic (we currently keep all PCI
> devices in 2 lists, which isn't the nicest, we should be able to get
> away with only 1 list.)
>
> The only bother I've found so far is the
Hi,
I'm reworking the pci device list logic (we currently keep all PCI
devices in 2 lists, which isn't the nicest, we should be able to get
away with only 1 list.)
The only bother I've found so far is the pci_get_device_reverse()
function, it's used in 2 places, IDE and the calgary driver.
I'm
On Tue, 12 Feb 2008, Paul Jackson wrote:
> I'm inclined toward the original types for the 'policy' field.
Good. And remove the enum.
> Specifically, I'd suggest adding the one line for 'mode_f_static_nodes'
> as below, and leaving the code involving the encoding of the policy
> field alone.
>
David Miller wrote:
From: Chris Mason <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 09:08:59 -0500
I've had requests to move the super down to 64k to make room for
bootloaders, which may not matter for sparc, but I don't really plan
on different locations for different arches.
The Sun disk
On Sat, 2008-02-09 at 19:39 +0100, Thomas Meyer wrote:
> H. Peter Anvin schrieb:
> > Thomas Meyer wrote:
> >> H. Peter Anvin schrieb:
> >>> Thomas Meyer wrote:
>
> I can not revert the commit
> e429795c68d3001ecae74f6465420c9f043b0ece. it gave me errors.
> but i'm also not
On Tue, 12 Feb 2008 17:57:19 -0800 (PST) Linus Torvalds <[EMAIL PROTECTED]>
wrote:
> - and you actually can help fix your issues by doing some simple things
>*before* pushing out, rather than push out immediately. IOW, do your
>whitespace sanity fixes, your compile checks etc early,
Goofed on last change, should avoid barrier only on rcu_assign_pointer(p, NULL)
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
---
include/linux/rcupdate.h | 13 +++--
1 files changed, 7 insertions(+), 6 deletions(-)
--- a/include/linux/rcupdate.h 2008-02-12 14:46:49.0
On Tue, 12 Feb 2008, Jason Gunthorpe wrote:
> Well, certainly today the memfree IB devices store the page tables in
> host memory so they are already designed to hang onto packets during
> the page lookup over PCIE, adding in faulting makes this time
> larger.
You really do not need a page table
On Tue, 12 Feb 2008, Lee Schermerhorn wrote:
> PATCH mempolicy - consolidate mpol_new() error paths
>
> Use common error path in mpol_new() for errors that we discover
> after allocation the new mempolicy structure. Free the mempolicy
> in the common error path.
>
> Signed-off-by: Lee
Hi all...
Here's my idea: what if we collaborate to extend and make the kernel
documentation better? I have done (slow) start by editing profile=
kernel param. It's not accepted by Adrian Bunk, but at least I did it.
Feedback?
regards,
Mulyadi.
--
To unsubscribe from this list: send the line
On Fri, 08 Feb 2008 18:57:42 +0900
Magnus Damm <[EMAIL PROTECTED]> wrote:
> smdev = kzalloc(sizeof(struct sm501_device) +
> - sizeof(struct resource) * res_count, GFP_KERNEL);
> + (sizeof(struct resource) * res_count) +
> +
On Wed 2008-02-13 00:32:16, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <[EMAIL PROTECTED]>
>
> The _WAK global ACPI control method has to be called with the
> argument representing the sleep state being exited. Make it happen.
>
> Special thanks to Mirco Tischler <[EMAIL PROTECTED]> for
On Feb 12 2008 15:38, David Miller wrote:
>
>> I still don't like the idea of btrfs trying to be smarter than a user
>> who can partition up his system according to
>> (a) his likes
>> (b) system or hardware requirements or recommendations
>> to align the superblock to a specific
* Mathieu Desnoyers ([EMAIL PROTECTED]) wrote:
> * Andrew Morton ([EMAIL PROTECTED]) wrote:
> >
> > fyi, I have this on hold because I spotted spufs build breakage,
> > but I haven't had time to investigate. powerpc allmodconfig, iirc.
>
> Christoph told me he would update his sputrace
Please cc on any replies, thanks.
---
When reboot_32.c and reboot_64.c were unified (commit 4d022e35fd...),
the machine_ops code was broken, leading to xen pvops kernels failing
to properly halt/poweroff/reboot etc. This fixes that up.
Signed-off-by: Jody Belka <[EMAIL PROTECTED]>
---
On Tue, 12 Feb 2008, Christoph Lameter wrote:
> On Tue, 12 Feb 2008, Jason Gunthorpe wrote:
>
> > Well, certainly today the memfree IB devices store the page tables in
> > host memory so they are already designed to hang onto packets during
> > the page lookup over PCIE, adding in faulting makes
> -Original Message-
> From: Marcin Slusarz [mailto:[EMAIL PROTECTED]
> Sent: Sunday, February 10, 2008 2:06 AM
> To: [EMAIL PROTECTED]; Linux Driver
> Cc: LKML
> Subject: [PATCH resend] qla3xxx: convert byte order of
> constant instead ofvariable
>
> convert byte order of constant
From: Chris Mason <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 09:35:20 -0500
> From my point of view, 0 is a bad idea because it is very likely to
> conflict with other things.
Starting at 0 is a bad idea because otherwise you'll waste
significant chunks of your disk on Sparc because of reasons
On Wednesday, 13 of February 2008, Mirco Tischler wrote:
>
> Am Dienstag, den 12.02.2008, 23:18 +0100 schrieb Rafael J. Wysocki:
> > Ouch. I think I know what the problem is.
> >
> > On top of this patch, please apply the appended one and retest.
> >
> > Thanks,
> > Rafael
> >
> > ---
> >
On Tue, Feb 12, 2008 at 11:01:32PM +, Alan Cox wrote:
> > Hrm... How badly is pl2303 broken? I actually use that sucker, so if
> > it needs help - count me in.
>
> 2303 is pretty good (in fact by usb serial standards outstanding). It has
> all the internal locking needed for now and right
On Tue, 2008-02-12 at 15:03 -0800, Badari Pulavarty wrote:
> Here is the version with your suggestion. Do you like this better ?
I do like how it looks, better, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
Am Dienstag, den 12.02.2008, 23:18 +0100 schrieb Rafael J. Wysocki:
> Ouch. I think I know what the problem is.
>
> On top of this patch, please apply the appended one and retest.
>
> Thanks,
> Rafael
>
> ---
> drivers/acpi/hardware/hwsleep.c |1 +
> 1 file changed, 1 insertion(+)
>
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:general-
> [EMAIL PROTECTED] On Behalf Of Roland Dreier
> Sent: Tuesday, February 12, 2008 2:42 PM
> To: Christoph Lameter
> Cc: Rik van Riel; [EMAIL PROTECTED]; Andrea Arcangeli;
> [EMAIL PROTECTED]; [EMAIL PROTECTED]; linux-
>
From: Jan Engelhardt <[EMAIL PROTECTED]>
Date: Tue, 12 Feb 2008 15:00:20 +0100 (CET)
> Something looks wrong here. Why would btrfs need to zero at all?
So that existing superblocks on the partition won't
be interpreted as correct by other filesystems. It's
a safety measure many mkfs programs
Am Dienstag, den 12.02.2008, 09:37 -0500 schrieb Martin K. Petersen:
> Brown paper bag time. My devel board has a 16MB 1st generation
> compact flash on the secondary so I never noticed this was hosed.
> Please try the following patch...
boots! For some reason, i had to apply it by hand (to
> Hrm... How badly is pl2303 broken? I actually use that sucker, so if
> it needs help - count me in.
2303 is pretty good (in fact by usb serial standards outstanding). It has
all the internal locking needed for now and right down to killing
lock_kernel entirely outside of open/close (which is
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
little_endian_variable = cpu_to_leX(leX_to_cpu(little_endian_variable) +
expression_in_cpu_byteorder);
with:
leX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
little_endian_variable = cpu_to_leX(leX_to_cpu(little_endian_variable) +
expression_in_cpu_byteorder);
with:
leX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic
On Tue, 12 Feb 2008 14:55:31 -0800
Greg KH <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 12, 2008 at 10:20:44PM +, Alan Cox wrote:
> > > I think the best way to get the serial drivers maintained would be to cat
> > > them all onto the end of synclink.c and hope that Paul thinks he did it.
> >
> >
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
little_endian_variable = cpu_to_leX(leX_to_cpu(little_endian_variable) +
expression_in_cpu_byteorder);
with:
leX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
big_endian_variable = cpu_to_beX(beX_to_cpu(big_endian_variable) +
expression_in_cpu_byteorder);
with:
beX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic patch
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
big_endian_variable = cpu_to_beX(beX_to_cpu(big_endian_variable) +
expression_in_cpu_byteorder);
with:
beX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic patch
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
big_endian_variable = cpu_to_beX(beX_to_cpu(big_endian_variable) +
expression_in_cpu_byteorder);
with:
beX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic patch
From: Marcin Slusarz <[EMAIL PROTECTED]>
replace all:
big_endian_variable = cpu_to_beX(beX_to_cpu(big_endian_variable) +
expression_in_cpu_byteorder);
with:
beX_add_cpu(_endian_variable, expression_in_cpu_byteorder);
generated with semantic patch
From: Marcin Slusarz <[EMAIL PROTECTED]>
Hi
This patchset converts
big/little_endian_variable =
cpu_to_[bl]eX([bl]eX_to_cpu(big/little_endian_variable) +
expression_in_cpu_byteorder);
to:
[bl]eX_add_cpu(/little_endian_variable,
Two pairs of parenthesis were missing around the result cast of cmpxchg64 and
cmpxchg64_local. This is a rather stupid mistake in
"Cast cmpxchg and cmpxchg_local result for 386 and 486". My bad. This fix
should be folded with the previous.
Sorry for this trivial bug which should have never
On Sun, 10 Feb 2008 00:24:28 +0900
"KOSAKI Motohiro" <[EMAIL PROTECTED]> wrote:
> the notification point to happen whenever the VM moves an
> anonymous page to the inactive list - this is a pretty good indication
> that there are unused anonymous pages present which will be very likely
> swapped
Hi,
Mark Brown wrote:
> This patch series adds support for the touchscreen controllers provided
> by Wolfson Microelectronics WM97xx series chips in both polled and
> streaming modes.
You used platform_device_register, but should be using platform_device_add,
otherwise you get barfs with
On Tuesday, 12 of February 2008, [EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=9944
>
>
> > Distribution: Debian Sid
> > Hardware Environment: Thinkpad T61
> > Software Environment:
> > Problem Description:
> >
> > Suspend to ram doesn't work anymore on my thinkpad t61
On Feb 12, 2008 3:13 PM, Haavard Skinnemoen <[EMAIL PROTECTED]> wrote:
> On Tue, 12 Feb 2008 14:43:30 -0600
> Olof Johansson <[EMAIL PROTECTED]> wrote:
>
> > > - depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
> > > + depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X
On Tue, Feb 12, 2008 at 02:04:30PM -0800, Andrew Morton wrote:
> On Sun, 10 Feb 2008 17:00:31 +0300
> Alexey Dobriyan <[EMAIL PROTECTED]> wrote:
>
> > This happened during LTP. FWIW, modprobe/rmmod trivial empty module
> > together with cat /proc/*/wchan and cat /proc/modules were also running.
>
Alan D. Brunelle wrote:
>
> Hopefully, the first column is self-explanatory - these are the settings
> applied to the queue_affinity, completion_affinity and rq_affinity tunables.
> Due to the fact that the standard deviations are so large coupled with the
> very close average results, I'm
Peter Zijlstra wrote:
> On Mon, 2008-02-11 at 13:44 -0800, Hiroshi Shimamoto wrote:
>> Hi Ingo,
>>
>> I think an interface to access RLIMIT_RTTIME from outside is useful.
>> It makes administrator able to set RLIMIT_RTTIME watchdog to existing
>> real-time applications without impact.
>>
>> I
H. Peter Anvin wrote:
> The USEC_TO_HZ and HZ_TO_USEC constant sets were mislabelled, with
> seriously incorrect results. This among other things manifested
> itself as cpufreq not working when a tickless kernel was configured.
>
> Signed-off-by: H. Peter Anvin <[EMAIL PROTECTED]>
Tested-by:
On Tuesday, 12 of February 2008, Mirco Tischler wrote:
>
> Am Dienstag, den 12.02.2008, 01:13 +0100 schrieb Rafael J. Wysocki:
> > Since _GTS and _BFS don't seem to be defined in your box's BIOS, please
> > try to apply the appended patch on top of the revert and see if that breaks
> > things
On Tue, 12 Feb 2008 21:51:52 +
Alan Cox <[EMAIL PROTECTED]> wrote:
> > We could simply decide that API changes affecting more than one subsystem
> > Must Be Serialized(tm). Explicitly. As in "any such change is posted
>
> Welcome to dreamland. The only way I can get serial changes done is
On Tue, 2008-02-12 at 14:07 -0800, Badari Pulavarty wrote:
> On Tue, 2008-02-12 at 13:57 -0800, Dave Hansen wrote:
> > On Tue, 2008-02-12 at 13:56 -0800, Badari Pulavarty wrote:
> > >
> > > +static void __remove_section(struct zone *zone, unsigned long
> > > section_nr)
> > > +{
> > > + if
On Tue, 12 Feb 2008 14:43:30 -0600
Olof Johansson <[EMAIL PROTECTED]> wrote:
> > - depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
> > + depends on (PCI && X86) || ARCH_IOP32X || ARCH_IOP33X || ARCH_IOP13XX
> > || AVR32
>
> This is a slippery slope. Things should be
When Willy go in 2.6.22.y, then I help it, so far as I 'm possible.
On 2/12/08, Mike Snitzer <[EMAIL PROTECTED]> wrote:
> On Feb 12, 2008 4:18 PM, Ferenc Wagner <[EMAIL PROTECTED]> wrote:
> > Xavier Bestel <[EMAIL PROTECTED]> writes:
> >
> > > On mar, 2008-02-12 at 21:27 +0100, Wagner Ferenc
On Tue, 12 Feb 2008, Steve Wise wrote:
> Chelsio's T3 HW doesn't support this.
Not so far I guess but it could be equipped with these features right?
Having the VM manage the memory area for Infiniband allows more reliable
system operations and enables the sharing of large memory areas via
RDMA/cxgb3: Fail loopback connections.
The cxgb3 HW and driver don't support loopback RDMA connections. So fail
any connection attempt where the destination address is local.
Signed-off-by: Steve Wise <[EMAIL PROTECTED]>
---
drivers/infiniband/hw/cxgb3/iwch_cm.c | 16
1
Back on the 32-way, in this set of tests we're running 12 disks spread out
through the 8 cells of the 32-way. Each disk will have an Ext2 FS placed on it,
a clean Linux kernel source untar()ed onto it, then a full make (-j4) and then
a make clean performed. The 12 series are done in parallel -
On Tue, 2008-02-12 at 13:56 -0800, Badari Pulavarty wrote:
> > > + /*
> > > +* Its ugly, but this is the best I can do - HELP !!
> > > +* We don't know where the allocations for section memmap and usemap
> > > +* came from. If they are allocated at the boot time, they would come
> >
Am Dienstag, den 12.02.2008, 01:13 +0100 schrieb Rafael J. Wysocki:
> Since _GTS and _BFS don't seem to be defined in your box's BIOS, please
> try to apply the appended patch on top of the revert and see if that breaks
> things again.
>
> Thanks,
> Rafael
>
> ---
>
On Tuesday 12 February 2008, David Miller wrote:
> From: Chris Mason <[EMAIL PROTECTED]>
> Date: Wed, 6 Feb 2008 12:00:13 -0500
>
> > So, here's v0.12.
>
> Any page size larger than 4K will not work with btrfs. All of the
> extent stuff assumes that PAGE_SIZE <= sectorsize.
Yeah, there is
On Tue, 2008-02-12 at 13:57 -0800, Dave Hansen wrote:
> On Tue, 2008-02-12 at 13:56 -0800, Badari Pulavarty wrote:
> >
> > +static void __remove_section(struct zone *zone, unsigned long
> > section_nr)
> > +{
> > + if (!valid_section_nr(section_nr))
> > + return;
> > +
> > +
The USEC_TO_HZ and HZ_TO_USEC constant sets were mislabelled, with
seriously incorrect results. This among other things manifested
itself as cpufreq not working when a tickless kernel was configured.
Signed-off-by: H. Peter Anvin <[EMAIL PROTECTED]>
---
kernel/timeconst.pl |2 +-
1 files
Roland Dreier wrote:
[Adding [EMAIL PROTECTED] to get the IB/RDMA people involved]
This thread has patches that add support for notifying drivers when a
process's memory map changes. The hope is that this is useful for
letting RDMA devices handle registered memory without pinning the
On Tue, 12 Feb 2008, J. Bruce Fields wrote:
> > So as a result, some *random* commit that was actually fine on its own has
> > now become a bug, just because it was re-written.
>
> If there was a "fundamental thing that didn't cause a conflict", then
> the two trees in question probably
maximilian attems wrote:
On Tue, Feb 12, 2008 at 01:14:04PM -0800, H. Peter Anvin wrote:
Are you sure that build matches the bug report?
urrgs right sorry, the posted vmlinux is a newer
2.6.24-git22 and not Version: 2.6.24-3
The EIP given falls inside the .data segment of that kernel,
On Tuesday 12 February 2008, Benjamin Herrenschmidt wrote:
>
> On Fri, 2008-02-08 at 19:40 +1100, Benjamin Herrenschmidt wrote:
> > On Fri, 2008-02-08 at 01:44 +0100, Bartlomiej Zolnierkiewicz wrote:
> > > - couple of fixes and preparatory patches
> > >
> > > - rework of PowerMac media-bay
On Tue, Feb 12, 2008 at 10:30:04AM -0800, Linus Torvalds wrote:
>
>
> On Tue, 12 Feb 2008, Jeff Garzik wrote:
>
> > Greg KH wrote:
> > > The work I'm doing here is for stupid PCI firmware engineers, who have
> > > created devices that are different things, all bound up under the same
> > > PCI
On Feb 12, 2008 4:18 PM, Ferenc Wagner <[EMAIL PROTECTED]> wrote:
> Xavier Bestel <[EMAIL PROTECTED]> writes:
>
> > On mar, 2008-02-12 at 21:27 +0100, Wagner Ferenc wrote:
> >
> >> which are the "currently active Linux kernel versions" at any point in
> >> time? The quote is taken from
On Tue, 12 Feb 2008, Greg KH wrote:
>
> Yes, I agree, there are lots of examples of this, but the overall
> majority are reviewed by 2 people at least (or sure as hell should be,
> maybe we need to bring into existance the "reviewed-by" marking to
> ensure this.)
Well, I don't really "review"
Andrew Morton wrote:
On Tue, 12 Feb 2008 11:44:52 -0500
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
On Mon, Feb 11, 2008 at 04:14:52PM +0530, Ananth N Mavinakayanahalli wrote:
The following series of patches create and populate the toplevel tests/
directory. This will henceforth be the place
On the day of Tuesday 12 February 2008 Krzysztof Halasa hast written:
> Hi,
>
> Is it a known problem?
> Linux 2.6.24.2, ASUS M2NPV-MX mobo, nforce 430 based, two PCI-E x1
> E1000 cards, 32-bit kernel, default e1000 driver (PCI IDs disabled in
> e1000e).
>
> Don't work by default. "pci=nomsi"
Linda Walsh wrote:
>
> David Chinner wrote:
>> Filesystem bugs rarely hang systems hard like that - more likely is
>> a hardware or driver problem. And neither of the lockdep reports
>> below are likely to be responsible for a system wide, no-response
>> hang.
> ---
> "Ish", the 32-bitter,
Hi,
Is it a known problem?
Linux 2.6.24.2, ASUS M2NPV-MX mobo, nforce 430 based, two PCI-E x1
E1000 cards, 32-bit kernel, default e1000 driver (PCI IDs disabled in
e1000e).
Don't work by default. "pci=nomsi" fixes the problem.
82572EI Gigabit Ethernet Controller (Copper) (rev 06)
Subsystem:
On Tuesday 12 February 2008, Borislav Petkov wrote:
> commit 272976f0f5754707f9e41da315717a6eb8d9d536
> Author: Borislav Petkov <[EMAIL PROTECTED]>
> Date: Tue Feb 12 16:22:44 2008 +0100
>
> ide-scsi: do non-atomic pc->flags testing
>
> Signed-off-by: Borislav Petkov <[EMAIL
On Tuesday 12 February 2008, Borislav Petkov wrote:
> commit 48f9b88d491aa478ffcf21e2f523e3665db0770b
> Author: Borislav Petkov <[EMAIL PROTECTED]>
> Date: Tue Feb 12 09:42:19 2008 +0100
>
> ide-floppy: rename end_request handler properly
>
> mv idefloppy_do_end_request ->
On Tue, Feb 12, 2008 at 01:14:04PM -0800, H. Peter Anvin wrote:
>
> Are you sure that build matches the bug report?
urrgs right sorry, the posted vmlinux is a newer
2.6.24-git22 and not Version: 2.6.24-3
> The EIP given falls inside the .data segment of that kernel,
> specifically inside
On Tue, 2008-02-12 at 21:41 +, Alan Cox wrote:
> On Wed, 13 Feb 2008 08:04:07 +1100
> Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote:
>
> >
> > On Fri, 2008-02-08 at 19:40 +1100, Benjamin Herrenschmidt wrote:
> > > On Fri, 2008-02-08 at 01:44 +0100, Bartlomiej Zolnierkiewicz wrote:
> > >
On Tue, Feb 12, 2008 at 01:02:05PM -0800, Linda Walsh wrote:
> David Chinner wrote:
> >Perhaps by running xfs_fsr manually you could reproduce the
> >problem while you are sitting in front of the machine...
>
> Um...yeah, AND with multiple "cp's of multi-gig files
> going on at same
On Tue, 2008-02-12 at 13:56 -0800, Badari Pulavarty wrote:
>
> +static void __remove_section(struct zone *zone, unsigned long
> section_nr)
> +{
> + if (!valid_section_nr(section_nr))
> + return;
> +
> + unregister_memory_section(__nr_to_section(section_nr));
> +
On Mon, 11 Feb 2008 16:28:13 -0600
Olof Johansson <[EMAIL PROTECTED]> wrote:
> I noticed this when looking at an openswan issue. Openswan (ab?)uses
> the tasklet API to defer processing of packets in some situations,
> with one packet per tasklet_action(). I started noticing sequences of
>
From: Paul Menage <[EMAIL PROTECTED]>
Add a new mount() flag, MS_BIND_FLAGS.
MS_BIND_FLAGS indicates that a bind mount should take its per-mount flags
from the arguments passed to mount() rather than from the source
mountpoint.
This flag allows you to create a bind mount with the desired
Xavier Bestel <[EMAIL PROTECTED]> writes:
> On mar, 2008-02-12 at 21:27 +0100, Wagner Ferenc wrote:
>
>> which are the "currently active Linux kernel versions" at any point in
>> time? The quote is taken from http://lkml.org/lkml/2008/2/11/29.
>> Or more precisely: which are the "stable"
maximilian attems wrote:
On Tue, Feb 12, 2008 at 12:32:27PM -0800, H. Peter Anvin wrote:
INT 6 is #UD, undefined instruction.
If you could send me a copy of your vmlinux file (not bzImage), it would
speed things up.
cp -l src/linux-2.6-2.6.24/debian/build/build_i386_none_686/vmlinux
On 2/13/08, Randy Dunlap <[EMAIL PROTECTED]> wrote:
> On Wed, 13 Feb 2008 09:08:12 +0700 Mulyadi Santosa wrote:
>
> > Hi all...
> >
> > Here's my idea: what if we collaborate to extend and make the kernel
> > documentation better? I have done (slow) start by editing profile=
> > kernel param. It's
Steven Rostedt wrote:
> On Tue, 12 Feb 2008, Peter Zijlstra wrote:
>>> Rusty - Stop machine.
>>>After doing a bunch of testing last three days I actually downgraded
>>> stop machine
>>>changes from [highly experimental] to simply [experimental]. Pleas see
>>> this thread
>>>for
901 - 1000 of 1349 matches
Mail list logo
