Am Wed, 07 Nov 2007 11:07:07 -0500
schrieb Mark Lord <[EMAIL PROTECTED]>:
> My ASUS board has one of these:
>
> 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 01)
> Subsystem: ASUSTeK Computer Inc. Unknown device 81aa Cont
Andrew Morton wrote:
> > > I would suggest getting a 'tcpdump -s0' trace and seeing (with
> > > wireshark) what is different between the various cases.
> >
> > Thanks Neil for looking into this. Your suggestion has already been
> > answered in a previous post, where the difference has been attribu
On Nov 2, 2007, at 9:28 AM, Kumar Gala wrote:
On Thu, 25 Oct 2007, Trond Myklebust wrote:
Could you please try the following patch?
Cheers
Trond
Its a new month so I'll ping again about sending this fix upstream to
linus for 2.6.24 :) ?
- k
Trond,
any update on sending this to Linus
Does it work as kernel parameter?
I tried libata_dma_mask=0x4 and to set 0xf or 0xff - doesn't help. How to
disable DMA in libata, if it is compiled in kernel?
On Thu, 8 Nov 2007 01:30:53 +0100, Bartlomiej Zolnierkiewicz wrote
> On Thursday 08 November 2007, Denys Fedoryshchenko wrote:
> > 2.6.2
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 7 Nov 2007 23:09:16 -0800
> I don't think that's a big problem? This syscall can (oddly) return any
> 32-bit (64-bit) number and a smart application developer (after saying wtf)
> would realise that he just can't check for errors and have correct
> On Wed, 07 Nov 2007 22:25:30 -0800 (PST) David Miller <[EMAIL PROTECTED]>
> wrote:
> From: Andrew Morton <[EMAIL PROTECTED]>
> Date: Wed, 7 Nov 2007 21:20:05 -0800
>
> > Yup. But userspace will already have a fit if either the start or end time
> > advanced into the glibc-thought-that-was-an-e
[adding linux-kernel again]
werner wrote:
The compilation is ready. By any reason that list as suggested by you wasn't
generated.
However, the 3 compiling/linking lists what my kernel-build-script normally
generates,
were. They are annexed here. It's the same , after booting the kernel crashs
On Wed, Nov 07 2007, Roland Dreier wrote:
> > Well, I spent the last 36 hours (more or less) trying to bisect the SD
> > problem. The method I used was to insert the card, umount it, and make 8 dd
> > in a row; the kernel is "bad" if they differs, "good" if they are the
> same.
> >
> > I co
You are right, seems no dma lines in adapter. hda=nodma helped, no errors
anymore. I will try now also libata_dma_mask and will mail result. Btw there
is no notes in Documentation/kernel-parameters.txt about it.
In any case it is complete board, WRAP.2C made by PCEngines in 2003. Kind of
popula
On Thu, Nov 08 2007, Tejun Heo wrote:
> Greg KH wrote:
> > On Thu, Nov 08, 2007 at 11:27:16AM +0900, Tejun Heo wrote:
> >> pkt_setup_dev() expects module reference to be held on invocation.
> >> This used to be true for sysfs callbacks but not anymore. Test and
> >> grab module reference around pk
Greg KH wrote:
> On Thu, Nov 08, 2007 at 11:27:16AM +0900, Tejun Heo wrote:
>> pkt_setup_dev() expects module reference to be held on invocation.
>> This used to be true for sysfs callbacks but not anymore. Test and
>> grab module reference around pkt_setup_dev() in
>> class_pktcdvd_store_add().
>
At Wed, 7 Nov 2007 19:07:07 -0500 (EST),
Gerhard Mack wrote:
>
> On Wed, 7 Nov 2007, Andrew Morton wrote:
>
> > Date: Wed, 7 Nov 2007 15:21:27 -0800
> > From: Andrew Morton <[EMAIL PROTECTED]>
> > To: Gerhard Mack <[EMAIL PROTECTED]>
> > Cc: linux-kernel@vger.kernel.org, Jaroslav Kysela <[EMAIL P
Anthony Liguori wrote:
> This patch moves virtio under the virtualization menu and changes virtio
> devices to not claim to only be for lguest.
>
Perhaps the virt menu needs to be split into a host-side support menu
and guest-side support menu.
--
Do not meddle in the internals of kernels, fo
Gregory Haskins wrote:
>
>> PCI means that you can reuse all of the platform's infrastructure for
>> irq allocation, discovery, device hotplug, and management.
>>
>
> Its tempting to use, yes. However, most of that infrastructure is
> completely inappropriate for a PV implementation, IMHO.
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 7 Nov 2007 21:20:05 -0800
> Yup. But userspace will already have a fit if either the start or end time
> advanced into the glibc-thought-that-was-an-error range.
On x86 only. We could use force_successful_syscall_return()
to make sure the condi
From: Paul Mackerras <[EMAIL PROTECTED]>
Date: Thu, 8 Nov 2007 16:15:51 +1100
> David Miller writes:
>
> > I can't see where x86 is doing this though, so perhaps for x86
> > glibc does make the negative value check. But I doubt it is
> > checking the range 0x8000-0x, otherwise mmap()
From: Paul Mackerras <[EMAIL PROTECTED]>
Date: Thu, 8 Nov 2007 15:59:12 +1100
> Not on powerpc. On powerpc the error indication is carried separately
> in a condition register bit. So a force_successful_syscall_return()
> call will make glibc automatically do the right thing without any
> glibc
On Wed, 07 Nov 2007 23:56:57 +0100
ciol <[EMAIL PROTECTED]> wrote:
> Hi, I'd like to ask you a few questions:
>
> * Do you like the way linux distributions integrate the kernel?
>
> * Wouldn't you prefer they ship with the stable and still maintained
> 2.6.16.X, while providing optionally the l
Anthony Liguori wrote:
> This is a PCI device that implements a transport for virtio. It allows virtio
> devices to be used by QEMU based VMMs like KVM or Xen.
>
>
Didn't see support for dma. I think that with Amit's pvdma patches you
can support dma-capable devices as well without too much fu
> On Thu, 8 Nov 2007 16:36:08 +1100 Paul Mackerras <[EMAIL PROTECTED]> wrote:
> Andrew Morton writes:
>
> > Yup. But userspace will already have a fit if either the start or end time
> > advanced into the glibc-thought-that-was-an-error range.
>
> Not nearly as much of a fit. The effect on x86
On Wed, Nov 07, 2007 at 11:04:41AM -0800, Ray Lee wrote:
> On Nov 7, 2007 10:50 AM, Roel Kluin <[EMAIL PROTECTED]> wrote:
> > If count reaches zero, the loop ends, but the postfix decrement
> > still subtracts: testing for 'count == 0' will not work.
> >
> > Signed-off-by: Roel Kluin <[EMAIL PROT
On Wed, Nov 07, 2007 at 03:28:33PM -0800, Andrew Morton wrote:
On Wed, 7 Nov 2007 14:47:22 -0800 David Brown <[EMAIL PROTECTED]> wrote:
will return '-1' to user space and set the negated clock_t value to errno.
At minimum, perhaps it should return a sane errno value.
RETURN VALUE
time
On Wed, 07 Nov 2007 15:37:46 -0800
Roland Dreier <[EMAIL PROTECTED]> wrote:
>
> mmc: Fix sg helper copy-and-paste error
>
> Commit 45711f1a ("[SG] Update drivers to use sg helpers") had the
> following bogus change in drivers/mmc/card/queue.c:
>
> > - src_buf = page_ad
Andrew Morton writes:
> Yup. But userspace will already have a fit if either the start or end time
> advanced into the glibc-thought-that-was-an-error range.
Not nearly as much of a fit. The effect on x86 is that values between
-4095 and -1 are reported as -1, so the end-start difference will b
On Thu, Nov 08, 2007 at 11:27:16AM +0900, Tejun Heo wrote:
> pkt_setup_dev() expects module reference to be held on invocation.
> This used to be true for sysfs callbacks but not anymore. Test and
> grab module reference around pkt_setup_dev() in
> class_pktcdvd_store_add().
>
> Signed-off-by: Te
> On Thu, 8 Nov 2007 15:59:12 +1100 Paul Mackerras <[EMAIL PROTECTED]> wrote:
> Andrew Morton writes:
>
> > "the latter" is what my protopatch does isn't it? It wraps at 0x7fff.
> > It appears that glibc treats all of 0x8000-0x as an error.
>
> Not on powerpc. On powerpc the err
David Miller writes:
> I can't see where x86 is doing this though, so perhaps for x86
> glibc does make the negative value check. But I doubt it is
> checking the range 0x8000-0x, otherwise mmap() would
> be busted.
At least for the INTERNAL_SYSCALL macro in glibc, the error check is
On Wed, Nov 07, 2007 at 02:20:03PM -0500, Steven Rostedt wrote:
> >
> > Introduce a macro for suppressing gcc from generating a warning about a
> > probable uninitialized state of a variable.
> >
> > Example:
> >
> > - spinlock_t *ptl;
> > + spinlock_t *uninitialized_var(ptl);
> >
> > Not a
Andrew Morton writes:
> "the latter" is what my protopatch does isn't it? It wraps at 0x7fff.
> It appears that glibc treats all of 0x8000-0x as an error.
Not on powerpc. On powerpc the error indication is carried separately
in a condition register bit. So a force_successful_sy
Peter Zijlstra wrote:
> Bah, missed a hunk
>
> ---
> Subject: sched: avoid large irq-latencies in smp-balancing
>
> SMP balancing is done with IRQs disabled and can iterate the full rq. When rqs
> are large this can cause large irq-latencies. Limit the nr of iterations on
> each run.
>
> Signed-
On Wed, Nov 07, 2007 at 05:43:23PM +, David Howells wrote:
>
>
> These patches add the MEI/Panasonic MN10300/AM33 architecture to the Linux
> kernel.
>
> The first patch suppresses AOUT support in the kernel if CONFIG_BINFMT_AOUT=n
> and CONFIG_IA32_AOUT=n. MN10300 does not support the AOUT
On Wed, Nov 07, 2007 at 11:52:32PM +0100, Adrian Bunk wrote:
> On Wed, Nov 07, 2007 at 02:34:52PM -0800, David Brownell wrote:
> > > > But on the other hand, it seems that only the ASIX code will work
> > > > right; the DM9601 and MCS7830 Kconfig is different/wrong.
> > >
> > > I'm not seeing the
On Wed, Nov 07, 2007 at 06:53:48PM -0800, David Brownell wrote:
> On Wednesday 07 November 2007, Adrian Bunk wrote:
> > On Wed, Nov 07, 2007 at 02:34:52PM -0800, David Brownell wrote:
> > > > > But on the other hand, it seems that only the ASIX code will work
> > > > > right; the DM9601 and MCS7830
> On Thu, 08 Nov 2007 11:57:26 +0900 Tetsuo Handa <[EMAIL PROTECTED]> wrote:
> Original patch assumed args->nlen < CTL_MAXNAME, but it can be false.
>
> Signed-off-by: Tetsuo Handa <[EMAIL PROTECTED]>
>
>
> --- linux-2.6.22-rc2.orig/kernel/sysctl.c 2007-11-08 10:38:17.0
> +0900
> ++
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 7 Nov 2007 19:07:14 -0800
> It appears that glibc treats all of 0x8000-0x as an
> error.
glibc treats it as an error if the system call returns with
the carry condition code set. At least that's how I've
understood it to work and at
> On Thu, 8 Nov 2007 12:53:57 +1100 Paul Mackerras <[EMAIL PROTECTED]> wrote:
> Andrew Morton writes:
>
> > Given all this stuff, the return value from sys_times() doesn't seem a
> > particularly useful or reliable kernel interface.
>
> I think the best thing would be to ignore any error from cop
Original patch assumed args->nlen < CTL_MAXNAME, but it can be false.
Signed-off-by: Tetsuo Handa <[EMAIL PROTECTED]>
--- linux-2.6.22-rc2.orig/kernel/sysctl.c 2007-11-08 10:38:17.0
+0900
+++ linux-2.6.22-rc2/kernel/sysctl.c2007-11-08 11:24:27.0 +0900
@@ -2609,6 +2609,
On Wednesday 07 November 2007, Adrian Bunk wrote:
> On Wed, Nov 07, 2007 at 02:34:52PM -0800, David Brownell wrote:
> > > > But on the other hand, it seems that only the ASIX code will work
> > > > right; the DM9601 and MCS7830 Kconfig is different/wrong.
> > >
> > > I'm not seeing the problem.
>
On Thu, Nov 08, 2007 at 02:20:58AM +0100, Andi Kleen wrote:
>
> > But I think we'd be best off stashing a single bit somewhere and
> > checking it at migrate time (relatively infrequent) rather than
> > copying and zeroing out a potentially enormous affinity mask every
> > time we disable migratio
This is a PCI device that implements a transport for virtio. It allows virtio
devices to be used by QEMU based VMMs like KVM or Xen.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
index 9e33fc4..c81e0f3 100644
--- a/drivers/virtio/
This patch moves virtio under the virtualization menu and changes virtio
devices to not claim to only be for lguest.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/Kconfig b/drivers/Kconfig
index f4076d9..d945ffc 100644
--- a/drivers/Kconfig
+++ b/drivers/Kconfig
@@ -93,6
This is needed for the virtio PCI device to be compiled as a module.
Signed-off-by: Anthony Liguori <[EMAIL PROTECTED]>
diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
index 0e1bf05..3f28b47 100644
--- a/drivers/virtio/virtio_ring.c
+++ b/drivers/virtio/virtio_ring.c
@@ -
This patch series implements a PCI driver for virtio. This allows virtio
devices (like block and network) to be used in QEMU/KVM. I'll post a very
early KVM userspace backend in kvm-devel for those that are interested.
This series depends on the two virtio fixes I've posted and Rusty's config_op
Rusty Russell wrote:
On Thursday 08 November 2007 04:30:50 Anthony Liguori wrote:
I would prefer that the virtio API not expose a little endian standard.
I'm currently converting config->get() ops to ioreadXX depending on the
size which already does the endianness conversion for me so this just
All x86 modes and architectures have very similar pagetable
structures: the page flags, the accessors for testing/setting them,
and the combinations of page flags used for kernel and usermode
mappings are all the same. The main difference is between 32 and
64-bit pagetable entries, with the latter
Some code reformatting in init_32.c. No functional change.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/x86/mm/init_32.c | 31 +--
1 file changed, 21 insertions(+), 10 deletions(-)
NB: RFC ONLY. DO NOT APPLY.
This series unifies many definitions in asm-x86/pgtable.h and page.h.
Later in the series, I take advantage of some of the earlier
infrastructure to simplify paravirt.h and bits of the Xen code.
This patch applies on top of Glauber's 64-bit pvops unification, so it
wo
Fix up various pieces of unconventional formatting in
asm-x86/pgtable*.h. In some cases, the old formatting was arguablly
clearer with a wide enough terminal, but this patch gives the option
of using a more standard form.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
include/asm-x86
Simplify paravirt.h using the unified page/pgtable.h infrastructure.
This removes a fair amount of duplication of the ops function pointers
themselves, but also of PVOP_*CALL* wrappers.
The wrappers are complicated by the fact that on a 32-bit PAE system,
literal 64-bit values are passed in two ar
Unify common definitions in page*.h. To simplify other code, I added
typedefs for the value of pte/pmd/pud/pgd values, so they can be used
symbolically elsewhere without needing to have lots of 32/64/PAE
tests.
Also, add PAGETABLE_LEVELS define so that other definitions can test
for it directly r
Take advantage of the unified page/pgtable.h definitions to reduce the
number of duplicate definitions of the various Xen mmu_ops functions.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/x86/xen/enlighten.c |8 -
arch/x86/xen/mmu.c | 67 +-
It only has a single use, which can be trivially replaced.
Signed-off-by: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
---
arch/x86/mm/init_64.c|3 +--
include/asm-x86/pgtable_64.h |9 -
2 files changed, 1 insertion(+), 11 deletions(-)
On Thu, Nov 08, 2007 at 02:27:07AM +0530, Kamalesh Babulal wrote:
> Hi Andrew,
>
> The kernel build fails with randconfig, with following error
>
> CC arch/powerpc/platforms/celleb/setup.o
> arch/powerpc/platforms/celleb/setup.c:151: error: ‘generic_calibrate_decr’
> undeclared here (not
pkt_setup_dev() expects module reference to be held on invocation.
This used to be true for sysfs callbacks but not anymore. Test and
grab module reference around pkt_setup_dev() in
class_pktcdvd_store_add().
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Acked-by: Peter Osterlund <[EMAIL PROTECTED
On Thursday 08 November 2007 12:06:07 Anthony Liguori wrote:
> Rusty Russell wrote:
> > On Wednesday 07 November 2007 13:52:29 Anthony Liguori wrote:
> >> This patch fixes a typo in vring_init().
> >
> > Thanks, applied.
> >
> > I've put it in the new, experimental virtio git tree on git.kernel.org
On Thursday 08 November 2007 04:30:50 Anthony Liguori wrote:
> I would prefer that the virtio API not expose a little endian standard.
> I'm currently converting config->get() ops to ioreadXX depending on the
> size which already does the endianness conversion for me so this just
> messes things up
Some SH boards (old R2D-1 boards) have generally not had working CF
under libata, due to both buswidth issues (handled by Aoi Shinkai
in 43f4b8c7578b928892b6f01d374346ae14e5eb70), and buggy interrupt
controllers. For these sorts of boards simply disabling the IRQ and
polling ends up working fine.
By default ata_host_activate() expects a valid IRQ in order to
successfully register the host. This patch enables a special case
for registering polling-only hosts that either don't have IRQs
or have buggy IRQ generation (either in terms of handling or
sensing), which otherwise work fine.
Hosts th
On Wednesday 07 November 2007 21:01:30 Jan Glauber wrote:
> Hi Rusty,
>
> I've seen a symbol-resolving race on s390. The qeth module uses symbols
> from qdio and although the loading order seems correct and the qdio
> symbols should be available the following error appears:
>
> qdio: loading QDIO b
From: Paul Mackerras <[EMAIL PROTECTED]>
Date: Thu, 8 Nov 2007 12:53:57 +1100
> Andrew Morton writes:
>
> > Given all this stuff, the return value from sys_times() doesn't seem a
> > particularly useful or reliable kernel interface.
>
> I think the best thing would be to ignore any error from co
Andrew Morton writes:
> Given all this stuff, the return value from sys_times() doesn't seem a
> particularly useful or reliable kernel interface.
I think the best thing would be to ignore any error from copy_to_user
and always return the number of clock ticks. We should call
force_successful_sy
Denys wrote:
Finally i got full DMESG with 1GB card till end. Seems not readable too.
..
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata1.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 cdb 0x0 data 4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (t
On Wed, Nov 07, 2007 at 11:56:57PM +0100, ciol wrote:
> Hi, I'd like to ask you a few questions:
>
> * Do you like the way linux distributions integrate the kernel?
>
> * Wouldn't you prefer they ship with the stable and still maintained
> 2.6.16.X, while providing optionally the latest kernel for
> But I think we'd be best off stashing a single bit somewhere and
> checking it at migrate time (relatively infrequent) rather than
> copying and zeroing out a potentially enormous affinity mask every
> time we disable migration (often, and in fast paths). Perhaps adding
> TASK_PINNED to the task
On Wed, Nov 07, 2007 at 02:34:52PM -0800, David Brownell wrote:
> > > But on the other hand, it seems that only the ASIX code will work
> > > right; the DM9601 and MCS7830 Kconfig is different/wrong.
> >
> > I'm not seeing the problem.
> >
> > Which configuration will be handled wrongly?
>
> Not
> On Thu, 08 Nov 2007 01:54:40 +0100 Andreas Schwab <[EMAIL PROTECTED]> wrote:
> Andrew Morton <[EMAIL PROTECTED]> writes:
>
> > diff -puN kernel/compat.c~a kernel/compat.c
> > --- a/kernel/compat.c~a
> > +++ a/kernel/compat.c
> > @@ -162,7 +162,8 @@ asmlinkage long compat_sys_times(struct
> >
> On Wed, 07 Nov 2007 16:50:22 -0800 (PST) David Miller <[EMAIL PROTECTED]>
> wrote:
> From: Andrew Morton <[EMAIL PROTECTED]>
> Date: Wed, 7 Nov 2007 15:28:33 -0800
>
> > Perhaps this is a bug in glibc: it is interpreting the times() return value
> > in the same way as other syscalls.
>
> The p
On Wed, Nov 07, 2007 at 05:43:28PM +, David Howells wrote:
> Suppress A.OUT library support in ELF binfmt if CONFIG_BINFMT_AOUT is not set.
>
> Not all architectures support the A.OUT binfmt, so the ELF binfmt should not
> be permitted to go looking for A.OUT libraries to load in such a case.
This isn't a regression. It's an intentional default change.
The default console mode changed from 8-bit legacy to UTF-8 in 2.6.24.
Apparently this user is using a legacy character set (note that it's a
Slackware machine), and isn't explicitly setting the character set via
the appropriate esc
This message contains a list of some regressions from 2.6.23 which have been
reported since 2.6.24-rc1 was released and for which there are no fixes in the
mainline that I know of. If any of them have been fixed already, please let me
know.
If you know of any other unresolved regressions from 2.6
On Wed, 07 Nov 2007 21:32:43 -0300 (GFT) werner wrote:
> On 7/Nov/2007 20:10 werner wrote ..
> > With 2.6.23-rc2 is the same problem: it crashed at the beginning: EIP 060
> > c03fdea4
> > EFLAGS 00010212 EIP is at xor_sse_2+0x34/0x200
> > Again during the compilation was reclaimed that
> > /ar
On Thu, Nov 08, 2007 at 01:31:00AM +0100, Andi Kleen wrote:
> On Thursday 08 November 2007 01:20, Matt Mackall wrote:
> > On Wed, Nov 07, 2007 at 12:30:45PM -0800, Andrew Morton wrote:
> > > Ow. Yes, from my reading delay_tsc() can return early (or after
> > > heat-death-of-the-universe) if the TS
Rusty Russell wrote:
On Wednesday 07 November 2007 13:52:29 Anthony Liguori wrote:
This patch fixes a typo in vring_init().
Thanks, applied.
I've put it in the new, experimental virtio git tree on git.kernel.org.
Hrm, perhaps you forgot to push? I don't see it in the tree althou
Resend the patch for more people to review
On some single node x64 system with huge amount of physical memory e.g >
64G. the memmap size maybe very big.
If the memmap is allocated from low pages, it may occupies too much
memory below 4G.
then swiotlb could fail to reserve bounce buffer under 4G
Resend the patch for more people to review.
If __alloc_bootmem_core was given a goal, it will first try to allocate
memory above that goal. If failed, it will try from the low pages.
Sometimes we don't want this behavior, we want the goal to be strict.
This patch introduce a strict_goal paramete
Andrew Morton <[EMAIL PROTECTED]> writes:
> diff -puN kernel/compat.c~a kernel/compat.c
> --- a/kernel/compat.c~a
> +++ a/kernel/compat.c
> @@ -162,7 +162,8 @@ asmlinkage long compat_sys_times(struct
> if (copy_to_user(tbuf, &tmp, sizeof(tmp)))
> return -EFAULT
From: Andrew Morton <[EMAIL PROTECTED]>
Date: Wed, 7 Nov 2007 15:28:33 -0800
> Perhaps this is a bug in glibc: it is interpreting the times() return value
> in the same way as other syscalls.
The problem is more likely that we are failing to
invoke force_successful_syscall_return() here.
Otherwi
On Wed, Nov 07, 2007 at 08:15:06AM +0100, Torsten Kaiser wrote:
> On 11/7/07, David Chinner <[EMAIL PROTECTED]> wrote:
> > Ok, so it's not synchronous writes that we are doing - we're just
> > submitting bio's tagged as WRITE_SYNC to get the I/O issued quickly.
> > The "synchronous" nature appears
On Wednesday, 7 of November 2007, Romano Giannetti wrote:
>
> On Tue, 2007-11-06 at 23:17 +0100, Romano Giannetti wrote:
> > Well, I started bisecting it. It will be a long shot, I suspect...
>
> Well, I spent the last 36 hours (more or less) trying to bisect the SD
> problem. The method I used w
On Thursday 08 November 2007 01:20, Matt Mackall wrote:
> On Wed, Nov 07, 2007 at 12:30:45PM -0800, Andrew Morton wrote:
> > Ow. Yes, from my reading delay_tsc() can return early (or after
> > heat-death-of-the-universe) if the TSCs are offset and if preemption
> > migrates the calling task betwee
On 7/Nov/2007 20:10 werner wrote ..
> With 2.6.23-rc2 is the same problem: it crashed at the beginning: EIP 060
> c03fdea4
> EFLAGS 00010212 EIP is at xor_sse_2+0x34/0x200
> Again during the compilation was reclaimed that
> /arch/x86/Makefile.o
> cannot be found and were certain dependencies on
On Wed, Nov 07, 2007 at 11:24:55PM +0100, Rafael J. Wysocki wrote:
> On Wednesday, 7 of November 2007, Daniel Drake wrote:
> > The CONFIG_SUSPEND changes in 2.6.23 caused a regression under certain
> > configuration conditions (SUSPEND=n, USB_AUTOSUSPEND=y) where all USB device
> > attributes in sy
On Wed, 2007-11-07 at 17:10 -0500, Steven Rostedt wrote:
> >
> > It would be nice if sched_nr_migrate didn't exist, really. It's hard to
> > imagine anyone wanting to tweak it, apart from developers.
>
> I'm not so sure about that. It is a tunable for RT. That is we can tweak
> this value to be
Norbert Preining wrote:
Dear all!
(please Cc me for answers)
Since about 5 days I am having serious problems with my SATA drive:
kernel 2.6.22 (from Debian/sid)
hardware nv
Sometimes at boot time, often/always at disk io intense stuff:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 acti
On Thursday 08 November 2007, Denys Fedoryshchenko wrote:
> 2.6.24-rc2 not working very well
>
>
> dmesg
> [ 12.386395] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> [ 12.405579] ide: Assuming 33MHz system bus speed for PIO modes; override
> with idebus=xx
> [ 12.430441] SC120
On Wed, Nov 07, 2007 at 12:30:45PM -0800, Andrew Morton wrote:
> Ow. Yes, from my reading delay_tsc() can return early (or after
> heat-death-of-the-universe) if the TSCs are offset and if preemption
> migrates the calling task between CPUs.
>
> I suppose a lameo fix would be to disable preemptio
On Wed, Nov 07, 2007 at 03:36:05PM +0100, Jan Kara wrote:
> > What if more than one application wants to use this facility?
>
> That should be fine - let's see: Each application keeps somewhere a time
> when
> it started a scan of a subtree (or it can actually remember a time when it
> set the f
Mark Lord <[EMAIL PROTECTED]> :
[...]
> I've now received a couple of private emails from people reporting
> full success with this patch.
Ok, I have pushed the patch below for Jeff to pull at korg.
>From 1dd7681bc2ff171341ea5cae957f8ecb5c0c102e Mon Sep 17 00:00:00 2001
From: Mark Lord <[EMAIL PR
> On Wed, 7 Nov 2007 15:28:33 -0800 Andrew Morton <[EMAIL PROTECTED]> wrote:
> > On Wed, 7 Nov 2007 14:47:22 -0800 David Brown <[EMAIL PROTECTED]> wrote:
> > compat_sys_times() has bogus return until jiffies is >= 0. I discovered
> > this running LTP within 5 minutes of booting.
> >
> > The retur
Hello.
Christoph Hellwig wrote:
> Same argument as with the AA folks: it does not have any business looking
> at the vfsmount. If you create a file it can and in many setups will
> show up in multiple vfsmounts, so making decisions based on the particular
> one this creat happens through is wrong
On 11/07/2007 04:12 PM, Roland McGrath wrote:
> Sure has my ACK.
> I never really understood why my old patch was not taken 2.5 years ago.
>
>
I forget the details, but I had to make some kind of trivial change
to make it work in some corner cases.
-
To unsubscribe from this list: send the lin
Tejun Heo wrote:
Florian La Roche wrote:
Hello all,
I've taking email addresses from the last NCQ blacklist changes going
into the kernel.
This Fujitsu drive also gives me spurious command completions. Detailed
output also available at https://bugzilla.redhat.com/show_bug.cgi?id=366181.
Let me
2.6.24-rc2 not working very well
dmesg
[ 12.386395] Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
[ 12.405579] ide: Assuming 33MHz system bus speed for PIO modes; override
with idebus=xx
[ 12.430441] SC1200: IDE controller (0x100b:0x0502 rev 0x01) at PCI slot
:00:12.2
[
FYI, http://sourceware.org/systemtap/wiki/utrace/tests has details on the
ptrace-tests suite we're collecting. A test I added there is how I noticed
the PTRACE_GET_THREAD_AREA regression. A regression test for the ebp bug
should be easy to add too.
Thanks,
Roland
-
To unsubscribe from this list
I am using Gentoo (and it is custom build of linux, actually only busybox +
kernel + uclibc and few other tools), hdparm is vanilla 7.7
I will try to compile now -rc2 to see if there any changes.
With 16MB 2.6.24-rc1 works fine, 1GB working also with some errors in dmesg.
And IF that all is im
On Monday, 5 of November 2007, Grant Wilson wrote:
> Hi,
> I got this oops on 2.6.24-rc1-641-gb4f5550:
(1) Is this reproducible?
(2) Did it happen previously on your system?
> [18073.371126] Unable to handle kernel NULL pointer dereference at
> 0120 RIP:
> [18073.371134] [] check_
> Well, I spent the last 36 hours (more or less) trying to bisect the SD
> problem. The method I used was to insert the card, umount it, and make 8 dd
> in a row; the kernel is "bad" if they differs, "good" if they are the same.
>
> I could not finish the bisect. The last pair good/bad were:
On Wed, Nov 07, 2007 at 01:12:22PM -0800, Roland McGrath wrote:
> Sure has my ACK.
> I never really understood why my old patch was not taken 2.5 years ago.
Nor I. It's needed.
As is your PTRACE_SET_THREAD_INFO patch from yesterday - with these
two fixes, I can boot a 32-bit UML on a 64-bit ho
David Woodhouse <[EMAIL PROTECTED]> wrote:
> Ew, no. This is horridly broken. You should never use CONFIG_xxx_MODULE
> in the static kernel at all -- and you should _especially_ not be using
> it in header files which are exported to userspace.
AOUT support can be mostly built into a module, but
> On Wed, 7 Nov 2007 14:47:22 -0800 David Brown <[EMAIL PROTECTED]> wrote:
> compat_sys_times() has bogus return until jiffies is >= 0. I discovered
> this running LTP within 5 minutes of booting.
>
> The return result
>
> return compat_jiffies_to_clock_t(jiffies);
>
> will return '-1' to
1 - 100 of 378 matches
Mail list logo
