On Wed, 20 Feb 2008, Herton Ronaldo Krzesinski wrote:
> Hi,
>
> I don't know if I did the right steps, currently I'm having problems
> trying to make Intel Classmate suspend/resume work with newer kernels
> (In this case 2.6.25-rc2+ latest checkout =
> 5d9c4a7de64d398604a978d267a6987f1f4025b7).
> After resume, the usb devices still get reenumerated even with USB-Persist
> enabled,
> making the root device (sda) being lost as it gets redetected as sdb. It is
> not a
> regression, as I tested with a kernel between 2.6.22/2.6.23 release (git)
> right
> after persist was added and the same occurs. This is similar to the problem
> we had some time ago with 2.6.17 kernel, but that would only happen if you
> had some usb device attached to the usb ports (hub powered on).
>
> I enabled persist doing echo 1 > /sys/devices/(...)/power/persist for the
> device, is there something else required? The device also has the
> USB_QUIRK_RESET_RESUME quirk enabled, that from what I debugged until
> now seems required. This is a full log example (with CONFIG_USB_DEBUG
> enabled):
Actually this doesn't look like a full log. For example, there should
be a line saying "Restarting tasks ... done."
> netconsole: network logging started
> PM: Syncing filesystems ... done.
> Freezing user space processes ... (elapsed 0.01 seconds) done.
> Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
> ACPI: Preparing to enter system sleep state S3
> Suspending console(s)
> uhci_hcd 0000:00:1d.1: release dev 2 ep81-INT, period 8, phase 4, 118 us
> uhci_hcd 0000:00:1d.1: release dev 2 ep82-INT, period 8, phase 4, 118 us
> usb 3-1: usb suspend
> usb 1-6: usb suspend
> usb 1-5: usb suspend
> usb 1-1: usb suspend
> hub 3-0:1.0: hub_suspend
> usb usb3: bus suspend
> usb usb3: suspend_rh
> hub 1-0:1.0: hub_suspend
> usb usb1: bus suspend
> ehci_hcd 0000:00:1d.7: suspend root hub
> drm_sysfs_suspend
> ACPI: PCI interrupt for device 0000:00:02.0 disabled
> ACPI handle has no context!
> ACPI handle has no context!
> ACPI: PCI interrupt for device 0000:00:1e.2 disabled
> ACPI: PCI interrupt for device 0000:00:1d.7 disabled
> ehci_hcd 0000:00:1d.7: --> PCI D3/wakeup
> uhci_hcd 0000:00:1d.3: uhci_suspend
> ACPI: PCI interrupt for device 0000:00:1d.3 disabled
> uhci_hcd 0000:00:1d.3: --> PCI D0/legacy
> uhci_hcd 0000:00:1d.2: uhci_suspend
> ACPI: PCI interrupt for device 0000:00:1d.2 disabled
> uhci_hcd 0000:00:1d.2: --> PCI D0/legacy
> uhci_hcd 0000:00:1d.1: uhci_suspend
> ACPI: PCI interrupt for device 0000:00:1d.1 disabled
> uhci_hcd 0000:00:1d.1: --> PCI D0/legacy
> uhci_hcd 0000:00:1d.0: uhci_suspend
> ACPI: PCI interrupt for device 0000:00:1d.0 disabled
> uhci_hcd 0000:00:1d.0: --> PCI D0/legacy
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0.
> Back to C!
> PM: Writing back config space on device 0000:00:02.0 at offset 1 (was 900007,
> writing 900003)
> PM: Writing back config space on device 0000:00:1c.0 at offset f (was 20100,
> writing 2010a)
> ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 16 (level, low) -> IRQ 16
> PCI: Setting latency timer of device 0000:00:1c.0 to 64
> uhci_hcd 0000:00:1d.0: PCI legacy resume
> ACPI: PCI Interrupt 0000:00:1d.0[A] -> GSI 23 (level, low) -> IRQ 23
> PCI: Setting latency timer of device 0000:00:1d.0 to 64
> uhci_hcd 0000:00:1d.0: uhci_resume
> uhci_hcd 0000:00:1d.0: uhci_check_and_reset_hc: legsup = 0x0f30
> uhci_hcd 0000:00:1d.0: Performing full reset
> usb usb2: root hub lost power or was reset
> usb usb2: suspend_rh
> uhci_hcd 0000:00:1d.1: PCI legacy resume
> 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
> uhci_hcd 0000:00:1d.1: uhci_resume
> uhci_hcd 0000:00:1d.1: uhci_check_and_reset_hc: legsup = 0x0030
> uhci_hcd 0000:00:1d.1: Performing full reset
> usb usb3: root hub lost power or was reset
> usb usb3: suspend_rh
> uhci_hcd 0000:00:1d.2: PCI legacy resume
> 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
> uhci_hcd 0000:00:1d.2: uhci_resume
> uhci_hcd 0000:00:1d.2: uhci_check_and_reset_hc: legsup = 0x0030
> uhci_hcd 0000:00:1d.2: Performing full reset
> usb usb4: root hub lost power or was reset
> usb usb4: suspend_rh
> uhci_hcd 0000:00:1d.3: PCI legacy resume
> ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16
At about this point it seems that a bunch of lines got lost. And of
course, they are the lines with the crucial information.
> hub 1-0:1.0: logical disconnect on port 5
> uhci_hcd 0000:00:1d.1: reserve dev 2 ep81-INT, period 8, phase 4, 118 us
> uhci_hcd 0000:00:1d.1: reserve dev 2 ep82-INT, period 8, phase 4, 118 us
> <7>hub 1-0:1.0: state 7 ports 8 chg 0062 evt 0000
> usb 1-1: uevent
> EXT3-fs error (device sda1): ext3_find_entry: reading directory #7201 offset 0
> Buffer I/O error on device sda1, logical block 0
> lost page write due to I/O error on sda1
> EXT3-fs error (device sda1): ext3_find_entry: reading directory #7201 offset 0
> ------------[ cut here ]------------
> WARNING: at fs/buffer.c:1184 mark_buffer_dirty+0x5d/0x80()
> Modules linked in: netconsole af_packet ipv6 snd_seq_oss snd_seq_midi_event
> snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss binfmt_misc rtc_cmos
> rtc_core rtc_lib snd_intel8x0 pcspkr snd_ac97_codec i2c_i801 ac97_bus?
> write_msg+0xcc/0xf0 [netconsole]
> [<c0123c54>] ? __call_console_drivers+0x54/0x70
> [<c0123ce9>] ? _call_console_drivers+0x79/0x90
> [<c0123f19>] ? release_console_sem+0x1d9/0x210
> [<c0124320>] ? vprintk+0x210/0x3e0
> [<c0124320>] ? vprintk+0x210/0x3e0
> [<c01f4ff3>] ? generic_unplug_device+0x23/0x40
> [<c0198d9d>] mark_buffer_dirty+0x5d/0x80
> [<c01c71b6>] ext3_commit_super+0x46/0x70
> [<c01c7b25>] ext3_handle_error+0x75/0xb0
> [<c012450b>] ? printk+0x1b/0x20
> [<c01c7c22>] ext3_error+0x52/0x60
> [<c01c5788>] ext3_find_entry+0x518/0x670
> [<c0200cd8>] ? rb_insert_color+0xb8/0xe0
> [<c0139e6e>] ? hrtimer_start+0x6e/0xf0
> [<c0375f04>] ? schedule+0x2b4/0x460
> [<c01c628a>] ext3_lookup+0x3a/0xd0
> [<c017e483>] do_lookup+0x133/0x180
> [<c017f7ec>] __link_path_walk+0x12c/0xe10
> [<c030d969>] ? kfree_skb+0x19/0x30
> [<c036d0ea>] ? unix_stream_recvmsg+0x39a/0x530
> [<c0180510>] link_path_walk+0x40/0xa0
> [<c0162049>] ? handle_mm_fault+0xf9/0x5f0
> [<c0174c31>] ? get_unused_fd_flags+0xc1/0x100
> [<c0180588>] path_walk+0x18/0x20
> [<c0180792>] do_path_lookup+0x82/0x1c0
> [<c0177861>] ? get_empty_filp+0x61/0x130
> [<c018135d>] __path_lookup_intent_open+0x4d/0x90
> [<c018141f>] path_lookup_open+0x1f/0x30
> [<c018151b>] open_namei+0x5b/0x620
> [<c0153254>] ? unlock_page+0x24/0x30
> [<c016021d>] ? __do_fault+0x17d/0x3d0
> [<c0174f6c>] do_filp_open+0x2c/0x50
> [<c0162049>] ? handle_mm_fault+0xf9/0x5f0
> [<c0174c31>] ? get_unused_fd_flags+0xc1/0x100
> [<c0174fd9>] do_sys_open+0x49/0xe0
> [<c01750ac>] sys_open+0x1c/0x20
> [<c0104d1e>] sysenter_past_esp+0x5f/0x85
> [<c0370000>] ? wireless_spy_update+0xd0/0x110
> =======================
> ---[ end trace 4651522f53c979cc ]---
> Buffer I/O error on device sda1, logical block 0
> lost page write due to I/O error on sda1
> done.
> input: AT Translated Set 2 keyboard as /class/input/input10
> ehci_hcd 0000:00:1d.7: port 1 high speed
> ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
> usb 1-1: new high speed USB device using ehci_hcd and address 6
> ehci_hcd 0000:00:1d.7: port 1 high speed
> ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0 PE CONNECT
> usb 1-1: USB quirks for this device: 2
> usb 1-1: default language 0x0409
> usb 1-1: uevent
> usb 1-1: usb_probe_device
> usb 1-1: configuration #1 chosen from 1 choice
> usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> usb 1-1:1.0: uevent
> usb-storage 1-1:1.0: usb_probe_interface
> usb-storage 1-1:1.0: usb_probe_interface - got id
> scsi1 : SCSI emulation for USB Mass Storage devices
> drivers/usb/core/inode.c: creating file '006'
> usb 1-1: New USB device found, idVendor=08ec, idProduct=1000
> usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> usb 1-1: Product: uDiskOnChip
> usb 1-1: Manufacturer: M-Systems
> usb 1-1: SerialNumber: 0FA14860F30378F8
...
Maybe with a complete log the cause will be evident. If you want to
experiment a little, you could try adding some printk lines to the
hub_reset_resume() routine in drivers/usb/core/hub.c. It would be nice
to know for sure which branch was taken inside the "if (child) {"
block. Another good place to look is in finish_port_resume() in the
same source file; does the "if (udev->reset_resume)" test succeed?
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
