From: Ray Bond <rmbond@purdue.edu>
To: jaegeuk.kim@samsung.com
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: PROBLEM: After power loss, seg fault on boot tracing to fs/f2fs/recovery.c:270
Date: Fri, 26 Jul 2013 09:40:19 -0400 [thread overview]
Message-ID: <1374846019.23354.18.camel@E6510ArchLinux> (raw)
In-Reply-To: <1374845156.26443.59.camel@kjgkr>
Thank you very much for looking into this. I'm glad to hear that it is a
problem that has been resolved upstream. Everything important on the
disk is backed up elsewhere, so reformatting is no big deal.
Thanks again,
Ray
-----Original Message-----
From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
To: Ray Bond <rmbond@purdue.edu>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: PROBLEM: After power loss, seg fault on boot tracing to
fs/f2fs/recovery.c:270
Date: Fri, 26 Jul 2013 22:25:56 +0900
Hi,
Very unfortunately, such the *unreachable NIDs* error was resolved by
the recent patches fixing several recovery routines. So it needs to use
the latest F2FS source urgently.
Even the worse thing is that we don't have fsck.f2fs fixing the file
system consistency, so that it needs to reformat the failed disk.
Sorry for that.
But, I strongly convince that most of recovery bugs have been fixed so
far. Hence you can believe that the current F2FS is very much stable
than ever before.
Thanks,
2013-07-25 (목), 11:43 -0400, Ray Bond:
> No problem. Since the Arch repo's version of f2fs-tools does not include
> fsck.f2fs, I built it from your git repo
> (git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git)
> using an Arch Linux install usb on the same machine, with Linux
> 3.9.8-1 .
>
> The output on the main system partition is:
> Info: sector size = 512
> Info: total sectors = 83879936 (in 512bytes)
>
> +--------------------------------------------------------+
> | Super block |
> +--------------------------------------------------------+
> magic [0xf2f52010 : 4076150800]
> major_ver [0x 1 : 1]
> minor_ver [0x 0 : 0]
> log_sectorsize [0x 9 : 9]
> log_sectors_per_block [0x 3 : 3]
> log_blocksize [0x c : 12]
> log_blocks_per_seg [0x 9 : 9]
> segs_per_sec [0x 1 : 1]
> secs_per_zone [0x 1 : 1]
> checksum_offset [0x 0 : 0]
> block_count [0x 9ffd00 : 10484992]
> section_count [0x 4f78 : 20344]
> segment_count [0x 4ffe : 20478]
> segment_count_ckpt [0x 2 : 2]
> segment_count_sit [0x 2 : 2]
> segment_count_nat [0x 5a : 90]
> segment_count_ssa [0x 28 : 40]
> segment_count_main [0x 4f78 : 20344]
> segment0_blkaddr [0x 100 : 256]
> cp_blkaddr [0x 100 : 256]
> sit_blkaddr [0x 500 : 1280]
> nat_blkaddr [0x 900 : 2304]
> ssa_blkaddr [0x bd00 : 48384]
> main_blkaddr [0x 10d00 : 68864]
> root_ino [0x 3 : 3]
> node_ino [0x 1 : 1]
> meta_ino [0x 2 : 2]
>
>
> +--------------------------------------------------------+
> | Checkpoint |
> +--------------------------------------------------------+
> checkpoint_ver [0x bc7 : 3015]
> user_block_count [0x 96d000 : 9883648]
> valid_block_count [0x 5660bb : 5660859]
> rsvd_segment_count [0x 19 : 25]
> overprov_segment_count [0x 410 : 1040]
> free_segment_count [0x 26ab : 9899]
> alloc_type[CURSEG_HOT_NODE] [0x 0 : 0]
> alloc_type[CURSEG_WARM_NODE] [0x 0 : 0]
> alloc_type[CURSEG_COLD_NODE] [0x 0 : 0]
> cur_node_segno[0] [0x 4567 : 17767]
> cur_node_segno[1] [0x 4562 : 17762]
> cur_node_segno[2] [0x 441b : 17435]
> cur_node_blkoff[0] [0x 139 : 313]
> cur_node_blkoff[1] [0x ad : 173]
> cur_node_blkoff[2] [0x 193 : 403]
> alloc_type[CURSEG_HOT_DATA] [0x 0 : 0]
> alloc_type[CURSEG_WARM_DATA] [0x 0 : 0]
> alloc_type[CURSEG_COLD_DATA] [0x 0 : 0]
> cur_data_segno[0] [0x 4569 : 17769]
> cur_data_segno[1] [0x 46d : 1133]
> cur_data_segno[2] [0x 456 : 1110]
> cur_data_blkoff[0] [0x 17 : 23]
> cur_data_blkoff[1] [0x 67 : 103]
> cur_data_blkoff[2] [0x 138 : 312]
> ckpt_flags [0x 6 : 6]
> cp_pack_total_block_count [0x 5 : 5]
> cp_pack_start_sum [0x 2 : 2]
> valid_node_count [0x 79f5b : 499547]
> valid_inode_count [0x 798df : 497887]
> next_free_nid [0x 7cf1c : 511772]
> sit_ver_bitmap_bytesize [0x 40 : 64]
> nat_ver_bitmap_bytesize [0x b40 : 2880]
> checksum_offset [0x ffc : 4092]
> elapsed_time [0x 4af7e6 : 4913126]
> sit_nat_version_bitmap[0] [0x 23 : 35]
>
>
> [build_nat_area_bitmap:1035] valid nat entries (block_addr != 0x0) [0x
> 7a3b2 : 500658]
> [build_sit_area_bitmap: 941] Blocks [0x5185b1] Free Segs [0x26ab]
>
>
> NID[0xdebbc] is unreachable
> NID[0x11f7f7] is unreachable
> [FSCK] Unreachable nat entries [Fail] [0x2]
> [FSCK] SIT valid block bitmap checking [Fail]
> [FSCK] Hard link checking for regular file [Ok..] [0x457]
> [FSCK] valid_block_count matching with CP [Fail] [0x5664f8]
> [FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x7a3b0]
> [FSCK] valid_node_count matcing with CP (nat lookup) [Fail] [0x7a3b2]
> [FSCK] valid_inode_count matched with CP [Fail] [0x798dd]
>
> Done.
>
> The output on the partition mounted to /home (also f2fs) is:
>
> Info: sector size = 512
> Info: total sectors = 140073871 (in 512bytes)
>
> +--------------------------------------------------------+
> | Super block |
> +--------------------------------------------------------+
> magic [0xf2f52010 : 4076150800]
> major_ver [0x 1 : 1]
> minor_ver [0x 0 : 0]
> log_sectorsize [0x 9 : 9]
> log_sectors_per_block [0x 3 : 3]
> log_blocksize [0x c : 12]
> log_blocks_per_seg [0x 9 : 9]
> segs_per_sec [0x 1 : 1]
> secs_per_zone [0x 1 : 1]
> checksum_offset [0x 0 : 0]
> block_count [0x 10b2b71 : 17509233]
> section_count [0x 84d5 : 34005]
> segment_count [0x 8594 : 34196]
> segment_count_ckpt [0x 2 : 2]
> segment_count_sit [0x 4 : 4]
> segment_count_nat [0x 76 : 118]
> segment_count_ssa [0x 43 : 67]
> segment_count_main [0x 84d5 : 34005]
> segment0_blkaddr [0x 200 : 512]
> cp_blkaddr [0x 200 : 512]
> sit_blkaddr [0x 600 : 1536]
> nat_blkaddr [0x e00 : 3584]
> ssa_blkaddr [0x fa00 : 64000]
> main_blkaddr [0x 18000 : 98304]
> root_ino [0x 3 : 3]
> node_ino [0x 1 : 1]
> meta_ino [0x 2 : 2]
>
>
> +--------------------------------------------------------+
> | Checkpoint |
> +--------------------------------------------------------+
> checkpoint_ver [0x c5be : 50622]
> user_block_count [0x fc3200 : 16527872]
> valid_block_count [0x adc6d9 : 11388633]
> rsvd_segment_count [0x 19 : 25]
> overprov_segment_count [0x 6bc : 1724]
> free_segment_count [0x 356f : 13679]
> alloc_type[CURSEG_HOT_NODE] [0x 0 : 0]
> alloc_type[CURSEG_WARM_NODE] [0x 0 : 0]
> alloc_type[CURSEG_COLD_NODE] [0x 0 : 0]
> cur_node_segno[0] [0x 83f0 : 33776]
> cur_node_segno[1] [0x 83ff : 33791]
> cur_node_segno[2] [0x 8488 : 33928]
> cur_node_blkoff[0] [0x 1a7 : 423]
> cur_node_blkoff[1] [0x 1f2 : 498]
> cur_node_blkoff[2] [0x 74 : 116]
> alloc_type[CURSEG_HOT_DATA] [0x 0 : 0]
> alloc_type[CURSEG_WARM_DATA] [0x 0 : 0]
> alloc_type[CURSEG_COLD_DATA] [0x 0 : 0]
> cur_data_segno[0] [0x 137a : 4986]
> cur_data_segno[1] [0x 12eb : 4843]
> cur_data_segno[2] [0x fb6 : 4022]
> cur_data_blkoff[0] [0x 5b : 91]
> cur_data_blkoff[1] [0x a9 : 169]
> cur_data_blkoff[2] [0x 13b : 315]
> ckpt_flags [0x 6 : 6]
> cp_pack_total_block_count [0x 5 : 5]
> cp_pack_start_sum [0x 2 : 2]
> valid_node_count [0x a72f : 42799]
> valid_inode_count [0x 7d5b : 32091]
> next_free_nid [0x 1c34f : 115535]
> sit_ver_bitmap_bytesize [0x 80 : 128]
> nat_ver_bitmap_bytesize [0x ec0 : 3776]
> checksum_offset [0x ffc : 4092]
> elapsed_time [0x 4aca1f : 4901407]
> sit_nat_version_bitmap[0] [0x 58 : 88]
>
>
> [build_nat_area_bitmap:1035] valid nat entries (block_addr != 0x0) [0x
> a7b9 : 42937]
> [build_sit_area_bitmap: 941] Blocks [0x9c05eb] Free Segs [0x356f]
>
>
> [FSCK] Unreachable nat entries [Ok..] [0x0]
> [FSCK] SIT valid block bitmap checking [Ok..]
> [FSCK] Hard link checking for regular file [Ok..] [0x0]
> [FSCK] valid_block_count matching with CP [Fail] [0xadc763]
> [FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0xa7b9]
> [FSCK] valid_node_count matcing with CP (nat lookup) [Fail] [0xa7b9]
> [FSCK] valid_inode_count matched with CP [Ok..] [0x7d5b]
>
> Done.
>
> I also ran fsck.f2fs on these partitions with higher debug levels, but
> the output files are somewhat large, so I won't bother sending those
> unless you need them.
>
> Thanks,
> Ray
>
>
> -----Original Message-----
> From: Jaegeuk Kim <jaegeuk.kim@samsung.com>
> To: Raymond M Bond <rmbond@purdue.edu>
> Cc: linux-f2fs-devel@lists.sourceforge.net
> Subject: Re: PROBLEM: After power loss, seg fault on boot tracing to
> fs/f2fs/recovery.c:270
> Date: Thu, 25 Jul 2013 20:10:03 +0900
>
> Hi,
> Thank you for the report.
>
> If possible, could you run fsck.f2fs to the failed device?
> Otherwise, can you send the disk image to me?
>
> Thanks,
>
> 2013-07-24 (수), 10:15 -0400, Raymond M Bond:
> > [1.] One line summary of the problem:
> > After power loss, seg fault on boot tracing to fs/f2fs/recovery.c:270
> >
> > [2.] Full description of the problem/report:
> > Laptop running Arch Linux kernel 3.10.2-ck, booting with the EFI boot stub using rEFInd. The machine has a Samsung 840 SSD with the root partition formatted to f2fs. Laptop battery must have run down without the system hibernating or shutting down gracefully. Boot fails with a segmentation fault reporting a bug at fs/f2fs/recovery.c:270
> >
> > [ 3.671739] ------------[ cut here ]------------
> > [ 3.671795] kernel BUG at fs/f2fs/recovery.c:270!
> > [ 3.671842] invalid opcode: 0000 [#1] PREEMPT SMP
> > [ 3.671914] Modules linked in: sr_mod sd_mod cdrom ahci libahci libata sdhci_pci ehci_pci ehci_hcd sdhci scsi_mod mmc_core usbcore usb_common f2fs
> > [ 3.672149] CPU: 1 PID: 102 Comm: mount Not tainted 3.10.1-2-ck #1
> > [ 3.672209] Hardware name: Dell Inc. Latitude E4310/0D8H24, BIOS A05 11/20/2010
> > [ 3.672277] task: ffff88011a1ba170 ti: ffff88011aeb6000 task.ti: ffff88011aeb6000
> > [ 3.672346] RIP: 0010:[<ffffffffa0016a1b>] [<ffffffffa0016a1b>] recover_fsync_data+0xdbb/0xe00 [f2fs]
> > [ 3.672446] RSP: 0018:ffff88011aeb7c28 EFLAGS: 00010297
> > [ 3.672498] RAX: 000000001fffffff RBX: 000000002007fffb RCX: ffffea0004653e80
> > [ 3.672564] RDX: ffff8801194fa000 RSI: 000000000008101d RDI: ffff88011a043e60
> > [ 3.672631] RBP: ffff88011aeb7d20 R08: 000000000007cb9b R09: ffff88011a51aa28
> > [ 3.672701] R10: ffff880000000000 R11: 0000160000000000 R12: ffff88011aeb7ca0
> > [ 3.672767] R13: 0000000000000000 R14: ffff88011943c000 R15: ffff88011a56d000
> > [ 3.672834] FS: 00007fb9b1d5c780(0000) GS:ffff8800d7240000(0000) knlGS:0000000000000000
> > [ 3.672909] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> > [ 3.672963] CR2: 00007f92ab893dee CR3: 000000011a365000 CR4: 00000000000007e0
> > [ 3.673029] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> > [ 3.673095] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> > [ 3.673160] Stack:
> > [ 3.673184] ffff88011943cfe8 ffff88011a56d000 0000000000000bc7 ffffea0004650f00
> > [ 3.673278] 0000000000000003 ffff88011a2fc000 ffff88011a571100 00000000008bd1fb
> > [ 3.673376] ffffffff2007fffb ffff88011943c168 200803f500000000 ffff88011a560280
> > [ 3.673469] Call Trace:
> > [ 3.673504] [<ffffffffa0008815>] f2fs_fill_super+0x855/0x880 [f2fs]
> > [ 3.673572] [<ffffffff8116e620>] mount_bdev+0x1c0/0x200
> > [ 3.673628] [<ffffffffa0007fc0>] ? validate_superblock+0x160/0x160 [f2fs]
> > [ 3.673698] [<ffffffffa0007945>] f2fs_mount+0x15/0x20 [f2fs]
> > [ 3.673755] [<ffffffff8116ef59>] mount_fs+0x39/0x1b0
> > [ 3.673807] [<ffffffff81129b10>] ? __alloc_percpu+0x10/0x20
> > [ 3.673866] [<ffffffff811881f7>] vfs_kern_mount+0x67/0x100
> > [ 3.675506] [<ffffffff8118a81e>] do_mount+0x23e/0xa20
> > [ 3.677151] [<ffffffff8112588b>] ? strndup_user+0x4b/0xf0
> > [ 3.678813] [<ffffffff8118b083>] SyS_mount+0x83/0xc0
> > [ 3.680478] [<ffffffff814a919d>] system_call_fastpath+0x1a/0x1f
> > [ 3.682142] Code: e9 ef f8 ff ff 0f 0b 0f 0b 41 89 c6 e9 7e f5 ff ff 48 8b 3d 60 9b 00 00 4c 89 f6 4c 89 fb 41 89 c5 e8 da d7 13 e1 e9 c1 fe ff ff <0f> 0b 48 8b bd 20 ff ff ff 89 85 68 ff ff ff e8 b1 50 0f e1 8b
> > [ 3.687914] RIP [<ffffffffa0016a1b>] recover_fsync_data+0xdbb/0xe00 [f2fs]
> > [ 3.689724] RSP <ffff88011aeb7c28>
> > [ 3.691513] ---[ end trace c8dca230095ac7dd ]---
> >
> > [3.] Keywords (i.e., modules, networking, kernel):
> > f2fs filesystem kernel
> >
> > [4.] Kernel information
> > Running kernel 3.10.2-ck-nehalem kernel. This is a kernel version patched with Con Kolivas' patch set, and compiled with optimizations for the nehalem architecture. Although the most notable difference in this patched kernel is the BFQ io scheduler, I am using the CFQ io scheduler on this machine.
> >
> > [4.1.] Kernel version (from /proc/version):
> > Linux version 3.10.1-2-ck (squishy@ease) (gcc version 4.8.1 (GCC) ) #1 SMP PREEMPT Sun Jul 14 07:14:59 EDT 2013
> >
> > [4.2.] Kernel .config file:
> > I am sorry, I don't have this on hand at the moment. If this is critical, I can boot this machine off of a USB iso and try to track down the config file.
> >
> > [8.] Environment
> > [8.1.] Software (add the output of the ver_linux script here)
> > Bootloader: rEFInd and EFI boot stub
> > linux_ver output is incomplete because ld and ldd were not found.
> > The information from linux_ver output that is not redundant is as follows:
> > mount assert
> > module-init-tools 14
> > Linux C Library 2.17
> > Procps '--version'
> > Kbd 79:
> > Sh-utils --v
> > Modules loaded usb_storage sr_mod sd_mopd cdrom ahci libahci libata sdhci_pci ehci_pci ehci_hcd sdhci scsi_mod mmc_core usbcore usb_common f2fs
> >
> >
> > [8.2.] Processor information (from /proc/cpuinfo):
> > processor : 0
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 37
> > model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
> > stepping : 5
> > microcode : 0x2
> > cpu MHz : 2660.165
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 0
> > cpu cores : 2
> > apicid : 0
> > initial apicid : 0
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 11
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm ida arat dtherm tpr_shadow vnmi flexpriority ept vpid
> > bogomips : 5322.01
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 1
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 37
> > model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
> > stepping : 5
> > microcode : 0x2
> > cpu MHz : 2660.165
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 2
> > cpu cores : 2
> > apicid : 4
> > initial apicid : 4
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 11
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm ida arat dtherm tpr_shadow vnmi flexpriority ept vpid
> > bogomips : 5322.01
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 2
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 37
> > model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
> > stepping : 5
> > microcode : 0x2
> > cpu MHz : 2660.165
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 0
> > cpu cores : 2
> > apicid : 1
> > initial apicid : 1
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 11
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm ida arat dtherm tpr_shadow vnmi flexpriority ept vpid
> > bogomips : 5322.01
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > processor : 3
> > vendor_id : GenuineIntel
> > cpu family : 6
> > model : 37
> > model name : Intel(R) Core(TM) i5 CPU M 560 @ 2.67GHz
> > stepping : 5
> > microcode : 0x2
> > cpu MHz : 2660.165
> > cache size : 3072 KB
> > physical id : 0
> > siblings : 4
> > core id : 2
> > cpu cores : 2
> > apicid : 5
> > initial apicid : 5
> > fpu : yes
> > fpu_exception : yes
> > cpuid level : 11
> > wp : yes
> > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt aes lahf_lm ida arat dtherm tpr_shadow vnmi flexpriority ept vpid
> > bogomips : 5322.01
> > clflush size : 64
> > cache_alignment : 64
> > address sizes : 36 bits physical, 48 bits virtual
> > power management:
> >
> > [8.3.] Module information (from /proc/modules):
> > usb_storage 47751 1 - Live 0xffffffffa01cc000
> > sr_mod 14738 0 - Live 0xffffffffa01c4000
> > sd_mod 30602 4 - Live 0xffffffffa01b7000
> > cdrom 34560 1 sr_mod, Live 0xffffffffa01a9000
> > ahci 22728 1 - Live 0xffffffffa019d000
> > libahci 21201 1 ahci, Live 0xffffffffa0191000
> > libata 168680 2 ahci,libahci, Live 0xffffffffa0150000
> > sdhci_pci 11819 0 - Live 0xffffffffa0142000
> > ehci_pci 4120 0 - Live 0xffffffffa013f000
> > ehci_hcd 46712 1 ehci_pci, Live 0xffffffffa011b000
> > sdhci 28627 1 sdhci_pci, Live 0xffffffffa010f000
> > scsi_mod 127453 4 usb_storage,sr_mod,sd_mod,libata, Live 0xffffffffa00db000
> > mmc_core 94875 2 sdhci_pci,sdhci, Live 0xffffffffa0076000
> > usbcore 176799 3 usb_storage,ehci_pci,ehci_hcd, Live 0xffffffffa0035000
> > usb_common 1648 1 usbcore, Live 0xffffffffa0031000
> > f2fs 144160 3 - Live 0xffffffffa0000000
> >
> > [8.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
> > /proc/ioports:
> > 0000-0cf7 : PCI Bus 0000:00
> > 0000-001f : dma1
> > 0020-0021 : pic1
> > 0040-0043 : timer0
> > 0050-0053 : timer1
> > 0060-0060 : keyboard
> > 0064-0064 : keyboard
> > 0070-0077 : rtc0
> > 0080-008f : dma page reg
> > 00a0-00a1 : pic2
> > 00c0-00df : dma2
> > 00f0-00ff : fpu
> > 0400-047f : pnp 00:04
> > 0400-0403 : ACPI PM1a_EVT_BLK
> > 0404-0405 : ACPI PM1a_CNT_BLK
> > 0408-040b : ACPI PM_TMR
> > 0420-042f : ACPI GPE0_BLK
> > 0450-0450 : ACPI PM2_CNT_BLK
> > 0500-057f : pnp 00:04
> > 0680-069f : pnp 00:04
> > 0930-0930 : EC data
> > 0934-0934 : EC cmd
> > 0cf8-0cff : PCI conf1
> > 0d00-ffff : PCI Bus 0000:00
> > 1000-1003 : pnp 00:04
> > 1004-1013 : pnp 00:04
> > 164e-164f : pnp 00:04
> > 2000-2fff : PCI Bus 0000:04
> > 3000-3fff : PCI Bus 0000:03
> > 4000-4fff : PCI Bus 0000:02
> > 5000-5fff : PCI Bus 0000:01
> > 6000-601f : 0000:00:1f.3
> > 6020-603f : 0000:00:1f.2
> > 6020-603f : ahci
> > 6040-605f : 0000:00:19.0
> > 6060-6063 : 0000:00:1f.2
> > 6060-6063 : ahci
> > 6070-6077 : 0000:00:1f.2
> > 6070-6077 : ahci
> > 6080-6083 : 0000:00:1f.2
> > 6080-6083 : ahci
> > 6090-6097 : 0000:00:1f.2
> > 6090-6097 : ahci
> > 60b0-60b7 : 0000:00:02.0
> > ffff-ffff : pnp 00:04
> >
> > /proc/iomem:
> > 00000000-00000fff : reserved
> > 00001000-0009ffff : System RAM
> > 000a0000-000bffff : PCI Bus 0000:00
> > 000a0000-000bffff : reserved
> > 000c0000-000cedff : Video ROM
> > 000d4000-000d7fff : PCI Bus 0000:00
> > 000d8000-000dbfff : PCI Bus 0000:00
> > 000dc000-000dffff : PCI Bus 0000:00
> > 000f0000-000fffff : System ROM
> > 00100000-d7761017 : System RAM
> > 02000000-024ad1c2 : Kernel code
> > 024ad1c3-028b017f : Kernel data
> > 029c8000-02b00fff : Kernel bss
> > d7761018-d7771057 : System RAM
> > d7771058-d777d017 : System RAM
> > d777d018-d778b857 : System RAM
> > d778b858-db1befff : System RAM
> > db1bf000-db25efff : reserved
> > db25f000-db27efff : ACPI Tables
> > db27f000-db36efff : ACPI Non-volatile Storage
> > db36f000-db3fefff : reserved
> > db3ff000-db3fffff : System RAM
> > db400000-dbffffff : reserved
> > ddc00000-dfffffff : reserved
> > e0000000-feafffff : PCI Bus 0000:00
> > e0000000-efffffff : 0000:00:02.0
> > e0000000-e01d4fff : efifb
> > f0000000-f03fffff : 0000:00:02.0
> > f0400000-f17fffff : PCI Bus 0000:04
> > f1800000-f2bfffff : PCI Bus 0000:03
> > f1830000-f18300ff : 0000:03:00.0
> > f1830000-f18300ff : mmc0
> > f2c00000-f3ffffff : PCI Bus 0000:02
> > f2c00000-f2c0ffff : 0000:02:00.0
> > f4000000-f53fffff : PCI Bus 0000:01
> > f5400000-f541ffff : 0000:00:19.0
> > f5420000-f5420fff : 0000:00:1f.6
> > f5430000-f54300ff : 0000:00:1f.3
> > f5440000-f54407ff : 0000:00:1f.2
> > f5440000-f54407ff : ahci
> > f5450000-f54503ff : 0000:00:1d.0
> > f5450000-f54503ff : ehci_hcd
> > f5460000-f5463fff : 0000:00:1b.0
> > f5470000-f54703ff : 0000:00:1a.0
> > f5470000-f54703ff : ehci_hcd
> > f5480000-f5480fff : 0000:00:19.0
> > f54c0000-f54c0fff : pnp 00:09
> > f5500000-f56fffff : PCI Bus 0000:01
> > f5700000-f58fffff : PCI Bus 0000:02
> > f5900000-f5afffff : PCI Bus 0000:03
> > f5b00000-f5cfffff : PCI Bus 0000:04
> > f8000000-fbffffff : PCI MMCONFIG 0000 [bus 00-3f]
> > f8000000-fbffffff : reserved
> > f8000000-fbffffff : pnp 00:09
> > fec00000-fec00fff : reserved
> > fec00000-fec003ff : IOAPIC 0
> > fed00000-fed003ff : HPET 0
> > fed10000-fed13fff : reserved
> > fed10000-fed13fff : pnp 00:09
> > fed18000-fed19fff : reserved
> > fed18000-fed18fff : pnp 00:09
> > fed19000-fed19fff : pnp 00:09
> > fed1c000-fed1ffff : reserved
> > fed1c000-fed1ffff : pnp 00:09
> > fed20000-fed3ffff : pnp 00:09
> > fed45000-fed8ffff : pnp 00:09
> > fed90000-fed90fff : dmar0
> > fed91000-fed91fff : dmar1
> > fed93000-fed93fff : dmar2
> > fee00000-fee00fff : Local APIC
> > fee00000-fee00fff : reserved
> > ff800000-ffffffff : reserved
> > 100000000-11bffffff : System RAM
> >
> > [8.5.] PCI information ('lspci -vvv' as root)
> > Sorry, cannot run lspci in the recovery shell. If this is critical, I can try to boot from USB and run lspci from there
> >
> > [8.6.] SCSI information (from /proc/scsi/scsi)
> > Attached devices:
> > Host: scsi0 Channel: 00 Id: 00 Lun: 00
> > Vendor: ATA Model: Samsung SSD 840 Rev: DXT0
> > Type: Direct-Access ANSI SCSI revision: 05
> > Host: scsi1 Channel: 00 Id: 00 Lun: 00
> > Vendor: MATSHITA Model: DVD+-RW UJ8A2 Rev: 1.02
> > Type: CD-ROM ANSI SCSI revision: 05
> > Host: scsi9 Channel: 00 Id: 00 Lun: 00
> > Vendor: HP Model: v100w Rev: 1.00
> > Type: Direct-Access ANSI SCSI revision: 02
> >
> > Note that the HP v100w was only used to copy over files for reporting; it was not present at boot time.
> >
> > See attached for full dmesg output up to the bug.
>
>
>
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2013-07-26 13:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1831795104.86305.1374673149679.JavaMail.root@mailhub017.itcs.purdue.edu>
2013-07-24 14:15 ` PROBLEM: After power loss, seg fault on boot tracing to fs/f2fs/recovery.c:270 Raymond M Bond
2013-07-25 11:10 ` Jaegeuk Kim
2013-07-25 15:43 ` Ray Bond
2013-07-26 13:25 ` Jaegeuk Kim
2013-07-26 13:40 ` Ray Bond [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1374846019.23354.18.camel@E6510ArchLinux \
--to=rmbond@purdue.edu \
--cc=jaegeuk.kim@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.