[Partially solved] Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

Hi, William. On Feb 12 2005, William Park wrote: > Your 'dmesg' says > Warning: Secondary channel requires an 80-pin cable for operation. > I assume it is. Well, I just finished compiling the 2.6.11-rc4 kernel and the problem persisted. This time, I enabled ACPI debugging and it indeed gener

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Feb 12 2005, William Park wrote: > Do you have MSI on by any chance? (CONFIG_PCI_MSI) If so, try kernel > without it. My motherboard exhibits runaway IRQ with it. Ok, now I've just downloaded the -rc4 patch and while selecting the options to compile, I saw what MSI means. No, I didn't have M

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Feb 12 2005, William Park wrote: > On Sat, Feb 12, 2005 at 09:50:43PM -0200, Rog?rio Brito wrote: > > To prevent the matters of loosing track of what is being done, I only > > changed one option at a time. I put the dmesg logs of all my attempts > > at

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Sat, Feb 12, 2005 at 09:50:43PM -0200, Rog?rio Brito wrote: > On Feb 12 2005, William Park wrote: > > This looks awefully like 'acpi' is on. If 'acpi=noirq' does not work, > > then try 'pci=noacpi'. > > Hi, Willian. > > First of all, thank you very much for both your attention and help. > >

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Feb 12 2005, William Park wrote: > This looks awefully like 'acpi' is on. If 'acpi=noirq' does not work, > then try 'pci=noacpi'. Hi, Willian. First of all, thank you very much for both your attention and help. Unfortunately, I have already tried booting the 2.6.11-rc3-mm2 that I just compil

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Sat, Feb 12, 2005 at 08:47:15PM -0200, Rog?rio Brito wrote: > On Feb 12 2005, William Park wrote: > > On Sat, Feb 05, 2005 at 08:45:58PM -0200, Rog?rio Brito wrote: > > > For some kernel versions (say, since 2.6.10 proper, all the 2.6.11-rc's, > > > some -mm trees and also -ac) I have been getti

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Feb 12 2005, William Park wrote: > On Sat, Feb 05, 2005 at 08:45:58PM -0200, Rog?rio Brito wrote: > > For some kernel versions (say, since 2.6.10 proper, all the 2.6.11-rc's, > > some -mm trees and also -ac) I have been getting the message "irq 10: > > nobody cared!". > > Try 'acpi=noirq'. Unf

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

am including the dmesg log of my system with this message. I am CC'ing > the linux-ide list, but I'm only subscribed to linux-kernel. I would > appreciate CC's, if possible. > > > Thank you very much for any help, Rog?rio. > > P.S.: I am, right now,

Re: 2.6.11-rc3-mm1

On Wed, Feb 09, 2005 at 08:12:07PM -0800, Andrew Morton wrote: > (I understand that it's only a "proof of concept" patch, but I thought I'd > bitch anyway ;)) > > So. I'll keep the patch as-is in -mm for now. I've Cc'ed linux-acpi. > Perhaps the people there can absorb this and fix it up for re

Re: 2.6.11-rc3-mm1

"Marcos D. Marado Torres" <[EMAIL PROTECTED]> wrote: > > Please add to -mm the patch in attachment, since it solves the old > acpi_power_off bug... > > ... > diff -Nru -p1 linux-2.6.11-rc2-mm1/drivers/base/power/shutdown.c > linux-2.6.11-rc2-mm1-mbn1/drivers/base/power/shutdown.c > --- linux-

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume [update]

d the warining. > > > > > > BTW, I've also tried to put touch_softlockup_watchdog() before > > > device_power_up(), but it didn't change much. > > > > this is a single-CPU box, right? > > Yes. > > OK, I think I've sorted it out. The s

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

t; device_power_up(), but it didn't change much. > > this is a single-CPU box, right? Yes. OK, I think I've sorted it out. The solution is to use your patch and the following change against swsusp.c: --- linux-2.6.11-rc3-mm1-orig/kernel/power/swsusp.c 2005-02-08 18:16:34

Re: 2.6.11-rc3-mm1

On Tue, Feb 08, 2005 at 08:54:06PM -0800, Andrew Morton wrote: > "Marcos D. Marado Torres" <[EMAIL PROTECTED]> wrote: > > > > Please add to -mm the patch in attachment, since it solves the old > > acpi_power_off bug... > > What acpi_power_off bug? And how does it solve it? Here's the observed b

Re: 2.6.11-rc3-mm1: two oops on startup

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/2005 03:09 PM, Andrew Morton wrote: > Clemens Schwaighofer <[EMAIL PROTECTED]> wrote: > >>during startup I get too oops on my Box > > > Yes, it is being worked on. You'll need to CONFIG_INOTIFY=n, thanks. okay, thanks. - -- [ Clemens Sch

Re: 2.6.11-rc3-mm1: two oops on startup

Clemens Schwaighofer <[EMAIL PROTECTED]> wrote: > > during startup I get too oops on my Box Yes, it is being worked on. You'll need to CONFIG_INOTIFY=n, thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo i

Re: 2.6.11-rc3-mm1: two oops on startup

6-17-2 Ginza Chuo-ku, Tokyo 104-0061, JAPAN ] [ Tel: +81-(0)3-3545-7703Fax: +81-(0)3-3545-7343 ] [ http://www.tequila.co.jphttp://www.tbwajapan.co.jp ] # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-mm1 # Wed Feb 9 12:39:10 2

Re: 2.6.11-rc3-mm1

On Wed, 9 Feb 2005, Marcos D. Marado Torres wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Fri, 4 Feb 2005, Andrew Morton wrote: > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > > Andrew, > &g

Re: 2.6.11-rc3-mm1

"Marcos D. Marado Torres" <[EMAIL PROTECTED]> wrote: > > Please add to -mm the patch in attachment, since it solves the old > acpi_power_off bug... What acpi_power_off bug? And how does it solve it? Thanks. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

Re: 2.6.11-rc3-mm1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 4 Feb 2005, Andrew Morton wrote: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ Andrew, Please add to -mm the patch in attachment, since it solves the old acpi_power_off bug... Best Regards, Marcos

Re: 2.6.11-rc3-mm1

o_getname: init seg:1 page:df404000 filename: len:4096 Unable to handle kernel NULL pointer dereference at virtual address printing eip: c01d8257 *pde = Oops: [#1] PREEMPT Modules linked in: CPU:0 EIP:0060:[]Not tainted V

Re: [PATCH] fix ACPI_BOOT for ia64 (2.6.11-rc3-mm1)

On Tue, Feb 08, 2005 at 03:03:38PM -0500, Martin Hicks wrote: > > Hi Andrew, > > One of your patches in 2.6.11-rc3-mm1 breaks ACPI_BOOT for ia64. It > removes the dependence on CONFIG_ACPI and makes it exclusively depend on > X86_HT, which is wrong. Thanks for the patch. A

[PATCH] fix ACPI_BOOT for ia64 (2.6.11-rc3-mm1)

Hi Andrew, One of your patches in 2.6.11-rc3-mm1 breaks ACPI_BOOT for ia64. It removes the dependence on CONFIG_ACPI and makes it exclusively depend on X86_HT, which is wrong. Signed-off-by: Martin Hicks <[EMAIL PROTECTED]> Index: linux-2.6.11-rc3-mm1/drivers/acpi/K

[PATCH 2.6.11-rc3-mm1] add TANBAC TB0219 base board driver

This patch adds GPIO/LED/DIPSW driver for TANBAC TB0219. Yoichi Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]> diff -urN -X dontdiff a-orig/arch/mips/Kconfig a/arch/mips/Kconfig --- a-orig/arch/mips/KconfigTue Feb 8 00:19:49 2005 +++ a/arch/mips/Kconfig Tue Feb 8 00:53:47 2005 @@ -122,10

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > The warning is printed right after the image is restored (ie somewhere > around the local_irq_enable() above, but it goes before the "PM: Image > restored successfully." message that is printed as soon as the return > is executed). Definitely, les

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

On Tue, Feb 08 2005, Andrew Morton wrote: > Jens Axboe <[EMAIL PROTECTED]> wrote: > > > > > ->axboe! > > > > :-) > > > > The thing wants a rewrite. Ideally the serializing point would be a > > special request. The patch is still better than nothing right now, it's > > really easy to

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

