13 Dec, 2005

1 commit

  • This has been broken for months. On resume, we call acpi_pci_link_set()
    with interrupts off, so we get a warning when we try to do a kmalloc of non
    atomic memory. The actual allocation is just 2 long's (plus extra byte for
    some reason I can't fathom), so a simple conversion to GFP_ATOMIC is
    probably the safest way to fix this.

    The error looks like this..

    Debug: sleeping function called from invalid context at mm/slab.c:2486
    in_atomic():0, irqs_disabled():1
    [] kmem_cache_alloc+0x40/0x56
    [] acpi_pci_link_set+0x3f/0x17f
    [] irqrouter_resume+0x1e/0x3c
    [] __sysdev_resume+0x11/0x6b
    [] sysdev_resume+0x34/0x52
    [] device_power_up+0x5/0xa

    Signed-off-by: Dave Jones
    Cc: "Brown, Len"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Dave Jones
     

05 Aug, 2005

4 commits


04 Aug, 2005

2 commits


03 Aug, 2005

1 commit


02 Aug, 2005

1 commit

  • If there are devices that use interrupts over a suspend event, ACPI must
    restore the PCI interrupt links on resume. Anything else breaks any
    device that hasn't been converted to the new (dubious) PM rules.

    Drivers that need the irq free/re-aquire sequence can be done one by one
    independently of this one.

    Linus Torvalds
     

30 Jul, 2005

1 commit


12 Jul, 2005

2 commits

  • http://bugme.osdl.org/show_bug.cgi?id=4016

    Written-by: David Shaohua Li
    Acked-by: Adam Belay
    Signed-off-by: Len Brown

    David Shaohua Li
     
  • Delete PCI Interrupt Link Device .resume method --
    it is the device driver's job to request interrupts,
    not the Link's job to remember what the devices want.

    This addresses the issue of attempting to run
    the ACPI interpreter too early in resume, when
    interrupts are still disabled.

    http://bugzilla.kernel.org/show_bug.cgi?id=3469

    Signed-off-by: David Shaohua Li
    Signed-off-by: Len Brown

    David Shaohua Li
     

17 Apr, 2005

1 commit

  • Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds