Re: suspend - Kernel

This is a discussion on Re: suspend - Kernel ; On Wednesday, 2 of April 2008, Justin Mattock wrote: > Hello; attached is my results with testing 2.6.25-rc8 with echo mem > > /sys/power/state > hopefully this helps in debugging the issues with the imac. > I'm running a macbook ...

+ Reply to Thread
Results 1 to 15 of 15

Thread: Re: suspend

  1. Re: suspend

    On Wednesday, 2 of April 2008, Justin Mattock wrote:
    > Hello; attached is my results with testing 2.6.25-rc8 with echo mem >
    > /sys/power/state
    > hopefully this helps in debugging the issues with the imac.
    > I'm running a macbook pro 15' with the ATI chipset.
    > regards;


    Well, I don't see anything particularly wrong in the log you sent.

    Wnat exactly is wrong with the box after a resume?

    Rafael
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: suspend

    Hello; the only problems I see after a suspend is the appletouch
    looses its scroll function, as well as the bluetooth mighty
    mouse(probably dont have my xorg.conf set up for suspend),
    wpa_supplicant seems to not respond as well.
    also here is what I see with sata: ( revalidation failed?)

    [ 1233.811794] sd 2:0:1:0: [sda] Starting disk
    [ 1234.013599] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
    [ 1234.013601] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 filtered out
    [ 1234.180232] ata1.00: configured for UDMA/66
    [ 1222.732011] ata3.01: NODEV after polling detection
    [ 1222.732016] ata3.01: revalidation failed (errno=-2)
    [ 1222.732020] ata3: failed to recover some devices, retrying in 5 secs
    [ 1227.908752] ata3.01: ACPI cmd ef/03:0c:00:00:00:b0 filtered out
    [ 1227.908758] ata3.01: ACPI cmd ef/03:45:00:00:00:b0 filtered out
    [ 1227.922377] ata3.01: configured for UDMA/100
    [ 1227.945525] sd 2:0:1:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
    [ 1227.945525] sd 2:0:1:0: [sda] Write Protect is off
    [ 1227.945525] sd 2:0:1:0: [sda] Mode Sense: 00 3a 00 00
    [ 1227.945525] sd 2:0:1:0: [sda] Write cache: enabled, read cache:
    enabled, doesn't support DPO or FUA
    [ 1227.945525] applesmc: device has already been initialized (0xe0, 0x00).

    Other than that it seems to work alright.
    regards;

    Justin P. Mattock

    On Wed, Apr 2, 2008 at 12:19 PM, Rafael J. Wysocki wrote:
    >
    > On Wednesday, 2 of April 2008, Justin Mattock wrote:
    > > Hello; attached is my results with testing 2.6.25-rc8 with echo mem >
    > > /sys/power/state
    > > hopefully this helps in debugging the issues with the imac.
    > > I'm running a macbook pro 15' with the ATI chipset.
    > > regards;

    >
    > Well, I don't see anything particularly wrong in the log you sent.
    >
    > Wnat exactly is wrong with the box after a resume?
    >
    > Rafael
    >




    --
    Justin P. Mattock
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: suspend

    On Wednesday, 2 of April 2008, Justin Mattock wrote:
    > Hello; the only problems I see after a suspend is the appletouch
    > looses its scroll function,


    Is that a USB device or some other kind?

    > as well as the bluetooth mighty mouse(probably dont have my xorg.conf set up
    > for suspend),


    That might be related to the issue that Pavel is fighting with.

    > wpa_supplicant seems to not respond as well.


    What wireless adapter is there in your box?

    > also here is what I see with sata: ( revalidation failed?)


    Let's Cc the SATA people.

    > [ 1233.811794] sd 2:0:1:0: [sda] Starting disk
    > [ 1234.013599] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
    > [ 1234.013601] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 filtered out
    > [ 1234.180232] ata1.00: configured for UDMA/66
    > [ 1222.732011] ata3.01: NODEV after polling detection
    > [ 1222.732016] ata3.01: revalidation failed (errno=-2)
    > [ 1222.732020] ata3: failed to recover some devices, retrying in 5 secs
    > [ 1227.908752] ata3.01: ACPI cmd ef/03:0c:00:00:00:b0 filtered out
    > [ 1227.908758] ata3.01: ACPI cmd ef/03:45:00:00:00:b0 filtered out
    > [ 1227.922377] ata3.01: configured for UDMA/100
    > [ 1227.945525] sd 2:0:1:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
    > [ 1227.945525] sd 2:0:1:0: [sda] Write Protect is off
    > [ 1227.945525] sd 2:0:1:0: [sda] Mode Sense: 00 3a 00 00
    > [ 1227.945525] sd 2:0:1:0: [sda] Write cache: enabled, read cache:
    > enabled, doesn't support DPO or FUA
    > [ 1227.945525] applesmc: device has already been initialized (0xe0, 0x00).
    >
    > Other than that it seems to work alright.


    OK

    Thanks,
    Rafael
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: suspend

    On Wednesday, 2 of April 2008, Justin Mattock wrote:
    > Hello; I did some testing with the suspend and it seems the mighty
    > mouse is being claimed by something before bluetooth daemon can claim
    > it. the infrared device gives me no response even after issuing
    > killall lirc and lircd and restarting the daemons,
    > I'm able to get uvcvideo working after a rrmod uvcvideo then a
    > modprobe uvcvideo then I'm able to use gmplayer tv:// -vf mirror to
    > view the camera. with appletouch i have to ctrl,alt,del then rmmod
    > appletouch then modprobe and startx for the scroll function to work
    > again.
    >
    > with sata = ata3.01: revalidation failed (errno=-2) I suspended
    > simultaneously, on the third time this seems to show up.
    >
    > Ill send the dmesg from the three suspends as soon as I locate the
    > e-mail address to the Sata people.


    Please just attach it here.

    Thanks,
    Rafael
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: suspend

    Rafael J. Wysocki wrote:

    > On Wednesday, 2 of April 2008, Justin Mattock wrote:
    >> Hello; the only problems I see after a suspend is the appletouch
    >> looses its scroll function,

    >
    > Is that a USB device or some other kind?


    I have the same Problem on my macbook 13,3" using the appletouch usb module
    to drive the touchpad. chvt 1; chvt 7 brings the touchpad back after resume
    but do you maybe know a better solution?

    Best regards,

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. Re: suspend

    On Thursday, 3 of April 2008, Stefan Schweizer wrote:
    > Rafael J. Wysocki wrote:
    >
    > > On Wednesday, 2 of April 2008, Justin Mattock wrote:
    > >> Hello; the only problems I see after a suspend is the appletouch
    > >> looses its scroll function,

    > >
    > > Is that a USB device or some other kind?

    >
    > I have the same Problem on my macbook 13,3" using the appletouch usb module
    > to drive the touchpad. chvt 1; chvt 7 brings the touchpad back after resume
    > but do you maybe know a better solution?


    No, I don't, but perhaps the USB developers do (CCed now).

    Thanks,
    Rafael
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  7. Re: suspend

    Hello,

    Justin Mattock wrote:
    >> > [ 1233.811794] sd 2:0:1:0: [sda] Starting disk
    >> > [ 1234.013599] ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
    >> > [ 1234.013601] ata1.00: ACPI cmd ef/03:44:00:00:00:a0 filtered out
    >> > [ 1234.180232] ata1.00: configured for UDMA/66
    >> > [ 1222.732011] ata3.01: NODEV after polling detection
    >> > [ 1222.732016] ata3.01: revalidation failed (errno=-2)


    I presume this is ata_piix, right? What's hanging off of ata3.01? An
    optical drive?

    What happened is that, after resuming, libata reseted the channel and
    issued IDENTIFY[_PACKET] to make sure the device was still there. The
    device violated the state machine transition in the same way as when
    there's no device attached. libata paused for a while and retries and
    the device responded correctly at the retry. Things like this can
    happen. The problem is that libata resume is currently synchronous and
    retries like this hold the machine back from reaching operational status
    even when there's no reason for resume retrial on optical drive to delay
    the rest of resume process.

    Can you please post full kernel log and the result of 'lspci -nn'?

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  8. Re: suspend

    Justin Mattock wrote:
    > Hello; attached is kern.log as asked and lspci -nn.


    kernel log is missing.

    > I've noticed some avc's in there. makes me wonder if this is why
    > wpa_supplicant isnt working after a wakeup


    Probably not. It just took one extra try to wake the device up. Both
    hard and optical drives are accessible after resume, right?

    --
    tejun
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: suspend

    Hello;
    Yes both the drives are working(put a dvd in after a wakeup and it
    worked.) As for the wireless if I dont shutdown the wireless before
    a suspend, and leave it as is, it seems to be still connected after
    the wakeup(that's pretty cool)

    regards;
    Justin P. Mattock


    On Thu, Apr 3, 2008 at 1:01 AM, Tejun Heo wrote:
    > Justin Mattock wrote:
    >
    > > Hello; attached is kern.log as asked and lspci -nn.
    > >

    >
    > kernel log is missing.
    >
    >
    > > I've noticed some avc's in there. makes me wonder if this is why
    > > wpa_supplicant isnt working after a wakeup
    > >

    >
    > Probably not. It just took one extra try to wake the device up. Both hard
    > and optical drives are accessible after resume, right?
    >
    > --
    > tejun
    >




    --
    Justin P. Mattock
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  10. Re: suspend

    Am Donnerstag, 3. April 2008 01:55:33 schrieb Rafael J. Wysocki:
    > On Thursday, 3 of April 2008, Stefan Schweizer wrote:
    > > Rafael J. Wysocki wrote:
    > >
    > > > On Wednesday, 2 of April 2008, Justin Mattock wrote:
    > > >> Hello; the only problems I see after a suspend is the appletouch
    > > >> looses its scroll function,
    > > >
    > > > Is that a USB device or some other kind?

    > >
    > > I have the same Problem on my macbook 13,3" using the appletouch usb module
    > > to drive the touchpad. chvt 1; chvt 7 brings the touchpad back after resume
    > > but do you maybe know a better solution?

    >
    > No, I don't, but perhaps the USB developers do (CCed now).


    Please load the appletouch module with the parameter "debug=1" and
    post dmesg of a suspend/resume and the chvt thing.

    Regards
    Oliver
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  11. Re: suspend

    Oliver Neukum wrote:
    > Please load the appletouch module with the parameter "debug=1" and
    > post dmesg of a suspend/resume and the chvt thing.


    I found out the appletouch issue was already discused here:
    http://lkml.org/lkml/2007/3/28/172

    Unfortunately there seems to be no workaround and X-input still has more
    issues than it solves..

    Attached is the dmesg excerpt

    Best regards,
    Stefan

    usbcore: deregistering interface driver appletouch
    input: appletouch disconnected
    appletouch: Geyser mode initialized.
    input: appletouch
    as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.1/input/input19
    usbcore: registered new interface driver appletouch
    PM: Syncing filesystems ... done.
    Stopping fuse filesystems.
    Freezing user space processes ... (elapsed 0.00 seconds) <6>done.
    Stopping normal filesystems.
    Freezing remaining freezable tasks ... (elapsed 0.00 seconds) <6>done.
    ACPI: Preparing to enter system sleep state S3
    Suspending console(s)
    sd 2:0:1:0: [sda] Synchronizing SCSI cache
    sd 2:0:1:0: [sda] Stopping disk
    ACPI handle has no context!
    ACPI: PCI interrupt for device 0000:02:00.0 disabled
    sky2 eth0: disabling interface
    ACPI: PCI interrupt for device 0000:00:1f.2 disabled
    ACPI: PCI interrupt for device 0000:00:1f.1 disabled
    ACPI: PCI interrupt for device 0000:00:1d.7 disabled
    ACPI: PCI interrupt for device 0000:00:1d.3 disabled
    ACPI: PCI interrupt for device 0000:00:1d.2 disabled
    ACPI: PCI interrupt for device 0000:00:1d.1 disabled
    ACPI: PCI interrupt for device 0000:00:1d.0 disabled
    ACPI: PCI interrupt for device 0000:00:1b.0 disabled
    Disabling non-boot CPUs ...
    CPU 1 is now offline
    SMP alternatives: switching to UP code
    CPU1 is down
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#0.
    Back to C!
    Enabling non-boot CPUs ...
    SMP alternatives: switching to SMP code
    Booting processor 1/1 eip 3000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 3995.35 BogoMIPS
    (lpj=1997676)
    CPU: After generic identify, caps: bfe9fbff 00100000 00000000 00000000
    0000c1a9 00000000 00000000 00000000
    monitor/mwait feature present.
    CPU: L1 I cache: 32K, L1 D cache: 32K
    CPU: L2 cache: 2048K
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    CPU: After all inits, caps: bfe9fbff 00100000 00000000 00002940 0000c1a9
    00000000 00000000 00000000
    Intel machine check architecture supported.
    Intel machine check reporting enabled on CPU#1.
    CPU1: Intel Genuine Intel(R) CPU T2500 @ 2.00GHz stepping 08
    CPU1 is up
    Switched to high resolution mode on CPU 1
    PM: Writing back config space on device 0000:00:02.0 at offset f (was 100,
    writing 10a)
    PM: Writing back config space on device 0000:00:02.0 at offset 7 (was 0,
    writing 90400000)
    PM: Writing back config space on device 0000:00:02.0 at offset 6 (was 8,
    writing 80000008)
    PM: Writing back config space on device 0000:00:02.0 at offset 5 (was 1,
    writing 20f1)
    PM: Writing back config space on device 0000:00:02.0 at offset 4 (was 0,
    writing 90380000)
    PM: Writing back config space on device 0000:00:02.0 at offset 1 (was
    900000, writing 900007)
    ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 16 (level, low) -> IRQ 17
    PCI: Setting latency timer of device 0000:00:02.0 to 64
    PM: Writing back config space on device 0000:00:02.1 at offset 4 (was 0,
    writing 90300000)
    PM: Writing back config space on device 0000:00:02.1 at offset 1 (was
    900000, writing 900007)
    PM: Writing back config space on device 0000:00:07.0 at offset f (was 100,
    writing 10a)
    PM: Writing back config space on device 0000:00:07.0 at offset 4 (was 0,
    writing 90444000)
    PM: Writing back config space on device 0000:00:07.0 at offset 1 (was
    b00000, writing b00002)
    PM: Writing back config space on device 0000:00:1b.0 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:00:1b.0 at offset 4 (was 4,
    writing 90440004)
    PM: Writing back config space on device 0000:00:1b.0 at offset 3 (was 0,
    writing 40)
    PM: Writing back config space on device 0000:00:1b.0 at offset 1 (was
    100000, writing 100002)
    ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 22 (level, low) -> IRQ 21
    PCI: Setting latency timer of device 0000:00:1b.0 to 64
    PM: Writing back config space on device 0000:00:1c.0 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:00:1c.0 at offset 9 (was 10001,
    writing 50015001)
    PM: Writing back config space on device 0000:00:1c.0 at offset 8 (was 0,
    writing 90209020)
    PM: Writing back config space on device 0000:00:1c.0 at offset 7 (was
    20000000, writing 20001010)
    PM: Writing back config space on device 0000:00:1c.0 at offset 6 (was 0,
    writing 10100)
    PM: Writing back config space on device 0000:00:1c.0 at offset 3 (was
    810000, writing 810040)
    PM: Writing back config space on device 0000:00:1c.0 at offset 1 (was
    100000, writing 100007)
    PCI: Setting latency timer of device 0000:00:1c.0 to 64
    PM: Writing back config space on device 0000:00:1c.1 at offset f (was 200,
    writing 20a)
    PM: Writing back config space on device 0000:00:1c.1 at offset 9 (was 10001,
    writing 1fff1)
    PM: Writing back config space on device 0000:00:1c.1 at offset 8 (was 0,
    writing 90109010)
    PM: Writing back config space on device 0000:00:1c.1 at offset 7 (was
    20000000, writing f0)
    PM: Writing back config space on device 0000:00:1c.1 at offset 6 (was 0,
    writing 20200)
    PM: Writing back config space on device 0000:00:1c.1 at offset 3 (was
    810000, writing 810040)
    PM: Writing back config space on device 0000:00:1c.1 at offset 1 (was
    100000, writing 100007)
    PCI: Setting latency timer of device 0000:00:1c.1 to 64
    PCI: Enabling device 0000:00:1d.0 (0000 -> 0001)
    ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 21 (level, low) -> IRQ 20
    PCI: Setting latency timer of device 0000:00:1d.0 to 64
    PM: Writing back config space on device 0000:00:1d.0 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:00:1d.0 at offset 8 (was 1,
    writing 20a1)
    usb usb1: root hub lost power or was reset
    PCI: Enabling device 0000:00:1d.1 (0000 -> 0001)
    ACPI: PCI Interrupt 0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19
    PCI: Setting latency timer of device 0000:00:1d.1 to 64
    PM: Writing back config space on device 0000:00:1d.1 at offset f (was 200,
    writing 20b)
    PM: Writing back config space on device 0000:00:1d.1 at offset 8 (was 1,
    writing 2081)
    usb usb2: root hub lost power or was reset
    PCI: Enabling device 0000:00:1d.2 (0000 -> 0001)
    ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 18
    PCI: Setting latency timer of device 0000:00:1d.2 to 64
    PM: Writing back config space on device 0000:00:1d.2 at offset f (was 300,
    writing 30b)
    PM: Writing back config space on device 0000:00:1d.2 at offset 8 (was 1,
    writing 2061)
    usb usb3: root hub lost power or was reset
    PCI: Enabling device 0000:00:1d.3 (0000 -> 0001)
    ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 17
    PCI: Setting latency timer of device 0000:00:1d.3 to 64
    PM: Writing back config space on device 0000:00:1d.3 at offset f (was 400,
    writing 40a)
    PM: Writing back config space on device 0000:00:1d.3 at offset 8 (was 1,
    writing 2041)
    usb usb4: root hub lost power or was reset
    PCI: Enabling device 0000:00:1d.7 (0000 -> 0002)
    ACPI: PCI Interrupt 0000:00:1d.7[A] -> GSI 21 (level, low) -> IRQ 20
    PCI: Setting latency timer of device 0000:00:1d.7 to 64
    PM: Writing back config space on device 0000:00:1d.7 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:00:1d.7 at offset 4 (was 0,
    writing 90445400)
    PM: Writing back config space on device 0000:00:1e.0 at offset 9 (was 10001,
    writing 1fff1)
    PM: Writing back config space on device 0000:00:1e.0 at offset 8 (was 0,
    writing 90009000)
    PM: Writing back config space on device 0000:00:1e.0 at offset 7 (was
    22800000, writing 228000f0)
    PM: Writing back config space on device 0000:00:1e.0 at offset 6 (was 0,
    writing 20030300)
    PM: Writing back config space on device 0000:00:1e.0 at offset 1 (was
    100000, writing 100007)
    PCI: Setting latency timer of device 0000:00:1e.0 to 64
    PM: Writing back config space on device 0000:00:1f.1 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:00:1f.1 at offset 1 (was
    2800001, writing 2800005)
    ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 18 (level, low) -> IRQ 18
    PCI: Setting latency timer of device 0000:00:1f.1 to 64
    PM: Writing back config space on device 0000:00:1f.2 at offset f (was 200,
    writing 20b)
    PM: Writing back config space on device 0000:00:1f.2 at offset 8 (was 1,
    writing 2021)
    PM: Writing back config space on device 0000:00:1f.2 at offset 1 (was
    2b00002, writing 2b00007)
    ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
    PCI: Setting latency timer of device 0000:00:1f.2 to 64
    PM: Writing back config space on device 0000:00:1f.3 at offset f (was 200,
    writing 20b)
    PM: Writing back config space on device 0000:01:00.0 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:01:00.0 at offset c (was 0,
    writing fffe0000)
    PM: Writing back config space on device 0000:01:00.0 at offset 6 (was 1,
    writing 1001)
    PM: Writing back config space on device 0000:01:00.0 at offset 4 (was 4,
    writing 90200004)
    PM: Writing back config space on device 0000:01:00.0 at offset 3 (was 0,
    writing 40)
    PM: Writing back config space on device 0000:01:00.0 at offset 1 (was
    40100000, writing 100007)
    sky2 eth0: enabling interface
    PM: Writing back config space on device 0000:02:00.0 at offset f (was 100,
    writing 10b)
    PM: Writing back config space on device 0000:02:00.0 at offset 4 (was 4,
    writing 90100004)
    PM: Writing back config space on device 0000:02:00.0 at offset 3 (was 0,
    writing 40)
    PM: Writing back config space on device 0000:02:00.0 at offset 1 (was
    100000, writing 100007)
    ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 17 (level, low) -> IRQ 16
    PCI: Setting latency timer of device 0000:02:00.0 to 64
    PM: Writing back config space on device 0000:03:03.0 at offset f (was
    180c0100, writing 180c010b)
    PM: Writing back config space on device 0000:03:03.0 at offset 4 (was 0,
    writing 90000000)
    PM: Writing back config space on device 0000:03:03.0 at offset 3 (was 0,
    writing f810)
    PM: Writing back config space on device 0000:03:03.0 at offset 1 (was
    2900000, writing 2900216)
    sd 2:0:1:0: [sda] Starting disk
    ata1.00: ACPI cmd ef/03:0c:00:00:00:a0 filtered out
    ata1.00: ACPI cmd ef/03:44:00:00:00:a0 filtered out
    ata3.01: ACPI cmd ef/03:0c:00:00:00:b0 filtered out
    ata3.01: ACPI cmd ef/03:45:00:00:00:b0 filtered out
    ata3.01: configured for UDMA/100
    sd 2:0:1:0: [sda] 156301488 512-byte hardware sectors (80026 MB)
    sd 2:0:1:0: [sda] Write Protect is off
    sd 2:0:1:0: [sda] Mode Sense: 00 3a 00 00
    sd 2:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support
    DPO or FUA
    ata1.00: configured for UDMA/66
    restoring control 00000000-0000-0000-0000-000000000101/0/2
    restoring control 00000000-0000-0000-0000-000000000101/3/7
    restoring control 00000000-0000-0000-0000-000000000101/5/9
    applesmc: received a shock interrupt
    applesmc: cannot setup irq handler
    applesmc: accelerometer successfully initialized.
    Restarting all filesystems ...
    Restarting tasks ... <6>usb 1-1: USB disconnect, address 6
    done.
    usb 1-1: new low speed USB device using uhci_hcd and address 8
    usb 1-1: configuration #1 chosen from 1 choice
    input: HID 0461:4d03
    as /devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/input/input20
    input: USB HID v1.10 Mouse [HID 0461:4d03] on usb-0000:00:1d.0-1
    usb 1-2: USB disconnect, address 7
    input: appletouch disconnected
    usb 1-2: new full speed USB device using uhci_hcd and address 9
    usb 1-2: configuration #1 chosen from 1 choice
    input: Apple Computer Apple Internal Keyboard / Trackpad
    as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.0/input/input21
    input: USB HID v1.11 Keyboard [Apple Computer Apple Internal Keyboard /
    Trackpad] on usb-0000:00:1d.0-2
    appletouch: Geyser mode initialized.
    input: appletouch
    as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.1/input/input22
    appletouch: incomplete data package (first byte: 2, length: 4).
    input: Apple Computer Apple Internal Keyboard / Trackpad
    as /devices/pci0000:00/0000:00:1d.0/usb1/1-2/1-2:1.2/input/input23
    input: USB HID v1.11 Device [Apple Computer Apple Internal Keyboard /
    Trackpad] on usb-0000:00:1d.0-2
    usb 3-2: USB disconnect, address 3
    usb 3-2: new full speed USB device using uhci_hcd and address 4
    usb 3-2: configuration #1 chosen from 1 choice
    hiddev0: USB HID v1.11 Device [Apple Computer, Inc. IR Receiver] on
    usb-0000:00:1d.2-2
    usb 4-1: USB disconnect, address 3
    usb 4-1: new full speed USB device using uhci_hcd and address 4
    usb 4-1: configuration #1 chosen from 1 choice
    input: HID 05ac:1000
    as /devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.0/input/input24
    input: USB HID v1.11 Keyboard [HID 05ac:1000] on usb-0000:00:1d.3-1
    input: HID 05ac:1000
    as /devices/pci0000:00/0000:00:1d.3/usb4/4-1/4-1:1.1/input/input25
    input: USB HID v1.11 Mouse [HID 05ac:1000] on usb-0000:00:1d.3-1

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  12. Re: suspend

    Am Donnerstag, 3. April 2008 09:42:00 schrieb Stefan Schweizer:
    > Oliver Neukum wrote:
    > > Please load the appletouch module with the parameter "debug=1" and
    > > post dmesg of a suspend/resume and the chvt thing.

    >
    > I found out the appletouch issue was already discused here:
    > http://lkml.org/lkml/2007/3/28/172
    >
    > Unfortunately there seems to be no workaround and X-input still has more
    > issues than it solves..
    >
    > Attached is the dmesg excerpt


    According to dmesg the kernel part works correctly. This is an X problem
    as diagnosed in the thread you sent a link to.

    Sorry
    Oliver

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  13. Re: suspend

    Am Donnerstag, 3. April 2008 09:42:00 schrieb Stefan Schweizer:
    > Oliver Neukum wrote:
    > > Please load the appletouch module with the parameter "debug=1" and
    > > post dmesg of a suspend/resume and the chvt thing.

    >
    > I found out the appletouch issue was already discused here:
    > http://lkml.org/lkml/2007/3/28/172
    >
    > Unfortunately there seems to be no workaround and X-input still has more
    > issues than it solves..
    >
    > Attached is the dmesg excerpt


    On second thought, this should be fixed by usb persist if the appletouch
    driver supported reset_resume. Would you be willing to test a kernel patch
    that implements reset_resume in the appletouch driver?

    Regards
    Oliver

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  14. Re: suspend

    > On second thought, this should be fixed by usb persist if the appletouch
    > driver supported reset_resume. Would you be willing to test a kernel patch
    > that implements reset_resume in the appletouch driver?


    Sure, I would love to have this fixed :-)

    best regards,
    -Stefan
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  15. Re: suspend

    Hello with doing some more testing on suspending the macbook pro;
    like in the other posts about appletouch, it seems to me to be a
    problem with X, one test appletouch was able to have scroll
    functionality due to the event number staying the same. Hopefully with
    the latest version coming this issue will be resolved. With running
    a test on wpa_supplicant. when shutting internet off then suspending
    the system wpa_supplicant seems to be unresponsive, but if you leave
    wpa_supplicant connected the only issue I see is when wpa_supplicant
    does a rekey.

    with streaming music xmms seems to do alright, the music will play
    whatever is left in the memory then reconnect itself, with watching
    T.V. through gmplayer it seems to loose connectivity as well as
    watching T.V. through flash.

    With watching a DVD gmplayer seems to crash everytime upon wakeup.

    with the isight it seems rmmod uvcvideo and modprobe uvcvideo does the
    trick, but SELinux will reject the device due to the event number
    changing.
    With the bluetooth mighty mouse hid2hci --tohci does the trick, but
    I'm not satisfied with that, how to keep the device on hci?
    after a wakeup.
    regards;
    Justin P. Mattock


    On Thu, Apr 3, 2008 at 8:53 AM, Stefan Schweizer wrote:
    > > On second thought, this should be fixed by usb persist if the appletouch
    > > driver supported reset_resume. Would you be willing to test a kernel patch
    > > that implements reset_resume in the appletouch driver?

    >
    > Sure, I would love to have this fixed :-)
    >
    > best regards,
    > -Stefan
    >
    >
    > --
    > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    > the body of a message to majordomo@vger.kernel.org
    > More majordomo info at http://vger.kernel.org/majordomo-info.html
    > Please read the FAQ at http://www.tux.org/lkml/
    >




    --
    Justin P. Mattock
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread