On Sat, 29 Sep 2007 01:31:52 -0400 Jeff Garzik <[EMAIL PROTECTED]> wrote:
> doesn't Andrew have a version of these patches that move the useful
> patch text into the area where it will get copied into the permanent
> kernel changelog?
>
> also, your PHYLIB patches give no notion at all of
doesn't Andrew have a version of these patches that move the useful
patch text into the area where it will get copied into the permanent
kernel changelog?
also, your PHYLIB patches give no notion at all of proper patch order.
-
To unsubscribe from this list: send the line "unsubscribe
Maciej W. Rozycki wrote:
A driver model and phylib update. It includes the following changes:
1. Removal of unused module options.
2. Phylib support and the resulting removal of generic bits for handling
the PHY.
3. Proper reserving of device resources and using ioremap()ped handles
Maciej W. Rozycki wrote:
Remove typedefs, volatiles and convert kmalloc()/memset() pairs to
kcalloc(). Also reformat the surrounding clutter.
Signed-off-by: Maciej W. Rozycki <[EMAIL PROTECTED]>
---
On Thu, 20 Sep 2007, Jeff Garzik wrote:
Remove the "linux-" prefix.
Hmm, it looks like a
[CCd to possibly interested Pierre Ossman and Rodolfo Giometti]
Hi there,
First, sorry for my poor english - I am not a native.
I know there have been a thread about this problem few months ago, but as
far as I see it did not led to any results:
On Tue, 2007-03-07 at 12:45 -0400, Zephaniah E. Hull wrote:
> We just want a more flexible approach then what we are already using[0].
>
> I'll see about writing something up when I get back to my computers[1]
> and have things set back up[2].
>
> Zephaniah E. Hull.
>
> 0: EVIOCGRAB.
> 1: The
My apologies for the two bogus addresses in the "To" of my previous
message. Script error, won't happen again.
Frans Pop
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Wolfgang Erig wrote:
> the latest kernel does not power off my system.
This is a known regression in rc8. See this mail and thread for details:
http://lkml.org/lkml/2007/9/25/239
The issue has already been fixed in Linus' git tree.
Please try again with that, or apply the patches included in the
Wolfgang Erig wrote:
> Hi,
>
> the latest kernel does not power off my old laptop.
>
> 2.6.22 succeeded
> 2.6.23-rc8 failed
>
> $ git bisect good
> Bisecting: 0 revisions left to test after this
> [626073132b381684c4983e0d911e9aceb32e2cbc] Assembly header and main routine
> for new x86 setup
On Fri, 28 Sep 2007 22:47:16 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Ayaz Abdulla wrote:
> > I am trying to track down a forcedeth driver issue described by bug 9047
> > in bugzilla (2.6.23-rc7-git1 forcedeth w/ MCP55 oops under heavy load).
> > I added a patch to synchronize the timer
Wolfgang Erig wrote:
> Hi,
>
> the latest kernel does not power off my system.
>
> 2.6.22 succeeded
> 2.6.23-rc8 failed
>
> $ git bisect bad
> Bisecting: 0 revisions left to test after this
> [f216cc3748a3a22c2b99390fddcdafa0583791a2] ACPI: suspend: consolidate
> handling of Sx states.
>
>
On Sat, Sep 29, 2007 at 12:04:47AM +, Maarten Bressers wrote:
> On Fri, 28 Sep 2007 15:49:26 -0700
> Greg KH <[EMAIL PROTECTED]> wrote:
>
> > On Fri, Sep 28, 2007 at 08:56:30PM +, Maarten Bressers wrote:
> > > This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on x86_64,
> >
On Fri, 28 Sep 2007, Alejandro Riveira Fernández wrote:
> I feel it better than 20.5 but the later is more stable. Let me explain.
>
> I patched a 2.6.22.9 kernel with both versions 22 and 20.5[1]. With the 22
> version if i lock the screen (run screensaver) or i try to run a wine program
> i
Ayaz Abdulla wrote:
I am trying to track down a forcedeth driver issue described by bug 9047
in bugzilla (2.6.23-rc7-git1 forcedeth w/ MCP55 oops under heavy load).
I added a patch to synchronize the timer handlers so that one handler
doesn't accidently enable the IRQ while another timer
> >> What kind of partition table is it? MS-DOS partition tables have a 2 TB
> >> limit.
> Issue number one -- don't use fdisk, as it doesn't support devices that
> big. Use parted instead:
climate:~ benc$ sudo parted /dev/sdc check 1
Warning: Partition 1 is 2005GB, but the file system is
On Fri, 28 Sep 2007 at 8:49pm, Benjamin Carr wrote
What kind of partition table is it? MS-DOS partition tables have a 2 TB
limit.
Hadn't thought of that, doesn't look good.
-Ben
sudo fdisk -l /dev/sdc1
benc's password:
Issue number one -- don't use fdisk, as it doesn't support devices
On Friday 28 September 2007 05:55, Daniel Spång wrote:
> Applications with dynamic input and dynamic memory usage have some
> issues with the current overcommitting kernel. A high memory usage
> situation eventually results in that a process is killed by the OOM
> killer. This is especially
On Friday 28 September 2007 12:16, Trond Myklebust wrote:
> crash> bt 3188
crash> ps|grep ps
Hey, that looks just like kdb! But I heard that kgdb is better in every
way than kdb.
Innocently yours,
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Friday 28 September 2007 06:35, Peter Zijlstra wrote:
> ,,,it would be grand (and dangerous) if we could provide for a
> button that would just kill off all outstanding pages against a dead
> device.
Substitute "resources" for "pages" and you begin to get an idea of how
tricky that actually
> What kind of partition table is it? MS-DOS partition tables have a 2 TB
> limit.
Hadn't thought of that, doesn't look good.
-Ben
sudo fdisk -l /dev/sdc1
benc's password:
Disk /dev/sdc1: 2004.8 GB, 2004856477184 bytes
255 heads, 63 sectors/track, 243743 cylinders
Units = cylinders of 16065 *
Benjamin Carr wrote:
>>> sudo fdisk -l /dev/sdc1
>> ^ Uh...
>
> yeah, long day:
>
> Disk /dev/sdc: 12999.9 GB, 1288871168 bytes
> 255 heads, 63 sectors/track, 1580491 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>Device Boot Start
Your fix seems to have remedied a problem we are having with EDID
fetches through vm86.c. At the present moment, we're trying to
understand your cleanup so as to back port it to an earlier rev of
the kernel (2.6.18).
3 questions for you:
1. Are we correct in understanding that your
Wolfgang Erig wrote:
> Hi,
>
> the latest kernel does not power off my old laptop.
>
> 2.6.22 succeeded
> 2.6.23-rc8 failed
>
> $ git bisect good
> Bisecting: 0 revisions left to test after this
> [626073132b381684c4983e0d911e9aceb32e2cbc] Assembly header and main routine
> for new x86 setup
> > sudo fdisk -l /dev/sdc1
> ^ Uh...
yeah, long day:
Disk /dev/sdc: 12999.9 GB, 1288871168 bytes
255 heads, 63 sectors/track, 1580491 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdc1
Martin Michlmayr wrote:
* Jeff Garzik <[EMAIL PROTECTED]> [2007-09-28 06:23]:
Yoichi's original patch and explanation can be found at
http://lkml.org/lkml/2007/8/23/411
I've no idea why it hasn't been applied unless nobody is quite sure who
owns it. As a PCI fix I guess Greg does (and drop it
Alan Cox wrote:
Drain up to 512 words from host/bridge FIFO on stuck DRQ HSM violation,
rather than just getting stuck there forever.
Why 512 words ?
Though I have queued Mark's patch to be applied, my gut feeling would
lean towards a single DRQ block, rather than 512.
Hi,
the latest kernel does not power off my old laptop.
2.6.22 succeeded
2.6.23-rc8 failed
$ git bisect good
Bisecting: 0 revisions left to test after this
[626073132b381684c4983e0d911e9aceb32e2cbc] Assembly header and main routine for
new x86 setup code
Which more info is needed?
Benjamin Carr wrote:
>> What kind of partition table is it? MS-DOS partition tables have a 2 TB
>> limit.
>
> Hadn't thought of that, doesn't look good.
> -Ben
>
> sudo fdisk -l /dev/sdc1
^ Uh...
> benc's password:
>
> Disk /dev/sdc1: 2004.8 GB, 2004856477184 bytes
>
William Cattey wrote:
> Andi,
>
> Sorry to have taken so long to take another step with this problem.
> Once my customers had a work-around, other priorities crowded out this
> project. Today Chuck and I did a little more work. We'd heard that a
> more recent kernel alleged to fix this stuff.
On Fri, Sep 28, 2007 at 11:11:07AM -0700, Stephen Hemminger wrote:
>
> It is only the nested removal problem.
Well such a count could apply to direct removals too. In other
words, you could ask modprobe to remove all modules for which
this count is zero.
Cheers,
--
Visit Openswan at
Hi,
the latest kernel does not power off my system.
2.6.22 succeeded
2.6.23-rc8 failed
$ git bisect bad
Bisecting: 0 revisions left to test after this
[f216cc3748a3a22c2b99390fddcdafa0583791a2] ACPI: suspend: consolidate handling
of Sx states.
Which more info is needed?
Wolfgang
-
To
From: Rob Landley <[EMAIL PROTECTED]>
Add Documentation/x86_64/00-INDEX
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
---
Trying again with the right path...
x86_64/00-INDEX | 14 ++
1 file changed, 14 insertions(+)
--- /dev/null 2007-04-23 10:59:00.0 -0500
+++
On Thursday 27 September 2007 23:50, Andrew Morton wrote:
> Actually we perhaps could address this at the VFS level in another
> way. Processes which are writing to the dead NFS server will
> eventually block in balance_dirty_pages() once they've exceeded the
> memory limits and will remain
From: Rob Landley <[EMAIL PROTECTED]>
Add Documentation/x86_64/00-INDEX
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
---
x86_64/00-INDEX | 14 ++
1 file changed, 14 insertions(+)
--- /dev/null 2007-04-23 10:59:00.0 -0500
+++ Documentation/x86_64/00-INDEX
On Fri, 2007-09-28 at 22:03 +0200, Santiago Garcia Mantinan wrote:
> Hi!
>
> I have just compiled a 2.6.23-rc8 using the config from my 2.6.22 as a basis
> and I came out with a not working (almost black) vga text console.
>
> This is what I'm getting on my logs:
>
> Console: colour dummy
Nakajima, Jun wrote:
> Yes. For the native, "safe_halt" is "sti; hlt". The "native_halt" is
> just "hlt". So the para_virt part of "hlt" could be moved to pv_cpu_ops,
> and the "sti" part stays in pv_irq_ops.
>
By "sti part", you mean the full "sti; hlt" sequence of safe_halt,
right? Since it
On Friday 28 September 2007, Frans Pop wrote:
> My Toshiba Satellite A40 (i386, P4 Mobile) hangs during boot after:
> Marking TSC unstable due to: possible TSC halt in C2.
> Time: acpi_pm clocksource has been installed.
A few new boot attempts show the problem is more likely at:
Probing IDE
From: Rob Landley <[EMAIL PROTECTED]>
Remove nonstandard line break from Documentation/powerpc/00-INDEX
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
---
This is the only instance of a newline in a 00-INDEX file description, and
it confuses my 00-INDEX > index.html converter.
From: Rob Landley <[EMAIL PROTECTED]>
Add a 00-INDEX file for Documentation/vm
Signed-off-by: Rob Landley <[EMAIL PROTECTED]>
---
Documentation/vm/00-INDEX | 20
1 file changed, 20 insertions(+)
--- /dev/null 2007-04-23 10:59:00.0 -0500
+++
Jeremy Fitzhardinge wrote:
> Nakajima, Jun wrote:
> > Jeremy Fitzhardinge wrote:
> >
> >
> > > + .pv_irq_ops = {
> > > + .init_IRQ = native_init_IRQ,
> > > + .save_fl = native_save_fl,
> > > + .restore_fl = native_restore_fl,
> > > + .irq_disable =
On Mon, 2007-09-24 at 23:25 -0700, Randy Dunlap wrote:
> Is there some reason that we don't put all video gfx config in one
> place? Is the split just historical, based on subdirectory locations,
> or is there a bigger reason for it?
Just historical, based on subdirectory locations. Someone did
On Wed, 2007-09-26 at 11:43 +0800, Bryan Wu wrote:
> From: Michael Hennerich <[EMAIL PROTECTED]>
> Date: Wed, 26 Sep 2007 11:33:01 +0800
> Subject: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device
> driver for a SHARP LQ043T1DG01 TFT LCD
>
> Signed-off-by: Michael Hennerich
On Saturday 29 September 2007, Kyle McMartin wrote:
>
> On Sat, Sep 29, 2007 at 01:38:23AM +0200, Arnd Bergmann wrote:
> > 1. Byte order matches the order in which 64 bit arguments are split
> > in system call conventions on all platforms.
>
> I checked powerpc, sparc, and mips, which are
On Fri, 28 Sep 2007 15:49:26 -0700
Greg KH <[EMAIL PROTECTED]> wrote:
> On Fri, Sep 28, 2007 at 08:56:30PM +, Maarten Bressers wrote:
> > This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on x86_64,
> > use of deprecated function pci_find_device() and a section mismatch.
> >
On Fri, Sep 28, 2007 at 08:01:31PM -0400, Kyle McMartin wrote:
> I checked powerpc, sparc, and mips, which are (besides parisc) the only
> 64-bit with 32-bit userspace big endian architectures that I could think
> of offhand. A quick grep shows sh64 too... Paul?
>
Ah, no CONFIG_COMPAT on sh64
On Sat, Sep 29, 2007 at 01:38:23AM +0200, Arnd Bergmann wrote:
> 1. Byte order matches the order in which 64 bit arguments are split
>in system call conventions on all platforms.
I checked powerpc, sparc, and mips, which are (besides parisc) the only
64-bit with 32-bit userspace big endian
Eric Sandeen wrote:
> Justin Piszcz wrote:
>> Including LKML on this one as it may be a partition size limit? Sdc1 is
>> not 11TB.
>>
>> Justin.
>
> Yup saw the same thing:
>
> (1957867653*1024)/1024/1024/1024/1024 = 1.82T
>
> I'm afraid you don't have a truncated filesystem, you have a
On Fri, 28 Sep 2007 10:35:44 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Fri, 28 Sep 2007, KAMEZAWA Hiroyuki wrote:
>
> > On Tue, 25 Sep 2007 16:42:17 -0700
> > Christoph Lameter <[EMAIL PROTECTED]> wrote:
> >
> > > +static noinline void vcompound_free(void *addr)
> > > +{
> >
On Saturday 29 September 2007, you wrote:
> +static inline u64 compat_merge64(u32 left, u32 right)
> +{
> +#if defined(__BIG_ENDIAN)
> + return ((u64)left << 32) | right;
> +#else /* defined (__LITTLE_ENDIAN) */
> + return ((u64)right << 32) | left;
> +#endif
> +}
Looks good, if we
Andrew Morton wrote:
if (rev > OLD_FLAT_VERSION) {
+ unsigned long persistent = 0;
`persistent' here only has meaning inside the next nesting level, so should
be moved down into that scope for readability reasons.
See below.
+ if
Basically everyone is using the same sys32_fallocate. Delete a whole bunch of
archdep code and move the compat wrapper to fs/compat.c
Signed-off-by: Kyle McMartin <[EMAIL PROTECTED]>
---
arch/mips/kernel/linux32.c|7 ---
arch/mips/kernel/scall64-o32.S|2 +-
To be used when endianness matters for argument ordering when reassembling
a 64-bit value out of two register halves.
Signed-off-by: Kyle McMartin <[EMAIL PROTECTED]>
---
include/linux/compat.h |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git
Sergey Popov wrote:
Short description: after recompiling 32-bit kernel with 64Gb highmem
support and rebooting into it, OS started working very much slower
then before.
Specifications: Intel Core 2 Duo [EMAIL PROTECTED],4Ghz on Intel i965Q-based
motherboard. 6Gb of DDR2 RAM, 2x1Gb+2x2Gb,
Dave Hansen wrote:
On Fri, 2007-09-28 at 01:30 -0700, Andrew Morton wrote:
On Thu, 27 Sep 2007 15:54:20 -0600 Zan Lynx <[EMAIL PROTECTED]> wrote:
Near the end of my boot sequence, there is a kernel error. I am not
sure exactly what user-space is doing to make this happen, but I know
Justin Piszcz wrote:
> Including LKML on this one as it may be a partition size limit? Sdc1 is
> not 11TB.
>
> Justin.
Yup saw the same thing:
(1957867653*1024)/1024/1024/1024/1024 = 1.82T
I'm afraid you don't have a truncated filesystem, you have a truncated
block device. I'm afraid this
Nakajima, Jun wrote:
> Jeremy Fitzhardinge wrote:
>
>> This patch refactors the paravirt_ops structure into groups of
>> functionally related ops:
>>
>> pv_info - random info, rather than function entrypoints
>> pv_init_ops - functions used at boot time (some for module_init too)
>> pv_misc_ops
No change in behavior even in case of low memory systems. I confirmed
it running on 1Gig machine.
Thanks
--Chakri
On 9/28/07, Chakri n <[EMAIL PROTECTED]> wrote:
> Here is a the snapshot of vmstats when the problem happened. I believe
> this could help a little.
>
> crash> kmem -V
>
Jeremy Fitzhardinge wrote:
> This patch refactors the paravirt_ops structure into groups of
> functionally related ops:
>
> pv_info - random info, rather than function entrypoints
> pv_init_ops - functions used at boot time (some for module_init too)
> pv_misc_ops - lazy mode, which didn't fit
On Friday, September 28, 2007 3:23 pm Roland Dreier wrote:
> > I don't have a 945 to test with, but Dave might...
>
> Actually I'm not looking for testing (I can test fine on my own
> laptop :) I was just hoping someone with docs could tell me "MSI is
> documented to be broken on 945GM" or "Oh
Maarten Bressers wrote:
Randy Dunlap <[EMAIL PROTECTED]> wrote:
On Fri, 28 Sep 2007 20:56:30 + (UTC) Maarten Bressers wrote:
This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on x86_64,
use of deprecated function pci_find_device() and a section mismatch.
Build log and
On Tue, 18 Sep 2007 16:09:25 +0800
Bryan Wu <[EMAIL PROTECTED]> wrote:
> From: Bernd Schmidt <[EMAIL PROTECTED]>
>
> This just adds minimum support for the Blackfin relocations,
> since we don't have enough space in each reloc. The idea
> is to store a value with one relocation so that
On Fri, 2007-09-28 at 11:15 -0400, Rik van Riel wrote:
> On Fri, 28 Sep 2007 16:36:34 +0200
> Eric Dumazet <[EMAIL PROTECTED]> wrote:
>
> > On Fri, 28 Sep 2007 10:17:11 -0400
> > Rik van Riel <[EMAIL PROTECTED]> wrote:
> >
> > > On Fri, 28 Sep 2007 10:04:23 -0400
> > > "linux-os \(Dick
--
On Fri, 28 Sep 2007, Gautham R Shenoy wrote:
> >
> > +#ifdef CONFIG_PREEMPT_RCU_BOOST
> > +/*
> > + * Task state with respect to being RCU-boosted. This state is changed
> > + * by the task itself in response to the following three events:
>
On Fri, Sep 28, 2007 at 08:56:30PM +, Maarten Bressers wrote:
> This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on x86_64,
> use of deprecated function pci_find_device() and a section mismatch.
> Build log and .config file included.
>
> Signed-off by: Maarten Bressers <[EMAIL
Sorry Randy, I accidentally deleted the subject line, so I sent it again.
On Fri, 28 Sep 2007 14:48:53 -0700
Randy Dunlap <[EMAIL PROTECTED]> wrote:
> On Fri, 28 Sep 2007 20:56:30 + (UTC) Maarten Bressers wrote:
>
> > This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on
Module refcounts currently use a percpu counter stored
in the 'struct module'. However, we also have a more
generic implementation that does stuff like handle
hotplug cpus.
I'm not actually all that convinced that this refcount
actually does a lot of good, with cpus racing bumping
the counters
Hi Paul,
Some silly doubts.
On Mon, Sep 10, 2007 at 11:39:01AM -0700, Paul E. McKenney wrote:
> Work in progress, not for inclusion.
>
> RCU priority boosting is needed when running a workload that might include
> CPU-bound user tasks running at realtime priorities with preemptible RCU.
> In
Randy Dunlap <[EMAIL PROTECTED]> wrote:
> On Fri, 28 Sep 2007 20:56:30 + (UTC) Maarten Bressers wrote:
>
> > This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on x86_64,
> > use of deprecated function pci_find_device() and a section mismatch.
> > Build log and .config file
From: [EMAIL PROTECTED]
Date: Thu, 27 Sep 2007 18:12:19 -0700
> +static inline int dma_flags_set_dmabarrier(int dir) {
> + return (dir | (DMA_BARRIER_ATTR<< DMA_ATTR_SHIFT));
> +}
> +
> +static inline int dma_flags_get_direction(int dir) {
> + return (dir & DMA_DIR_MASK);
> +}
> +
>
From: [EMAIL PROTECTED]
Date: Thu, 27 Sep 2007 18:10:59 -0700
> +#ifndef ARCH_CAN_REORDER_DMA
> +static inline int dma_flags_set_dmabarrier(int dir) {
> + return dir;
> +}
> +#endif /* ARCH_CAN_REORDER_DMA */
Coding style, that initial openning brace should be
on a line by itself.
-
To
From: [EMAIL PROTECTED]
Date: Thu, 27 Sep 2007 18:09:26 -0700
>
> On Altix, DMA may be reordered between a device and host memory.
> This reordering can happen in the NUMA interconnect, and it usually
> results in correct operation and improved performance. In some
> situations it may be
ben soo wrote:
i spoke too soon. The Gbit interface still dies. Lasted around 19hrs.
or so. i can't tell if there are hardware issues: yesterday a Gbit NIC
on the firewall died. Different chip (Realtek), different driver,
different machine, same segment. Segment is a mix of 100Mbit and
Santiago Garcia Mantinan wrote:
> Hi!
>
> I have just compiled a 2.6.23-rc8 using the config from my 2.6.22 as a basis
> and I came out with a not working (almost black) vga text console.
>
> This is what I'm getting on my logs:
>
> Console: colour dummy device 80x25
> console [tty0] enabled
>
Huang, Ying wrote:
> Hi, Peter,
>
> On Wed, 2007-09-19 at 09:04 -0700, H. Peter Anvin wrote:
>> Huang, Ying wrote:
>>> Known Issues:
>>>
>>> 1. Where is safe to place the linked list of setup_data?
>>> Because the length of the linked list of setup_data is variable, it
>>> can not be copied into
> I don't have a 945 to test with, but Dave might...
Actually I'm not looking for testing (I can test fine on my own laptop :)
I was just hoping someone with docs could tell me "MSI is documented to be
broken on 945GM" or "Oh yeah, 945GM requires you to set SECRET_MSI_ENABLE_BIT
in register FOO
Including LKML on this one as it may be a partition size limit? Sdc1 is
not 11TB.
Justin.
On Fri, 28 Sep 2007, Benjamin Carr wrote:
For the second time in two weeks, a system restart has resulted in a
truncated filesystem on my server. The server is running 64bit SuSE with a
fibrechannel
>-Original Message-
>From: Jean Delvare [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 31, 2007 8:51 AM
>To: Gaston, Jason D
>Cc: linux-kernel@vger.kernel.org; [EMAIL PROTECTED]; [EMAIL PROTECTED]
>Subject: Re: [PATCH 2.6.23-rc4][reRESEND] i2c-i801: SMBus patch for
Intel
>Tolapai
>
>Hi
bo yang wrote:
> Added module parameter "poll_mode_io" to support for "polling" (reduced
> interrupt operation).
> In this mode, IO completion interrupts are delayed. At the end of
> initiating IOs,
> the driver schedules for cmd completion if there are pending cmds.
>
On Fri, 28 Sep 2007 17:24:20 -0400 Bill Davidsen wrote:
> Randy Dunlap wrote:
>
> > This seems reasonable, so I tried to use it. Here are the results
> > and comments and meta-comments.
> >
> >
> > 1. Please forcibly wrap text lines in mail body at around column 70-72.
> >
> > 2. Put
On Fri, 28 Sep 2007 20:56:30 + (UTC) Maarten Bressers wrote:
> This (trivial) patch fixes two compiler warnings for 2.6.23-rc8 on x86_64,
> use of deprecated function pci_find_device() and a section mismatch.
> Build log and .config file included.
>
> Signed-off by: Maarten Bressers <[EMAIL
On Fri, 28 Sep 2007 17:32:00 -0400 Erez Zadok wrote:
> 1. Updates chapter 13 (printing kernel messages) to expand on the use of
>pr_debug()/pr_info(), what to avoid, and how to hook your debug code with
>kernel.h.
>
> 2. New chapter 19, branch prediction optimizations, discusses the
On Saturday 29 September 2007 03:15, Sergey Popov wrote:
> Short description: after recompiling 32-bit kernel with 64Gb highmem
> support and rebooting into it, OS started working very much slower
> then before.
>
> Specifications: Intel Core 2 Duo [EMAIL PROTECTED],4Ghz on Intel i965Q-based
>
On Saturday 29 September 2007 03:33, Christoph Lameter wrote:
> On Fri, 28 Sep 2007, Nick Piggin wrote:
> > On Wednesday 19 September 2007 13:36, Christoph Lameter wrote:
> > > SLAB_VFALLBACK can be specified for selected slab caches. If fallback
> > > is available then the conservative settings
Ingo Molnar wrote:
Maybe there's more to come: if we can get CONFIG_FAIR_USER_SCHED to work
properly then your Xorg will have a load-independent 50% of CPU time all
to itself.
It seems that perhaps that 50% makes more sense on a single/dual CPU
system than on a more robust one, such as a
TCP MD5 signatures on sparc64 (big-endian) completely fail on current
kernel releases in interoperability with Cisco/Foundry or other
little-endian linux systems.
The root cause is a cast in the return statement of tcp_v4_md5_do_lookup,
where a tcp4_md5sig_key is casted onto tcp_md5sig_key
Here is a the snapshot of vmstats when the problem happened. I believe
this could help a little.
crash> kmem -V
NR_FREE_PAGES: 680853
NR_INACTIVE: 95380
NR_ACTIVE: 26891
NR_ANON_PAGES: 2507
NR_FILE_MAPPED: 1832
NR_FILE_PAGES: 119779
Kanevsky, Arkady wrote:
Exactly,
it forces the burden on administrator.
And one will be forced to try one mount for iWARP and it does not
work issue another one TCP or UDP if it fails.
Yack!
And server will need to listen on different IP address and simple
* will not work since it will need to
The script calls checkpatch.pl on each file, and formats any error messages
to comply with standard compiler error messages:
file_name:line_number:error_message
This is particularly useful when run from within a text editor which can
parse these error messages and show the user a buffer
1. Updates chapter 13 (printing kernel messages) to expand on the use of
pr_debug()/pr_info(), what to avoid, and how to hook your debug code with
kernel.h.
2. New chapter 19, branch prediction optimizations, discusses the whole
un/likely issue.
Cc: "Kok, Auke" <[EMAIL PROTECTED]>
Cc:
Signed-off-by: Erez Zadok <[EMAIL PROTECTED]>
---
scripts/checkpatch.pl |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
index dae7d30..ecbb030 100755
--- a/scripts/checkpatch.pl
+++ b/scripts/checkpatch.pl
@@ -33,6 +33,7 @@ if
The following is a series of patches related to coding standards. The first
patch updates the CodingStandards document with respect to printk debugging
and un/likely use; the second patch updates the usage string for
checkpatch.pl; the third patch introduces a new small perl script that can
be
bo yang wrote:
> +static ssize_t
> +sysfs_max_sectors_read(struct kobject *kobj,
> + struct bin_attribute *bin_attr,
> + char *buf, loff_t off, size_t count)
> +{
> + struct Scsi_Host *host = class_to_shost(container_of(kobj,
> +
From: David Miller <[EMAIL PROTECTED]>
Date: Fri, 28 Sep 2007 14:20:15 -0700 (PDT)
> Thanks for finding this bug.
>
> > --- linux.old/include/net/tcp.h 2007-09-28 21:43:26.0 +0200 +++
> > linux/include/net/tcp.h 2007-09-28 21:45:35.0 +0200 @@ -1055,6
> > +1055,7 @@ static
Kanevsky, Arkady wrote:
Exactly,
it forces the burden on administrator.
And one will be forced to try one mount for iWARP and it does not
work issue another one TCP or UDP if it fails.
Yack!
I see your point. I have no defense. My hands have been tied on fixing
this properly...
And
On Friday, 28 September 2007 23:17, Mark Lord wrote:
> Thomas Gleixner wrote:
> > On Fri, 2007-09-28 at 16:27 -0400, Mark Lord wrote:
> ..
> >> On a closely related note: I just now submitted a patch to fix
> >> SMP-poweroff,
> >> by having it do disable_nonboot_cpus before doing poweroff.
> >>
From: "Peter Lieven" <[EMAIL PROTECTED]>
Date: Fri, 28 Sep 2007 22:42:25 +0200 (CEST)
> TCP MD5 signatures on sparc64 (big-endian) completely fail on current
> kernel releases in interoperability with Cisco/Foundry or other
> little-endian linux systems.
>
> The root cause is a cast in the
Randy Dunlap wrote:
This seems reasonable, so I tried to use it. Here are the results
and comments and meta-comments.
1. Please forcibly wrap text lines in mail body at around column 70-72.
2. Put patches inline in the mail body, not as attachments.
I'll offer this suggestion, knowing it
Thomas Gleixner wrote:
On Fri, 2007-09-28 at 16:27 -0400, Mark Lord wrote:
..
On a closely related note: I just now submitted a patch to fix SMP-poweroff,
by having it do disable_nonboot_cpus before doing poweroff.
Which has led me to thinking..
..are similar precautions perhaps necessary
On Thursday, 27 September 2007 17:49, Thomas Gleixner wrote:
> On Thu, 2007-09-27 at 17:59 +0200, Rafael J. Wysocki wrote:
> > > 2) CPU hotplug is busted (onlining of CPU1 kills the kernel), probably
> > > due to
> > >the same issue that I'm having with the -hrt version of 2.6.23-rc8
> > >
On Fri, 28 Sep 2007 11:06:09 +0200
Thomas Gleixner <[EMAIL PROTECTED]> wrote:
> > The problem with git-commit is who's repo to add the hook to. I did
> > attempt to do this by picking up each of linus' main releases and then
> > using the git blame engine to attribute each "failure" to a
1 - 100 of 896 matches
Mail list logo
