Pavel Machek wrote:
> Hi!
> 
>>> velocity_suspend() seems to be at fault.
>> (gdb) l *(velocity_suspend+0x37)
>> 0xc0244665 is in velocity_suspend (drivers/net/via-velocity.c:3399).
>> 3394         if(!netif_running(vptr->dev))
>> 3395                 return 0;
>> 3396 
>> 3397         netif_device_detach(vptr->dev);
>> 3398 
>> 3399         spin_lock_irqsave(&vptr->lock, flags);
>> 3400         pci_save_state(pdev);
>> 3401 #ifdef ETHTOOL_GWOL
>> 3402         if (vptr->flags & VELOCITY_FLAGS_WOL_ENABLED) {
>> 3403                 velocity_get_ip(vptr);
>> (gdb) 
>> 3404                 velocity_save_context(vptr, &vptr->context);
>> 3405                 velocity_shutdown(vptr);
>> 3406                 velocity_set_wol(vptr);
>> 3407                 pci_enable_wake(pdev, PCI_D3hot, 1);
>> 3408                 pci_set_power_state(pdev, PCI_D3hot);
>> 3409         } else {
>> 3410                 velocity_save_context(vptr, &vptr->context);
>> 3411                 velocity_shutdown(vptr);
>> 3412                 pci_disable_device(pdev);
>> 3413                 pci_set_power_state(pdev, pci_choose_state(pdev, 
>> state));
>> (gdb) 
>> 3414         }
>> 3415 #else
>> 3416         pci_set_power_state(pdev, pci_choose_state(pdev, state));
>> 3417 #endif
>> 3418         spin_unlock_irqrestore(&vptr->lock, flags);
>> 3419         return 0;
>> 3420 }
>>
>> So velocity_suspend calls spin_lock_irqsave, and then pci_set_power_state 
>> which msleep()s.  Is that the root problem here? (I've added Ingo & Peter to 
>> the CC list since they may have some comments on the scheduler/lockdep parts 
>> of the trace).
> 
> Looks like velocity is broken. Can you try to unload it before sleep
> to see if the rest of suspend works for you?
> 

(Trimmed cc, since this is really just more of a PM discussion)

No modules here...

I recompiled the kernel without the velocity driver, and got behaviour more 
comparable to the other failures I've experienced in the past:

