Bug 232829

Summary: kernel crach under heavy disk load
Product: [Fedora] Fedora Reporter: Edmond <ymedhui>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: jonstanley
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: F8 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-01-08 03:01:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 427887    
Attachments:
Description Flags
kernel crash screen shot
none
part 1 of 2 crash screen
none
part 2 of 2 crash screen none

Description Edmond 2007-03-18 14:55:48 UTC 
Description of problem:
Kernel panic when running mencoder. I encountered a few similar cases, mostly
related to heavy disk access with DVD burning, MySQL. The server is also running
web server, mail server, bittorrent.

Version-Release number of selected component (if applicable):
kernel 2.6.20-1.2925.fc6

hw setup:
MSI RS480M2-IL m/b (see
http://www.msicomputer.com/product/p_spec.asp?model=RS480M2-IL&class=mb), AMD X2
3800+, 2 SATA HDD running hardward RAID from m/b, 2 ATA-100

This problem been happening since 2.6.19, 2.6.18 also have some disk related
problem (DVD burning failed/crash), but disk access is stabled

How reproducible:
quite often 6/10 times

Steps to Reproduce:
run mencoder to convert mpeg video (capture by WinTV250 TV capture card) to avi.
mencoder filename -ovc frameno -o frameno.avi -oac mp3lame -lameopts vbr=3
mencoder filename -ovc lavc -lavcopts vcodec=mpeg4:vpass=1 -oac copy -o filename.avi
mencoder filename -ovc lavc -lavcopts vcodec=mpeg4:vpass=2 -oac copy -o filename.avi

When burning DVD, I am using k3b, the hangs happened when verifying DVD burned.
  
Actual results:
kenerl panic, see attach screenshot

Expected results:
no error should encounter

Additional info:
I run smolt to collect my system setup, hw-uuid 72b5ecb7-7d79-4221-a16f-9e87491d3787
Comment 1 Edmond 2007-03-18 14:55:48 UTC 
Created attachment 150333 [details]
kernel crash screen shot
Comment 2 Chuck Ebbert 2007-03-18 22:30:38 UTC 
Please try to boot in 50-line mode and capture the entire oops.
Comment 3 Edmond 2007-03-18 22:39:44 UTC 
how to do that?

Rgds,
Comment 4 Dave Jones 2007-03-18 23:14:45 UTC 
add vga=1 to your boot command line.
Comment 5 Edmond 2007-03-18 23:41:46 UTC 
I added it to /etc/grub.conf but it didn't work for me... I think my LCD display
didn't support 50-line text mode
Comment 6 Chuck Ebbert 2007-03-19 15:26:19 UTC 
Everything supports 50-line boot mode. Sometimes the default font
causes problems, though. You can just rename the directory
/lib/kbd/consolefonts to /lib/kbd/consolefonts.save ... just be
sure to put it back after you are done. There will be annoying messages
about "not able to find default font" but they are harmless.

Or you could try "vga=792" for really small fonts...
Comment 7 Edmond 2007-03-19 15:29:27 UTC 
It's very unstable, I rollback default kernel back to 2.6.18 now. But I wil try
to reproduce it tonight.

Thanks for the response.

Rgds,
Comment 8 Edmond 2007-03-20 01:17:24 UTC 
Created attachment 150452 [details]
part 1 of 2 crash screen
Comment 9 Edmond 2007-03-20 01:19:17 UTC 
Created attachment 150453 [details]
part 2 of 2 crash screen
Comment 10 Edmond 2007-03-20 13:52:46 UTC 
BTW, should point out that even under 2.6.18. Sometime the kernel reboot (after
panic??) under heavy disk load... but 2.6.19/20 makes it worst that he panic
frezzed.....
Comment 11 Edmond 2007-03-28 13:40:37 UTC 
any news on this?

cheers,
Comment 12 Jon Stanley 2008-01-08 01:53:00 UTC 
(This is a mass-update to all current FC6 kernel bugs in NEW state)

Hello,

I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.

http://fedoraproject.org/wiki/KernelBugTriage

I am CC'ing myself to this bug, however this version of Fedora is no longer
maintained.

Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.

Thanks for using Fedora!
Comment 13 Edmond 2008-01-08 02:59:18 UTC 
Hi,

I have not reproduce it in FC8, so please close this.