Jens Axboe <[EMAIL PROTECTED]> wrote: > > >->axboe! > > :-) > > The thing wants a rewrite. Ideally the serializing point would be a > special request. The patch is still better than nothing right now, it's > really easy to hang the device with hdparm in -linus since it's > impos

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

On Tue, Feb 08 2005, Andrew Morton wrote: > Maciej Soltysiak <[EMAIL PROTECTED]> wrote: > > > > Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady > > SeekComplete Error } > > Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError > > BadCRC } > > Feb 6 17:07

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

Maciej Soltysiak <[EMAIL PROTECTED]> wrote: > > Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady > SeekComplete Error } > Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError > BadCRC } > Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown > Feb

Re: [RFC][PATCH 2.6.11-rc3-mm1] Relay Fork Module

On Mon, 2005-02-07 at 15:46 -0800, Andrew Morton wrote: > Guillaume Thouvenin <[EMAIL PROTECTED]> wrote: > > > >This module sends a signal to one or several processes (in user > > space) when a fork occurs in the kernel. It relays information about > > forks (parent and child pid) to a user sp

Re: [RFC][PATCH 2.6.11-rc3-mm1] Relay Fork Module

Guillaume Thouvenin <[EMAIL PROTECTED]> wrote: > > Hello, > >This module sends a signal to one or several processes (in user > space) when a fork occurs in the kernel. It relays information about > forks (parent and child pid) to a user space application. > > ... >This patch is used

