Description of problem: System crashes with kernel bug at fs/ext4/inode.c:2188 while trying to report bug #699153 using ABRT. Version-Release number of selected component (if applicable): Kernel version shipped with F15 beta x86_64 live image. How reproducible: Always. Steps to Reproduce: 1.try to run keyboard configuration 2.app crashes (bug #699153) 3.try to report the problem using ABRT Actual results: Somewhere after debug info package 72 is downloaded system drops out of graphical mode and shows a kernel stack trace. Expected results: Report the keyboard configuration problem using ABRT, system keeps running. Additional info: This is a x86_64 live image running from a 2G FAT32 partition on a 16G USB stick. I don't have the whole stack trace, but it starts with kernel BUG at fs/ext4/inode.c:2188 invalid opcode : 0000 [#1] SMP last sys file: /sys/devices/system/cpu1/cache/index2/shared_cpu_map the last stackreace entry is: mpage_da_map_and_submit+0x1fa/0x2e0
fs/ext4/inode.c:2188:ext4_da_block_invalidatepages(): for (i = 0; i < nr_pages; i++) { struct page *page = pvec.pages[i]; if (page->index > end) break; ===> BUG_ON(!PageLocked(page)); BUG_ON(PageWriteback(page)); block_invalidatepage(page, 0); ClearPageUptodate(page); unlock_page(page); } > the last stackreace entry is: > > mpage_da_map_and_submit+0x1fa/0x2e0 Maybe the multipage write code is still buggy?
(In reply to comment #1) > Maybe the multipage write code is still buggy? Good possibility, new bugs are still being found. we'll see how it goes, I guess, maybe disabling for a while longer would be in order.
How do we even tell if the multipage write code is enabled? I don't see any defaults in ext4.
It's not on by default in 2.6.38.3... sorry, not sure yet what's going on here.
Andre, have you been able to reproduce this at all ?
(In reply to comment #5) > Andre, have you been able to reproduce this at all ? Hi Dave, sorry, forgot to follow up on this. Been using F16 for a while now, and even reported a couple of bugs already on it using ABRT, so it could have been a problem with F15 beta only. Maybe it's not worth chasing this anymore. Thks for the interest anyway. If you'd like me to try to report something with ABRT on F17 alpha/beta to see if it's still there, just let me know.