[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)

On Sat, Feb 05, 2005 at 08:45:58PM -0200, Rog?rio Brito wrote: > Dear developers, > > 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!". > > The message says that I should pass the irqp

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]

On Wednesday, 9 of February 2005 17:35, Rafael J. Wysocki wrote: > On Tuesday, 8 of February 2005 12:04, Ingo Molnar wrote: > > > > * Rafael J. Wysocki <[EMAIL PROTECTED]> wrote: > > > > > The warning is printed right after the image is restored (ie somewhere > > > around the local_irq_enable() a

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

On Tuesday, 8 of February 2005 12:04, Ingo Molnar wrote: > > * 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 t

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

Hi, during startup I get too oops on my Box. It's a debian/unstable. dmesg from right after the start and the kernel config are attached. -- [ Clemens Schwaighofer -=:~ ] [ TBWA\ && TEQUILA\ Japan IT Group ] [6-17-2 Ginza

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, > > Please add to -mm the patch in attach

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 Marad

Re: 2.6.11-rc3-mm1

Robert Love <[EMAIL PROTECTED]> writes: > 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 > > > > >

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: 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 > > > > ... > >

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

On Monday, 7 of February 2005 09:57, Ingo Molnar wrote: > > * 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/ker

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 really know if it's

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's the good place to tal

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/power/swsusp.c > 2005-02-05

Re: 2.6.11-rc3-mm1

Peter Osterlund <[EMAIL PROTECTED]> writes: > 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/

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

Hi, On Saturday, 5 of February 2005 20:07, Ingo Molnar wrote: > > * 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 l

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-rc3-mm1/ > > > > It gives me

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/ > > > > It gives me a kernel panic at bo

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 > enabled. If I also have CONFIG_F

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: Unable to hand

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

On Feb 05 2005, William Park wrote: > On Sat, Feb 05, 2005 at 08:45:58PM -0200, Rogério Brito wrote: > > The message seems to be related to the Promise PDC20265 driver and it > > appeared right after I moved my HDs from my motherboard's VIA controllers > > to the Promise controllers. I have an Asus

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 kernel 2.6.11-rc3-mm1. I can't mount an UDF-formatted cdrw > > > > in packet-writ

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 > > > in packet-writing mode. Mount process gets stuck in D state. > > > > > >

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

On Sat, Feb 05, 2005 at 08:45:58PM -0200, Rog?rio Brito wrote: > Dear developers, > > 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!". > > The message says that I should pass the irqp

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 the good place to talk about 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. > > > > Mounting and writing this media in packet-writing mode works

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-rc2-mm2. I tried to repeat th

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)

Dear developers, 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!". The message says that I should pass the irqpoll option to the kernel and even if I do, I still get the stack trace and th

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_KALLSYMS_EXTRA_PASS > make[1]: *** [vmlinux

Re: 2.6.11-rc3-mm1 - broken bttv ?

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) : Feb 5 17:43:57 client kernel: tuner: i2c i/o error: rc == -121 (should be 4) Feb 5 17:44:05 client last message repeated 4 times Feb 5 17:44:48 client kernel: bt

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_vmlinux2

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: Error inserting d

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

Hi, It looks like softlockup is not happy with suspend/resume: Feb 5 02:16:06 albercik kernel: BUG: soft lockup detected on CPU#0! Feb 5 02:16:06 albercik kernel: Feb 5 02:16:06 albercik kernel: Modules linked in: snd_seq snd_seq_device usbserial parport_pc lp parport thermal processor fan bu

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: Fan [FN00] (off) kobject

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. > - After man

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 : > > FATAL: Error inserting dm-mod > (/lib/module

Re: 2.6.11-rc3-mm1

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 >> > lash with USB disabled. >> >> Also, can you try editing arch/ppc/sysl

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 apparently handled norma

Re: 2.6.11-rc3-mm1 (compile stats)

On Fri, 2005-02-04 at 13:51 -0800, John Cherry wrote: > On Fri, 2005-02-04 at 13:13 -0800, Andrew Morton wrote: > > John Cherry <[EMAIL PROTECTED]> wrote: > > > > > > Errors in the build relate to an undefined reference to > > > "randomize_va_space"... > > > > > >LD init/built-in.o > >

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: 2.6.11-rc3-mm1 (compile stats)

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 `randomize_va_space' make: [.tmp_vmlinux1] Error 1 (ignored) ---

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