Re[2]: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

Hello Hans, Monday, February 7, 2005, 9:19:47 PM, you wrote: > Maciej Soltysiak wrote: >>) >> >>Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady >>SeekComplete Error } >>Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError >>BadCRC } >> >> > this means

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

Maciej Soltysiak wrote: ) Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } this means bad hard drive, or at least a bad sector on it. - To unsubscribe from this list: send th

Re: 2.6.11-rc3-mm1

On Sun, 2005-02-06 at 22:22 +0100, Peter Osterlund wrote: > > > > EIP is a strncpy_from_user+0x33/0x47 > > > > ... > > > > Call Trace: > > > > getname+0x69/0xa5 > > > > sys_open+0x12/0xc6 > > > > sysenter_past_esp+0x52/0x75 > > > > ... > >

[PATCH 2.6.11-rc3-mm1] pcmcia: update vrc4171_card

This patch updates vrc4171 pcmcia driver. Yoichi Signed-off-by: Yoichi Yuasa <[EMAIL PROTECTED]> diff -urN -X dontdiff a-orig/arch/mips/vr41xx/common/Makefile a/arch/mips/vr41xx/common/Makefile --- a-orig/arch/mips/vr41xx/common/Makefile Thu Feb 3 10:55:52 2005 +++ a/arch/mips/vr41xx/commo

[RFC][PATCH 2.6.11-rc3-mm1] Relay Fork Module

module or directly in the kernel. This patch is used by the Enhanced Linux System Accounting tool that can be downloaded from http://elsa.sf.net Regards, Guillaume $ diffstat linux-2.6.11-rc3-mm1-relayfork.patch include/linux/generic_hooks.h |9 init/Kconfig | 25 ++

[PATCH 2.6.11-rc3-mm1] mips: add unknown page size string

This patch had fixed the following warning. arch/mips/lib-32/dump_tlb.c: In function 'dump_tlb': arch/mips/lib-32/dump_tlb.c:69: warning: control may reach end of non-void function 'msk2str' being inlined This patch adds return value, when page size is not match. Yoichi Signed-off-by: Yoichi Y

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

