From mboxrd@z Thu Jan 1 00:00:00 1970 From: Siddhartha Jain Subject: Re: [PATCH] SATA / AHCI: Do not play with the link PM during suspend to RAM Date: Mon, 30 Aug 2010 19:03:16 -0700 Message-ID: References: <1283027290.2721.37.camel@myfedorahat> <4C7BAA42.2050809@kernel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from mail-pz0-f46.google.com ([209.85.210.46]:57015 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756607Ab0HaCDR convert rfc822-to-8bit (ORCPT ); Mon, 30 Aug 2010 22:03:17 -0400 Received: by pzk9 with SMTP id 9so2281402pzk.19 for ; Mon, 30 Aug 2010 19:03:17 -0700 (PDT) In-Reply-To: Sender: linux-ide-owner@vger.kernel.org List-Id: linux-ide@vger.kernel.org To: linux-ide@vger.kernel.org Upgraded to latest stable release - 2.6.35.4. Same errors: PM: Syncing filesystems ... done. PM: Preparing system for mem sleep =46reezing user space processes ... (elapsed 0.01 seconds) done. =46reezing remaining freezable tasks ... (elapsed 0.01 seconds) done. PM: Entering mem sleep Suspending console(s) (use no_console_suspend to debug) eth0: link up. scsi 0:0:0:0: Direct-Access ATA FUJITSU MJA2250B 0081 PQ: 0 AN= SI: 5 sd 0:0:0:0: Attached scsi generic sg0 type 0 ata2.00: detaching (SCSI 1:0:0:0) EXT4-fs error (device sda2): __ext4_get_inode_loc: inode #2885332: (comm udevd) unable to read inode block 11534477 sd 0:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/232 GiB) EXT4-fs error (device sda2): ext4_find_entry: inode #2884877: (comm udevd) reading directory lblock 0 sd 0:0:0:0: [sdc] Write Protect is off sd 0:0:0:0: [sdc] Mode Sense: 00 3a 00 00 sd 0:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sdc: scsi 1:0:0:0: CD-ROM HL-DT-ST DVDRW GS23N SB03 PQ: 0 AN= SI: 5 EXT4-fs error (device sda2): ext4_find_entry: inode #4456450: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #4456489: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #3670077: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #3670017: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #3670068: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #10485761: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #3670068: (comm gnome-panel) reading directory lblock 0 EXT4-fs error (device sda2): ext4_find_entry: inode #4456450: (comm gnome-panel) reading directory lblock 0 sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda caddy sr 1:0:0:0: Attached scsi CD-ROM sr0 sr 1:0:0:0: Attached scsi generic sg1 type 5 EXT4-fs error (device sda2): __ext4_get_inode_loc: inode #2885332: (comm udevd) unable to read inode block 11534477 EXT4-fs error (device sda2): __ext4_get_inode_loc: inode #2885332: (comm udevd) unable to read inode block 11534477 EXT4-fs error (device sda2): __ext4_get_inode_loc: inode #2885332: (comm udevd) unable to read inode block 11534477 EXT4-fs error (device sda2): __ext4_get_inode_loc: inode #2885332: (comm udevd) unable to read inode block 11534477 EXT4-fs error (device sda2): __ext4_get_inode_loc: inode #2885332: (comm udevd) unable to read inode block 11534477 sdc1 sdc2 sdc3 sd 0:0:0:0: [sdc] Attached SCSI disk On Mon, Aug 30, 2010 at 5:59 PM, Siddhartha Jain wrote: > Re-installed with encryption off and netconsole logging on. Same > result, that is, sda switches to sdc and everything goes haywire. > > eth0: link up. > ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) > ata1.00: configured for UDMA/100 > ata1: EH complete > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #2884877 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #2884877 offset 0 > sd 0:0:0:0: [sda] Stopping disk > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #13631490 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670077 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670077 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3677072 offset 0 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456489 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670077 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456489 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D4456517, block=3D17825828 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3691827 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3812945 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3681172 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670113 offset 0 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #2884877 offset 0 > scsi 0:0:0:0: Direct-Access =A0 =A0 ATA =A0 =A0 =A0FUJITSU MJA2250B 0= 081 PQ: 0 ANSI: 5 > sd 0:0:0:0: Attached scsi generic sg0 type 0 > ata2.00: detaching (SCSI 1:0:0:0) > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #2884877 offset 0 > sd 0:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/232 GiB) > sd 0:0:0:0: [sdc] Write Protect is off > sd 0:0:0:0: [sdc] Mode Sense: 00 3a 00 00 > sd 0:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't > support DPO or FUA > =A0sdc: > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456489 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670077 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670017 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670068 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #10485761 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670068 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > scsi 1:0:0:0: CD-ROM =A0 =A0 =A0 =A0 =A0 =A0HL-DT-ST DVDRW =A0GS23N =A0= =A0 SB03 PQ: 0 ANSI: 5 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456486 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > sr0: scsi3-mmc drive: 24x/24x writer cd/rw xa/form2 cdda caddy > sr 1:0:0:0: Attached scsi CD-ROM sr0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #2883586 offset 0 > sr 1:0:0:0: Attached scsi generic sg1 type 5 > EXT4-fs error (device sda2): ext4_find_entry: reading directory #2 of= fset 0 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > =A0sdc1 sdc2 sdc3 > sd 0:0:0:0: [sdc] Attached SCSI disk > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670077 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #3670026 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): ext4_find_entry: reading directory > #4456450 offset 0 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D2885332, block=3D11534477 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D13631490, block=3D54525984 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D13631490, block=3D54525984 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D13631490, block=3D54525984 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D13631490, block=3D54525984 > EXT4-fs error (device sda2): __ext4_get_inode_loc: unable to read > inode block - inode=3D13631490, block=3D54525984 > > > > On Mon, Aug 30, 2010 at 3:26 PM, Siddhartha Jain > wrote: >> Got into runlevel 3 and manually invoked suspend via "pm-suspend". O= n >> resume, got these logs via netconsole. For some reason, sda becomes >> sdc and all sorts of panicking ensues. >> >> >> PM: Syncing filesystems ... done. >> PM: Preparing system for mem sleep >> Freezing user space processes ... (elapsed 0.01 seconds) done. >> Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. >> PM: Entering mem sleep >> Suspending console(s) (use no_console_suspend to debug) >> eth0: link up. >> ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) >> ata2.00: configured for UDMA/133 >> ata2: EH complete >> Buffer I/O error on device dm-0, logical block 41791664 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41791665 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41791666 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41800003 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41963521 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41789440 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41789449 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41791667 >> lost page write due to I/O error on dm-0 >> Buffer I/O error on device dm-0, logical block 41791667 >> lost page write due to I/O error on dm-0 >> EXT3-fs: ext3_journal_dirty_data: aborting transaction: IO failure i= n >> ext3_journal_dirty_data >> EXT3-fs (dm-0): error in ext3_orphan_add: Readonly filesystem >> EXT3-fs (dm-0): error in ext3_ordered_write_end: IO failure >> ------------[ cut here ]------------ >> WARNING: at fs/buffer.c:1159 mark_buffer_dirty+0x2b/0x86() >> Hardware name: MacBookPro5,4 >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0Modules linked in: rfcomm >> sco bridge stp llc bnep l2cap sbs sbshc coretemp sunrpc >> cpufreq_ondemand acpi_cpufreq freq_table ip6t_REJECT nf_conntrack_ip= v6 >> ip6table_filter ip6_tables ipv6 netconsole configfs uinput b43 >> snd_hda_codec_cirrus snd_hda_intel mac80211 snd_hda_codec cfg80211 >> snd_hwdep snd_seq uvcvideo snd_seq_device ssb snd_pcm applesmc >> snd_timer videodev snd forcedeth v4l1_compat mmc_core shpchp >> v4l2_compat_ioctl32 btusb soundcore snd_page_alloc bluetooth >> i2c_nforce2 joydev input_polldev bcm5974 appleir rfkill mbp_nvidia_b= l >> microcode aes_x86_64 aes_generic xts gf128mul dm_crypt firewire_ohci >> usb_storage firewire_core crc_itu_t nouveau ttm drm_kms_helper drm >> i2c_algo_bit vid >> eo output i2c_core [last unloaded: scsi_wait_scan] >> Pid: 1989, comm: rsyslogd Not tainted 2.6.33.8-149.fc13.x86_64 #1 >> Call Trace: >> =A0[] warn_slowpath_common+0x77/0x8f >> =A0[] warn_slowpath_null+0xf/0x11 >> =A0[] mark_buffer_dirty+0x2b/0x86 >> =A0[] ext3_commit_super.clone.0+0x54/0x64 >> =A0[] ext3_handle_error+0x90/0xb7 >> =A0[] __ext3_std_error+0x72/0x8f >> =A0[] __ext3_journal_stop+0x3f/0x49 >> =A0[] ext3_ordered_write_end+0xd7/0x11b >> =A0[] generic_file_buffered_write+0x165/0x25f >> =A0[] ? ext3_dirty_inode+0x7b/0x84 >> =A0[] __generic_file_aio_write+0x247/0x27c >> =A0[] generic_file_aio_write+0x58/0xa2 >> =A0[] do_sync_write+0xbf/0xfc >> =A0[] ? pick_next_task+0x22/0x41 >> =A0[] ? schedule+0x850/0x8e6 >> =A0[] ? native_sched_clock+0x2d/0x5f >> =A0[] ? security_file_permission+0x11/0x13 >> =A0[] vfs_write+0xa9/0x106 >> =A0[] sys_write+0x45/0x69 >> =A0[] system_call_fastpath+0x16/0x1b >> ---[ end trace 65d387dd571aab2f ]--- >> JBD: Detected IO errors while flushing file data on dm-0 >> Aborting journal on device dm-0. >> EXT3-fs (dm-0): error in ext3_orphan_add: Journal has aborted >> EXT3-fs (dm-0): error in ext3_truncate: Journal has aborted >> JBD: Detected IO errors while flushing file data on dm-0 >> EXT3-fs (dm-0): error: ext3_journal_start_sb: Detected aborted journ= al >> EXT3-fs (dm-0): error: ext3_journal_start_sb: Detected aborted journ= al >> EXT3-fs (dm-0): error: remounting filesystem read-only >> INFO: task ata_aux:27 blocked for more than 120 seconds. >> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this mes= sage. >> ata_aux =A0 =A0 =A0 D ffff8800057157c0 =A0 =A0 0 =A0 =A027 =A0 =A0 =A0= 2 0x00000000 >> =A0ffff88013b441950 0000000000000046 ffff8801382a0000 00000000000000= 00 >> =A0ffff88013b4418d0 ffffffff812bb5f8 ffff88013b441960 ffff88013b441f= d8 >> =A0ffff88013b441fd8 000000000000f9b0 00000000000157c0 ffff88013b43b2= 68 >> Call Trace: >> =A0[] ? __scsi_get_command+0x15/0x90 >> =A0[] schedule_timeout+0x31/0xde >> =A0[] ? kobject_put+0x47/0x4b >> =A0[] ? put_device+0x12/0x14 >> =A0[] wait_for_common+0xd1/0x12c >> =A0[] ? default_wake_function+0x0/0xf >> =A0[] ? __generic_unplug_device+0x2d/0x32 >> =A0[] wait_for_completion+0x18/0x1a >> =A0[] blk_execute_rq+0xa1/0xd0 >> =A0[] ? write_msg+0xe5/0xf4 [netconsole] >> =A0[] ? blk_get_request+0x3c/0x72 >> =A0[] scsi_execute+0xf1/0x143 >> =A0[] scsi_execute_req+0xa4/0xd6 >> =A0[] sd_sync_cache+0x95/0xf3 >> =A0[] ? printk+0x3c/0x40 >> =A0[] sd_shutdown+0x93/0x116 >> =A0[] sd_remove+0x56/0x8b >> =A0[] __device_release_driver+0x70/0xc3 >> =A0[] device_release_driver+0x1e/0x2b >> =A0[] bus_remove_device+0xb1/0xe0 >> =A0[] device_del+0x135/0x1a1 >> =A0[] __scsi_remove_device+0x4d/0x98 >> =A0[] scsi_remove_device+0x21/0x2e >> =A0[] ata_scsi_handle_link_detach+0xfe/0x131 >> =A0[] ata_scsi_hotplug+0x26/0x62 >> =A0[] worker_thread+0x1a4/0x232 >> =A0[] ? ata_scsi_hotplug+0x0/0x62 >> =A0[] ? autoremove_wake_function+0x0/0x34 >> =A0[] ? worker_thread+0x0/0x232 >> =A0[] kthread+0x7a/0x82 >> =A0[] kernel_thread_helper+0x4/0x10 >> =A0[] ? kthread+0x0/0x82 >> =A0[] ? kernel_thread_helper+0x0/0x10 >> sd 0:0:0:0: timing out command, waited 180s >> >> >> Thanks, >> >> - Siddhartha >> >> >> On Mon, Aug 30, 2010 at 8:25 AM, Siddhartha Jain >> wrote: >>> Hi Tejun, >>> >>> Will get more debugging info by setting up netconsole. Meanwhile, >>> syslog did glean some important info, I think. Looks like, for some >>> reason, after resume, device mapping for the hdd changes from sda t= o >>> sdc. Please see logs below. For ease of troubleshooting, I >>> re-installed the box with stock Fedora 13 x64 with no modifications >>> except that dmcrypt is turned on for root and swap (so using Nouvea= u >>> display drivers instead of Nvidia). >>> >>> Aug 29 19:13:45 192.168.1.199 kernel: PM: Syncing filesystems ... d= one. >>> Aug 29 19:13:45 192.168.1.199 kernel: PM: Preparing system for mem = sleep >>> Aug 29 19:18:57 192.168.1.199 kernel: scsi 0:0:0:0: Direct-Access >>> ATA =A0 =A0 =A0FUJITSU MJA2250B 0081 PQ: 0 ANSI: 5 >>> Aug 29 19:18:57 192.168.1.199 kernel: sd 0:0:0:0: Attached scsi >>> generic sg0 type 0 >>> Aug 29 19:18:57 192.168.1.199 kernel: ata2.00: detaching (SCSI 1:0:= 0:0) >>> Aug 29 19:18:57 192.168.1.199 kernel: sd 0:0:0:0: [sdc] 488397168 >>> 512-byte logical blocks: (250 GB/232 GiB) >>> Aug 29 19:18:57 192.168.1.199 kernel: sd 0:0:0:0: [sdc] Write Prote= ct is off >>> Aug 29 19:18:57 192.168.1.199 kernel: sd 0:0:0:0: [sdc] Mode Sense:= 00 3a 00 00 >>> Aug 29 19:18:57 192.168.1.199 kernel: sd 0:0:0:0: [sdc] Write cache= : >>> enabled, read cache: enabled, doesn't support DPO or FUA >>> Aug 29 19:18:57 192.168.1.199 kernel: sdc: >>> Aug 29 19:18:57 192.168.1.199 kernel: scsi 1:0:0:0: CD-ROM >>> HL-DT-ST DVDRW =A0GS23N =A0 =A0 SB03 PQ: 0 ANSI: 5 >>> Aug 29 19:18:57 192.168.1.199 kernel: sr0: scsi3-mmc drive: 24x/24x >>> writer cd/rw xa/form2 cdda caddy >>> Aug 29 19:18:57 192.168.1.199 kernel: sr 1:0:0:0: Attached scsi CD-= ROM sr0 >>> Aug 29 19:18:57 192.168.1.199 kernel: sr 1:0:0:0: Attached scsi >>> generic sg1 type 5 >>> Aug 29 19:18:58 192.168.1.199 kernel: sdc1 sdc2 sdc3 >>> Aug 29 19:18:58 192.168.1.199 kernel: sd 0:0:0:0: [sdc] Attached SC= SI disk >>> Aug 29 19:20:20 192.168.1.199 ntpd[1466]: 0.0.0.0 c61c 0c clock_ste= p -0.389692 s >>> Aug 29 19:20:20 192.168.1.199 ntpd[1466]: 0.0.0.0 c614 04 freq_mode >>> Aug 29 19:20:21 192.168.1.199 ntpd[1466]: 0.0.0.0 c618 08 no_sys_pe= er >>> Aug 29 19:22:29 192.168.1.199 sshd[2425]: WARNING: no suitable prim= es >>> in /etc/ssh/primes >>> Aug 29 19:22:29 192.168.1.199 rsyslogd: /var/log/secure >>> Aug 29 19:22:37 192.168.1.199 auditd[1734]: Record was not written = to >>> disk (Read-only file system) >>> Aug 29 19:22:37 192.168.1.199 auditd[1734]: write: Audit daemon >>> detected an error writing an event to disk (Connection refused) >>> Aug 29 19:22:37 192.168.1.199 sshd[2425]: Failed password for sjain >>> from 192.168.1.100 port 49902 ssh2 >>> Aug 29 19:22:37 192.168.1.199 auditd[2428]: Audit daemon failed to = exec (null) >>> Aug 29 19:22:37 192.168.1.199 auditd[2428]: The audit daemon is exi= ting. >>> Aug 29 19:22:37 192.168.1.199 auditd[1734]: Record was not written = to >>> disk (Read-only file system) >>> Aug 29 19:22:37 192.168.1.199 auditd[1734]: write: Audit daemon >>> detected an error writing an event to disk (Read-only file system) >>> Aug 29 19:22:37 192.168.1.199 auditd[2429]: Audit daemon failed to = exec (null) >>> Aug 29 19:22:37 192.168.1.199 auditd[2429]: The audit daemon is exi= ting. >>> Aug 29 19:22:37 192.168.1.199 kernel: type=3D1305 >>> audit(1283134957.511:19078): audit_pid=3D0 old=3D1734 auid=3D429496= 7295 >>> ses=3D4294967295 res=3D1 >>> Aug 29 19:22:37 192.168.1.199 kernel: type=3D1305 >>> audit(1283134957.511:19079): audit_pid=3D0 old=3D0 auid=3D429496729= 5 >>> ses=3D4294967295 res=3D1 >>> Aug 29 19:22:54 192.168.1.199 kernel: EXT3-fs error (device dm-0): >>> ext3_find_entry: reading directory #10445218 offset 0 >>> Aug 29 19:22:54 192.168.1.199 sshd[2426]: Connection closed by 192.= 168.1.100 >>> Aug 29 19:23:17 192.168.1.199 auditd[2428]: Error setting audit dae= mon >>> pid (Resource temporarily unavailable) >>> Aug 29 19:23:18 192.168.1.199 auditd[2429]: Error setting audit dae= mon >>> pid (Resource temporarily unavailable) >>> Aug 29 19:34:26 192.168.1.199 kernel: CE: hpet increasing min_delta= _ns >>> to 15000 nsec >>> Aug 29 19:35:46 192.168.1.199 ntpd[1466]: 0.0.0.0 c612 02 freq_set >>> kernel -65.666 PPM >>> Aug 29 19:35:46 192.168.1.199 ntpd[1466]: 0.0.0.0 c615 05 clock_syn= c >>> Aug 29 19:38:26 192.168.1.199 kernel: EXT3-fs error (device dm-0): >>> ext3_find_entry: reading directory #1803721 offset 0 >>> >>> Odd? >>> >>> Thanks, >>> >>> - Siddhartha >>> >>> >>> >>> On Mon, Aug 30, 2010 at 5:55 AM, Tejun Heo wrote: >>>> On 08/28/2010 10:28 PM, Siddhartha Jain wrote: >>>>> I am going to try pointing rsyslog at a remote syslog server to s= ee if I >>>>> can capture what happens at resume-time but any other pointers to >>>>> debug/troubleshoot this issue will be helpful. >>>> >>>> Setting up netconsole (see Documentation/networking/netconsole.txt= in >>>> the kernel source tree) would be better. >>>> >>>> Thanks. >>>> >>>> -- >>>> tejun >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-id= e" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at =A0http://vger.kernel.org/majordomo-info.ht= ml >>>> > --=20 - Siddhartha =A0 WV6U