Bug 93491
| Summary: | Kernel crashes every 10 minutes. Computer stalls | ||
|---|---|---|---|
| Product: | File System | Reporter: | Ionut Radu (ionut.radu) |
| Component: | ext4 | Assignee: | fs_ext4 (fs_ext4) |
| Status: | CLOSED OBSOLETE | ||
| Severity: | blocking | CC: | cmaiolino, DARWINZOU110, sandeen, szg00000 |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 3.18.7-200.fc21.x86_64 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
abrt message
dmesg after reboot |
||
in static void ext4_mb_use_inode_pa(), BUG_ON(start < pa->pa_pstart); BUG_ON(end > pa->pa_pstart + EXT4_C2B(sbi, pa->pa_len)); BUG_ON(pa->pa_free < len); <<<<---- here It'd be good to have full dmesg etc, this is a pretty sparse bug report. Did a fedora bug get filed from abrt? It might be worth booting a rescue environment and capturing an e2image -r or e2iamge -q of the filesystem, to see if this is caused by on-disk corruption somehow. Created attachment 167571 [details]
dmesg after reboot
I've attached dmesg after reboot.
A fedora bug was not filled by the abrt. Computer stalled and after reboot abrt
tells there is not enough data to report a bug.
After computer stall and forced turn off, filesystem got corrupted and was fixed via emergency disk with fsck.
dmesg after reboot won't be helpful, I'm afraid. If the fs was corrupt and fixed, but output not saved, and no further information is available from the crash, this will be very hard to resolve. Hi Eric, I see there are some oops dumps from abrt. Can you please take a look ? https://www.dropbox.com/sh/dq0ocnrgocsuuzk/AABpo4_8PJjBFI_X0WBekI7Fa?dl=0 That's a lot to look through; the first dmesg I grabbed had no oops in it, and dropbox is a little tedious to navigate. If there's an interesting one, can you attach it here? Hi Eric, I don't know what you are looking for, so I can't tell if a dmesg is interesting or not. Can't you temporary copy all of them to your disk if you find dropbox tedious to navigate ? sure, let me do that for you.... the only files which contain "kernel BUG" are "backtrace" and "reason" files, and they have no other information: $ cat oops-2015-02-19-09:46:07-817-0/reason kernel BUG at fs/ext4/mballoc.c:3272! so there's still not much to go on. I don't know why abrt didn't capture more. Probably because the abrt is collecting data after reboot if computer stalls. Can you collect data before the reboot then? sysrq or serial console maybe? No, I'm sorry. That's all I can provide. Issue was fixed. |
Created attachment 167541 [details] abrt message With the latest kernel, there are crashes every 10 minutes and computer stalls. After reboot ABRT displays : kernel BUG at fs/ext4/mballoc.c:3272!