gt; I did: > > > > --- > > /home/rafael/tmp/kernel/testing/linux-2.6.11-rc3-mm1/kernel/power/swsusp.c > > 2005-02-05 20:57:03.0 +0100 > > +++ linux-2.6.11-rc3-mm1/kernel/power/swsusp.c 2005-02-06 > > 19:07:39.0 +0100 &

Re: 2.6.11-rc3-mm1 - broken bttv ?

Paulo Marques wrote: jjluza wrote: Eyal Lebedinsky wrote I am having bttv problems with vanilla -rc3. Does it work for you? I don't know, as I said I didn't test kernel between 2.6.10 and 2.6.11-rc3-mm1. Sorry. If I have time enough later, I can test 2.6.11-rc3. Since I don't real

Re: 2.6.11-rc3-mm1 - broken bttv ?

jjluza wrote: Eyal Lebedinsky wrote I am having bttv problems with vanilla -rc3. Does it work for you? I don't know, as I said I didn't test kernel between 2.6.10 and 2.6.11-rc3-mm1. Sorry. If I have time enough later, I can test 2.6.11-rc3. Since I don't really know if it'

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > ah, ok. Could you try my patch and add touch_softlockup_watchdog() to > > the resume code (before interrupts are re-enabled)? > > I did: > > --- > /home/rafael/tmp/kernel/testing/linux-2.6.11-rc3-mm1/kernel/po

2.6.11-rc3-mm1 bad scheduling while atomic + lockup

Hello, I just want to report a lockup on my 2.6.11-rc3-mm1 machine. I was working on it via ssh and suddenly the machine stopped responding. When, the next day I came up to the console it was printing over and over this oops. In the logs I could find the oops. I am posting it inline here along

Re: 2.6.11-rc3-mm1

rnel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > > > > > > It gives me a kernel panic at boot if I have CONFIG_FB_RADEON > > > enabled. If I also have CONFIG_FRAMEBUFFER_CONSOLE enabled, I get this > > > output: > >

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

ge) is > > considered as spent in the kernel, so it triggers softlockup as soon > > as its threads are woken up (is that correct, Pavel?). > > ah, ok. Could you try my patch and add touch_softlockup_watchdog() to > the resume code (before interrupts are re-enabled)? I did

Re: 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state

Le 06.02.2005 09:18, Peter Osterlund a écrit : [snip] Anyway, the problem is that the add-struct-request-end_io-callback patch forgot to update pktcdvd.c. This patch fixes it. It should probably be merged into the add-struct-request-end_io-callback patch, because that patch already fixes up other s

Re: 2.6.11-rc3-mm1

On Sun, Feb 06, 2005 at 09:33:44PM +1100, Benjamin Herrenschmidt wrote: > On Sun, 2005-02-06 at 11:07 +0100, Peter Osterlund wrote: > > Andrew Morton <[EMAIL PROTECTED]> writes: > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11

Re: 2.6.11-rc3-mm1

Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes: > On Sun, 2005-02-06 at 11:07 +0100, Peter Osterlund wrote: > > Andrew Morton <[EMAIL PROTECTED]> writes: > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ &g

Re: 2.6.11-rc3-mm1

On Sun, 2005-02-06 at 11:07 +0100, Peter Osterlund wrote: > Andrew Morton <[EMAIL PROTECTED]> writes: > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > > It gives me a kernel panic at boot if I have CONFIG_FB_RADEON &

Re: 2.6.11-rc3-mm1

Andrew Morton <[EMAIL PROTECTED]> writes: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ It gives me a kernel panic at boot if I have CONFIG_FB_RADEON enabled. If I also have CONFIG_FRAMEBUFFER_CONSOLE enabled, I get this output:

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

passed to the kernel. Would there be anything else that I should try? Thank you very much for the help, Rogério. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogério Brito - [EMAIL PROTECTED] - http://www.ime.usp.br/~rbrito =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Linux version

