libreport version: 2.0.10 cmdline: BOOT_IMAGE=/vmlinuz-3.6.10-2.fc16.x86_64 root=/dev/mapper/vg_luks-root_verne ro KEYTABLE=es LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 quiet rhgb nouveau.modeset=0 rd.driver.blacklist=nouveau fsck.mode=force thermal.nocrt=1 backtrace: :WARNING: at fs/ext4/page-io.c:233 ext4_flush_unwritten_io+0x6b/0x80() :Hardware name: V1S :Modules linked in: xts gf128mul dm_crypt firewire_ohci firewire_core sdhci_pci sdhci crc_itu_t mmc_core video :Pid: 613, comm: mount Not tainted 3.6.10-2.fc16.x86_64 #1 :Call Trace: : [<ffffffff8105c69f>] warn_slowpath_common+0x7f/0xc0 : [<ffffffff8105c6fa>] warn_slowpath_null+0x1a/0x20 : [<ffffffff8121534b>] ext4_flush_unwritten_io+0x6b/0x80 : [<ffffffff8123d67d>] ext4_ext_truncate+0x2d/0x1d0 : [<ffffffff8122ddb5>] ? ext4_msg+0x55/0x60 : [<ffffffff8120f4f5>] ext4_truncate+0x125/0x130 : [<ffffffff81233d9e>] ext4_fill_super+0x2b4e/0x2c60 : [<ffffffff81617ccd>] ? mutex_lock+0x1d/0x50 : [<ffffffff81190d0e>] mount_bdev+0x1be/0x200 : [<ffffffff81231250>] ? ext4_calculate_overhead+0x430/0x430 : [<ffffffff8121ff05>] ext4_mount+0x15/0x20 : [<ffffffff811919c3>] mount_fs+0x43/0x1b0 : [<ffffffff8114daa0>] ? __alloc_percpu+0x10/0x20 : [<ffffffff811ab412>] vfs_kern_mount+0x72/0x110 : [<ffffffff811abc04>] do_kern_mount+0x54/0x110 : [<ffffffff811ad5f4>] do_mount+0x1a4/0x8a0 : [<ffffffff81147f6b>] ? memdup_user+0x4b/0x90 : [<ffffffff8114800b>] ? strndup_user+0x5b/0x80 : [<ffffffff811add80>] sys_mount+0x90/0xe0 : [<ffffffff81622129>] system_call_fastpath+0x16/0x1b
Created attachment 667773 [details] File: smolt_data
Created attachment 667823 [details] Start of /var/log/messages until after the oops Attaching /var/log/messages from boot until a little after the oops (( Hmm, abrt didn't send the full report (?) )) More info Oops did occur during boot-time fsck (via fsck.mode=force), following a "critical temperature" emergency shutdown. Despite kernel/EC failing regularly on this hardware (mistaking about the temperature itself), I do not recall such an oops ever before. Nevertheless, system & fs went just fine, unbreakable :p
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.