Feb 25 20:18:46 alekhine kernel: [   73.564725] PM: Syncing filesystems ... 
done.
Feb 25 20:19:14 alekhine kernel: [   73.580807] Freezing user space processes 
... (elapsed 0.01 seconds) done.
Feb 25 20:19:14 alekhine kernel: [   73.595524] Freezing remaining freezable 
tasks ... (elapsed 0.00 seconds) done.
Feb 25 20:19:14 alekhine kernel: [   73.595839] ACPI: Preparing to enter system 
sleep state S3
Feb 25 20:19:14 alekhine kernel: [   73.697308] Suspending console(s)
Feb 25 20:19:14 alekhine kernel: [   73.700386] sd 3:0:0:0: [sda] Synchronizing 
SCSI cache
Feb 25 20:19:14 alekhine kernel: [   73.783185] sd 3:0:0:0: [sda] Stopping disk
Feb 25 20:19:14 alekhine kernel: [   73.784302] ACPI: PCI interrupt for device 
0000:00:11.5 disabled
Feb 25 20:19:14 alekhine kernel: [   73.794585] ACPI: PCI interrupt for device 
0000:00:10.4 disabled
Feb 25 20:19:14 alekhine kernel: [   73.805370] ACPI: PCI interrupt for device 
0000:00:10.3 disabled
Feb 25 20:19:14 alekhine kernel: [   73.816170] ACPI: PCI interrupt for device 
0000:00:10.2 disabled
Feb 25 20:19:14 alekhine kernel: [   73.826999] ACPI: PCI interrupt for device 
0000:00:10.1 disabled
Feb 25 20:19:14 alekhine kernel: [   73.837833] ACPI: PCI interrupt for device 
0000:00:10.0 disabled
Feb 25 20:19:14 alekhine kernel: [   73.848668] ACPI: PCI interrupt for device 
0000:00:0f.1 disabled
Feb 25 20:19:14 alekhine kernel: [   73.859346] ACPI: PCI interrupt for device 
0000:00:0f.0 disabled
Feb 25 20:19:14 alekhine kernel: [   73.882878] Intel machine check 
architecture supported.
Feb 25 20:19:14 alekhine kernel: [   73.882878] Intel machine check reporting 
enabled on CPU#0.
Feb 25 20:19:14 alekhine kernel: [   73.884890] ACPI: PCI Interrupt 
0000:00:0f.0[B] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 20
Feb 25 20:19:14 alekhine kernel: [   73.884892] ACPI: PCI Interrupt 
0000:00:0f.1[A] -> Link [ALKA] -> GSI 20 (level, low) -> IRQ 20
Feb 25 20:19:14 alekhine kernel: [   73.890893] ACPI: PCI Interrupt 
0000:00:10.0[A] -> GSI 21 (level, low) -> IRQ 21
Feb 25 20:19:14 alekhine kernel: [   73.890893] usb usb2: root hub lost power 
or was reset
Feb 25 20:19:14 alekhine kernel: [   73.901724] ACPI: PCI Interrupt 
0000:00:10.1[A] -> GSI 21 (level, low) -> IRQ 21
Feb 25 20:19:14 alekhine kernel: [   73.901724] usb usb3: root hub lost power 
or was reset
Feb 25 20:19:14 alekhine kernel: [   73.912597] ACPI: PCI Interrupt 
0000:00:10.2[B] -> GSI 21 (level, low) -> IRQ 21
Feb 25 20:19:14 alekhine kernel: [   73.912597] usb usb4: root hub lost power 
or was reset
Feb 25 20:19:14 alekhine kernel: [   73.923472] ACPI: PCI Interrupt 
0000:00:10.3[B] -> GSI 21 (level, low) -> IRQ 21
Feb 25 20:19:14 alekhine kernel: [   73.923472] usb usb5: root hub lost power 
or was reset
Feb 25 20:19:14 alekhine kernel: [   73.934336] ACPI: PCI Interrupt 
0000:00:10.4[C] -> GSI 21 (level, low) -> IRQ 21
Feb 25 20:19:14 alekhine kernel: [   73.945209] ACPI: PCI Interrupt 
0000:00:11.5[C] -> GSI 22 (level, low) -> IRQ 22
Feb 25 20:19:14 alekhine kernel: [   73.947465] ACPI: PCI Interrupt 
0000:01:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Feb 25 20:19:14 alekhine kernel: [   73.947660] sd 3:0:0:0: [sda] Starting disk
Feb 25 20:19:14 alekhine kernel: [   74.183122] ata3.01: ACPI cmd 
ef/03:0c:00:00:00:b0 filtered out
Feb 25 20:19:14 alekhine kernel: [   74.183122] ata3.01: ACPI cmd 
ef/03:42:00:00:00:b0 filtered out
Feb 25 20:19:14 alekhine kernel: [   74.336028] ata3.00: ACPI cmd 
ef/03:0c:00:00:00:a0 filtered out
Feb 25 20:19:14 alekhine kernel: [   74.336028] ata3.00: ACPI cmd 
ef/03:42:00:00:00:a0 filtered out
Feb 25 20:19:14 alekhine kernel: [   74.491252] ata3.00: configured for UDMA/33
Feb 25 20:19:14 alekhine kernel: [   74.678330] ata3.01: configured for UDMA/33
Feb 25 20:19:14 alekhine kernel: [   78.168897] ata4.00: ACPI cmd 
ef/03:0c:00:00:00:a0 filtered out
Feb 25 20:19:14 alekhine kernel: [   78.168897] ata4.00: ACPI cmd 
ef/03:45:00:00:00:a0 filtered out
Feb 25 20:19:14 alekhine kernel: [   78.172976] ata4.00: configured for UDMA/100
Feb 25 20:19:14 alekhine kernel: [   78.177133] sd 3:0:0:0: [sda] 156301488 
512-byte hardware sectors (80026 MB)
Feb 25 20:19:14 alekhine kernel: [   78.177133] sd 3:0:0:0: [sda] Write Protect 
is off
Feb 25 20:19:14 alekhine kernel: [   78.177133] sd 3:0:0:0: [sda] Write cache: 
enabled, read cache: enabled, doesn't support DPO or FUA
Feb 25 20:19:14 alekhine kernel: [   78.720991] Restarting tasks ... <6>usb 
2-1: USB disconnect, address 2
Feb 25 20:19:14 alekhine kernel: [   78.766838] done.
Feb 25 20:19:14 alekhine kernel: [   78.951998] usb 2-1: new low speed USB 
device using uhci_hcd and address 4
Feb 25 20:19:14 alekhine kernel: [   79.114037] usb 2-1: configuration #1 
chosen from 1 choice
Feb 25 20:19:14 alekhine kernel: [   79.138166] input: Logitech USB Mouse as 
/devices/pci0000:00/0000:00:10.0/usb2/2-1/2-1:1.0/input/input5
Feb 25 20:19:14 alekhine kernel: [   79.180828] input: USB HID v1.10 Mouse 
[Logitech USB Mouse] on usb-0000:00:10.0-1
Feb 25 20:19:14 alekhine kernel: [   79.181059] usb 2-2: USB disconnect, 
address 3
Feb 25 20:19:15 alekhine kernel: [   79.436567] usb 2-2: new low speed USB 
device using uhci_hcd and address 5
Feb 25 20:19:15 alekhine kernel: [   79.606180] usb 2-2: configuration #1 
chosen from 1 choice
Feb 25 20:19:15 alekhine kernel: [   79.623893] input: Microsoft Microsoft<AE> 
Digital Media Pro Keyboard as 
/devices/pci0000:00/0000:00:10.0/usb2/2-2/2-2:1.0/input/input6
Feb 25 20:19:15 alekhine kernel: [   79.663140] input: USB HID v1.11 Keyboard 
[Microsoft Microsoft<AE> Digital Media Pro Keyboard] on usb-0000:00:10.0-2
Feb 25 20:19:15 alekhine kernel: [   79.697610] input: Microsoft Microsoft<AE> 
Digital Media Pro Keyboard as 
/devices/pci0000:00/0000:00:10.0/usb2/2-2/2-2:1.1/input/input7
Feb 25 20:19:15 alekhine kernel: [   79.721948] input: USB HID v1.11 Device 
[Microsoft Microsoft<AE> Digital Media Pro Keyboard] on usb-0000:00:10.0-2


I don't see anything there that would explain the failure, but the console 
never comes back, and I am forced to hard reset the box.  Anything else I can 
try?

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

Reply via email to