lkml.org 
[lkml]   [2007]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectSATA resume slowness, e1000 MSI warning

    * Michael S. Tsirkin <mst@mellanox.co.il> wrote:

    > > (Resume is very slow, because disks are not spinned up properly; and
    > > there's something wrong with timers; console beeps take way too long).

    > Pavel, I tried with your .config, and indeed the system came back to
    > life after 2-3 minutes after I press Fn/F4, indeed the issue seems to
    > be with the disk. It could be that the same takes place with my
    > original .config - maybe I just wasn't patient enough. I'll need to
    > re-test that.

    the spin-up takes a few seconds here under suspend/resume simulation:

    | ata1: waiting for device to spin up (7 secs)
    | Restarting tasks ... done.

    [5-10 seconds pass]

    | ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    | ata1.00: configured for UDMA/100
    | SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
    | sda: Write Protect is off
    | sda: Mode Sense: 00 3a 00 00
    | SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA

    with real resume it takes even longer time - but i dont see where the
    delays come from in that case - i suspect it's SATA.

    i'm also getting this WARN_ON() from e1000:

    BUG: at drivers/pci/msi.c:611 pci_enable_msi()
    [<c01061bd>] show_trace_log_lvl+0x19/0x2e
    [<c01062b6>] show_trace+0x12/0x14
    [<c01062cc>] dump_stack+0x14/0x16
    [<c024fcc4>] pci_enable_msi+0x6d/0x203
    [<c02b709e>] e1000_request_irq+0x2e/0xe2
    [<c02bb742>] e1000_resume+0x7f/0xef
    [<c0249a68>] pci_device_resume+0x1a/0x44
    [<c02b39ec>] resume_device+0xf7/0x16f
    [<c02b3adb>] dpm_resume+0x77/0xcb
    [<c02b3b69>] device_resume+0x3a/0x51
    [<c014e669>] enter_state+0x193/0x1bb
    [<c014e712>] state_store+0x81/0x97
    [<c01b68bc>] subsys_attr_store+0x20/0x25
    [<c01b6feb>] sysfs_write_file+0xce/0xf6
    [<c017e16b>] vfs_write+0xb1/0x13a
    [<c017e899>] sys_write+0x3d/0x61
    [<c0105220>] syscall_call+0x7/0xb

    seems harmless because it seems to work fine.

    Ingo
    -
    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/

    \
     
     \ /
      Last update: 2007-03-05 11:23    [W:4.250 / U:0.024 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site