Re: 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state

Andrew Morton <[EMAIL PROTECTED]> writes: > Peter Osterlund <[EMAIL PROTECTED]> wrote: > > > > Peter Osterlund <[EMAIL PROTECTED]> writes: > > > > > Laurent Riffard <[EMAIL PROTECTED]> writes: > > > > > > > This is k

Re: 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state

Peter Osterlund <[EMAIL PROTECTED]> wrote: > > Peter Osterlund <[EMAIL PROTECTED]> writes: > > > Laurent Riffard <[EMAIL PROTECTED]> writes: > > > > > This is kernel 2.6.11-rc3-mm1. I can't mount an UDF-formatted cdrw > > &g

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

am including the dmesg log of my system with this message. I am CC'ing > the linux-ide list, but I'm only subscribed to linux-kernel. I would > appreciate CC's, if possible. > > > Thank you very much for any help, Rog?rio. > > P.S.: I am, right now, re-compili

Re: 2.6.11-rc3-mm1 - broken bttv ?

Eyal Lebedinsky wrote > > I am having bttv problems with vanilla -rc3. Does it work for you? I don't know, as I said I didn't test kernel between 2.6.10 and 2.6.11-rc3-mm1. Sorry. If I have time enough later, I can test 2.6.11-rc3. Since I don't really know if it's th

Re: 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state

Peter Osterlund <[EMAIL PROTECTED]> writes: > Laurent Riffard <[EMAIL PROTECTED]> writes: > > > This is kernel 2.6.11-rc3-mm1. I can't mount an UDF-formatted cdrw > > in packet-writing mode. Mount process gets stuck in D state. > > > > Mountin

Re: 2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state

Laurent Riffard <[EMAIL PROTECTED]> writes: > This is kernel 2.6.11-rc3-mm1. I can't mount an UDF-formatted cdrw > in packet-writing mode. Mount process gets stuck in D state. > > Mounting and writing this media in packet-writing mode works fine > with kernel 2.6.11-r

Re: 2.6.11-rc3-mm1 - broken bttv ?

jjluza wrote: I have a problem with my bttv card, I get these error messages when I try to access the TV device (and of course I can't watch TV) : I am having bttv problems with vanilla -rc3. Does it work for you? -- Eyal Lebedinsky ([EMAIL PROTECTED]) attach .zip

Re: irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

On Feb 05 2005, Rogério Brito wrote: > I am including the dmesg log of my system with this message. (...) Ooops! Forgot to include the dmesg in the previous message. :-( Thanks again, Rogério. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogério Brito - [EMAIL PRO

irq 10: nobody cared! (was: Re: 2.6.11-rc3-mm1)

iate CC's, if possible. Thank you very much for any help, Rogério. P.S.: I am, right now, re-compiling 2.6.11-rc3-mm1 with the extra pass of kallsyms to see if the problem persists with this release. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Rogério Brito -

Re: 2.6.11-rc3-mm1

On Sat, 2005-02-05 at 10:48 +, Sean Neakums wrote: > Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]> writes: > > > On Sat, 05 Feb 2005 11:16:49 +1100, Benjamin Herrenschmidt > > <[EMAIL PROTECTED]> wrote: > >> > >> > I tried it two or three times, same result each time. I'll give it a > >> > l

Re: 2.6.11-rc3-mm1

On Feb 05 2005, Jurriaan wrote: > From: Rogério Brito <[EMAIL PROTECTED]> > Date: Sat, Feb 05, 2005 at 04:10:18PM -0200 > > Inconsistent kallsyms data > > Try setting CONFIG_KALLSYMS_EXTRA_PASS > > make[1]: *** [vmlinux] Error 1 > > make[1]: Leaving directory `/usr/local/media/progs/linux/kernel/li

Re: 2.6.11-rc3-mm1 : can't insmod dm-mod

On Sat, Feb 05, 2005 at 04:29:45PM +, Christoph Hellwig wrote: > On Sat, Feb 05, 2005 at 03:26:05AM -0800, Andrew Morton wrote: > > You've enabled CONFIG_BASE_SMALL and so the major_names[] hashtable has > > just one element. device-mapper uses dynamic major allocation, the range > > of which

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

Hi! > > > It looks like softlockup is not happy with suspend/resume: > > > > Does it happen while writing out state to disk? > > No, it occurs during resume, right after the image has been restored (sorry, > I should have said this before). > > > I've attached a patch for touch_softlockup_watch

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

Hi! > > It looks like softlockup is not happy with suspend/resume: > > Does it happen while writing out state to disk? I've attached a patch > for touch_softlockup_watchdog() below - but i think what we really need > is another mechanism. I'm wondering what the primary reason for the > lockup-det

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > I've attached a patch for touch_softlockup_watchdog() below - but i think > > what we really need is another mechanism. I'm wondering what the primary > > reason for the lockup-detection is - did swsuspend stop the the softlockup > > threads? >

Re: 2.6.11-rc3-mm1

From: Rog?rio Brito <[EMAIL PROTECTED]> Date: Sat, Feb 05, 2005 at 04:10:18PM -0200 > > I'm having problems when trying to get 2.6.11-rc3-mm1 compiled. The build > breaks with the message being thrown: > > Inconsistent kallsyms data > Try setting CONFIG

Re: 2.6.11-rc3-mm1 - broken bttv ?

x27;t test other kernel version between 2.6.10 and 2.6.11-rc3-mm1) See attachment for the kernel configuration # # Automatically generated make config: don't edit # Linux kernel version: 2.6.11-rc3-mm1 # Fri Feb 4 19:46:41 2005 # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DM

Re: 2.6.11-rc3-mm1

I'm having problems when trying to get 2.6.11-rc3-mm1 compiled. The build breaks with the message being thrown: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - (...) LD .tmp_vmlinux1 KSYM.tmp_kallsyms1.S AS .tmp_kallsyms1.o LD .tmp_vml

Oops on 2.6.11-rc3-mm1

I hit the following oops on 2.6.11-rc3-mm1. I was previously running -rc2-mm2 with no problems. Rgds, Grant Wilson Feb 5 02:43:21 tlg kernel: Unable to handle kernel paging request at 2e16f000 RIP: Feb 5 02:43:21 tlg kernel: {copy_user_generic_c+8} Feb 5 02:43:21 tlg kernel: PGD

2.6.11-rc3-mm1 : mount UDF CDRW stuck in D state

Hello, This is kernel 2.6.11-rc3-mm1. I can't mount an UDF-formatted cdrw in packet-writing mode. Mount process gets stuck in D state. Mounting and writing this media in packet-writing mode works fine with kernel 2.6.11-rc2-mm2. Mounting and reading this media in normal mode (/dev/hdd on

Re: 2.6.11-rc3-mm1 : can't insmod dm-mod

On Sat, Feb 05, 2005 at 03:26:05AM -0800, Andrew Morton wrote: > You've enabled CONFIG_BASE_SMALL and so the major_names[] hashtable has > just one element. device-mapper uses dynamic major allocation, the range > of which is limited to the size of the top-level major_names[] array. You > ran out

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

On Saturday, 5 of February 2005 15:35, Ingo Molnar wrote: > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > It looks like softlockup is not happy with suspend/resume: > > Does it happen while writing out state to disk? No, it occurs during resume, right after the image has been restored

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

* Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > It looks like softlockup is not happy with suspend/resume: Does it happen while writing out state to disk? I've attached a patch for touch_softlockup_watchdog() below - but i think what we really need is another mechanism. I'm wondering what the p

Re: 2.6.11-rc3-mm1 : can't insmod dm-mod

Le 05.02.2005 12:26, Andrew Morton a écrit : Laurent Riffard <[EMAIL PROTECTED]> wrote: Le 04.02.2005 19:33, Andrew Morton a écrit : > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > loading dm-mod module fails with this message : FATAL: Err

Re: 2.6.11-rc3-mm1: softlockup and suspend/resume

tainted 2.6.11-rc3-mm1 Feb 5 02:16:12 albercik kernel: RIP: 0010:[] {swsusp_suspend+52} Feb 5 02:16:13 albercik kernel: RSP: :81000d51de38 EFLAGS: 0292 Feb 5 02:16:18 albercik kernel: RAX: RBX: 80427fc0 RCX: 803f263e Feb 5 02:16:20 albercik kernel: RDX

Re: 2.6.11-rc3-mm1: kobject_register fails for processor on Athlon64

On Friday, 4 of February 2005 19:33, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ This occurs on my box (Athlon64-based) if "processor" is directly compiled into the kernel: ACPI: Lid Switch [LID] ACPI:

Re: 2.6.11-rc3-mm1

On Fri, Feb 04, 2005 at 10:33:50AM -0800, Andrew Morton wrote: > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > - The bk-usb and bk-pci and bk-driver-core trees have been temporarily > dropped from -mm, for they are not healthy at present.

Re: 2.6.11-rc3-mm1 : can't insmod dm-mod

Laurent Riffard <[EMAIL PROTECTED]> wrote: > > Le 04.02.2005 19:33, Andrew Morton a écrit : > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > > > > loading dm-mod module fails with this message : > >

Re: 2.6.11-rc3-mm1

eset()-removal, I got an Oops on suspend, reproduced below. I then received Bartlomiej's patch, which I applied to a clean 2.6.11-rc3-mm1 tree. Same USB Oops, no suspend. Then I disabled USB, and suspend/resume worked. I can still try the openpic_reset()-removal in a clean tree with U

Re: [patch] 2.6.11-rc3-mm1: fix swsusp with gcc 3.4

Pavel > Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]> > > --- linux-2.6.11-rc3-mm1/kernel/power/swsusp.c2005-02-04 > 22:33:52.0 +0100 > +++ new/kernel/power/swsusp.c 2005-02-04 22:32:36.0 +0100 > @@ -614,9 +614,9 @@ > stru

2.6.11-rc3-mm1 : can't insmod dm-mod

Le 04.02.2005 19:33, Andrew Morton a écrit : ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ loading dm-mod module fails with this message : FATAL: Error inserting dm-mod (/lib/modules/2.6.11-rc3-mm1/kernel/drivers/md/dm-mod.ko): Device or resource busy

bk-usb is now safe (was 2.6.11-rc3-mm1)

On Fri, Feb 04, 2005 at 10:33:50AM -0800, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > > > - The bk-usb and bk-pci and bk-driver-core trees have been temporarily > dropped from -mm, for they are not healt

Re: 2.6.11-rc3-mm1

On Sat, 05 Feb 2005 11:16:49 +1100, Benjamin Herrenschmidt <[EMAIL PROTECTED]> wrote: > > > I tried it two or three times, same result each time. I'll give it a > > lash with USB disabled. > > Also, can you try editing arch/ppc/syslib/open_pic.c, in function > openpic_resume(), comment out the c

Re: 2.6.11-rc3-mm1

On Fri, 2005-02-04 at 22:17 +, Sean Neakums wrote: > I gave this a crack on the PowerBook5.4 -- somewhat more successful > than 2.6.11-rc2-mm2. It boots, radeonfb works and X starts. However, > suspend seems a tad faster than usual, and resume stops after setting > the hard disk's DMA mode, a

Re: 2.6.11-rc3-mm1

> I tried it two or three times, same result each time. I'll give it a > lash with USB disabled. Also, can you try editing arch/ppc/syslib/open_pic.c, in function openpic_resume(), comment out the call to openpic_reset() and let me know if that helps... Ben. - To unsubscribe from this list: s

Re: 2.6.11-rc3-mm1

Benjamin Herrenschmidt <[EMAIL PROTECTED]> writes: > On Fri, 2005-02-04 at 22:17 +, Sean Neakums wrote: >> I gave this a crack on the PowerBook5.4 -- somewhat more successful >> than 2.6.11-rc2-mm2. It boots, radeonfb works and X starts. However, >> suspend seems a tad faster than usual, and

Re: 2.6.11-rc3-mm1: device_resume() hangs on Athlon64

On Friday, 4 of February 2005 19:33, Andrew Morton wrote: > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ > On my box (Athlon64-based) swsusp hangs forever in device_resume() called from swsusp_write(), although interrupts are apparentl

Re: 2.6.11-rc3-mm1 (compile stats)

linux1] Error 1 (ignored) > > > > hm. You must have CONFIG_SYSCTL=n? > > > > I'll fix that up. > > CONFIG_SYSCTL=n in the allnoconfig build, which I would expect. > > http://developer.osdl.org/cherry/compile/2.6/linux-2.6.11-rc3-mm1.results/2.6.11-

Re: 2.6.11-rc3-mm1

I gave this a crack on the PowerBook5.4 -- somewhat more successful than 2.6.11-rc2-mm2. It boots, radeonfb works and X starts. However, suspend seems a tad faster than usual, and resume stops after setting the hard disk's DMA mode, although the log below made it to disk. eth0: suspending, Wak

Re: [patch] 2.6.11-rc3-mm1: fix swsusp with gcc 3.4

fix > >... > > This broke compilation with gcc 3.4: [-- snip --] BTW, it requires the following bugfix, on top of the Adrian's patch. Greets, Rafael Signed-off-by: Rafael J. Wysocki <[EMAIL PROTECTED]> --- linux-2.6.11-rc3-mm1/kernel/power/swsusp.c 2005-02-04 22:33:52.000

Re: 2.6.11-rc3-mm1 (compile stats)

es bzImage modules (defconfig) (allno) (allyes) (allyes) (allmod) (allmod) --- -- ---- ---- ---- 2.6.11-rc3-mm1 13w/10e0w/7e 196w/12e 6w/0e 18w/12e 177w/0e 2.6.11-rc2-mm2 15w/0e 0w/0e 201w/0e6w/0e 18w/0e182w/0e 2.6.11-rc2-mm

Re: 2.6.11-rc3-mm1 (compile stats)

John Cherry <[EMAIL PROTECTED]> wrote: > > Errors in the build relate to an undefined reference to > "randomize_va_space"... > >LD init/built-in.o >LD .tmp_vmlinux1 > arch/i386/kernel/built-in.o(.text+0xf92): In function `arch_align_stack': > : undefined reference to `randomi

[patch] 2.6.11-rc3-mm1: fix swsusp with gcc 3.4

wsusp.o] Error 1 <-- snip --> The fix is simple: Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]> --- kernel/power/swsusp.c | 30 ++ 1 files changed, 14 insertions(+), 16 deletions(-) --- linux-2.6.11-rc3-mm1-full/kernel/power/swsusp.c.old 2005-02

2.6.11-rc3-mm1

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm1/ - The bk-usb and bk-pci and bk-driver-core trees have been temporarily dropped from -mm, for they are not healthy at present. - After many months dormancy, the ieee1394 tree is back and is included in

[compile fix] 2.6.11-rc3-mm1 (acpi Kconfig)

Hi Andrew, I had the following errors while compiling 2.6.11-rc3-mm1: In file included from include/asm/fixmap.h:27, from arch/i386/kernel/asm-offsets.c:12: include/asm/acpi.h: In function `acpi_noirq_set': include/asm/acpi.h:160:

[patch] inotify for 2.6.11-rc3-mm1

h| 119 include/linux/miscdevice.h |1 include/linux/sched.h |2 kernel/user.c |2 18 files changed, 1530 insertions(+), 63 deletions(-) diff -urN linux-2.6.11-rc3-mm1/arch/sparc64/Kconfig linux-mm/arch/sparc64/Kconfig --- linux-2.6.11-rc3-mm1/arch/spa