Bug 144766 - kernel panic at cache_alloc_refill
Summary: kernel panic at cache_alloc_refill
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel   
(Show other bugs)
Version: rawhide
Hardware: i686 Linux
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2005-01-11 13:42 UTC by Ralf Ertzinger
Modified: 2015-01-04 22:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-11 16:18:16 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ralf Ertzinger 2005-01-11 13:42:32 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041228 Firefox/1.0 Fedora/1.0-8

Description of problem:
I have experienced several system freezes during the last days, most
occur when the system is under interrupt load somehow. Today I managed
to grab a panic while using transcode capturing a live tv feed (bttv
driver) into a file on disk:

Unable to handle kernel paging request at virtual address 5c636467
 printing eip:
*pde = 00000000
Oops: 0002 [#1]
Modules linked in: md5 ipv6 lp autofs4 sunrpc dm_mod joydev ohci1394
ieee1394 uhci_hcd bt878 tuner bttv video_buf i2c_algo_bit v4l2_
common btcx_risc videodev parport_pc parport i2c_viapro i2c_core
snd_ens1371 snd_rawmidi snd_seq_device snd_ac97_codec snd_pcm_oss s
nd_mixer_oss snd_pcm snd_timer snd soundcore snd_page_alloc gameport
3c59x floppy sr_mod ext3 jbd aic7xxx sd_mod scsi_mod
CPU:    0
EIP:    0060:[<c0145ee5>]    Not tainted VLI
EFLAGS: 00010046   (2.6.10-1.1063_FC4) 
EIP is at cache_alloc_refill+0x18d/0x27f
eax: 5c636463   ebx: e7fed740   ecx: 00000000   edx: e7fed74c
esi: cc85f000   edi: 00000005   ebp: c15edef8   esp: c533dcc8
ds: 007b   es: 007b   ss: 0068
Process transcode (pid: 4305, threadinfo=c533d000 task=d2c49aa0)
Stack: e7fed74c 00000050 e7fed740 00000050 00000246 00000001 c01463ed
       00000000 00001000 c016389e 00000000 c0161458 c101dc00 c101dc00
       e3222e44 c101dc00 c0161d22 0000000c e3222e44 c01621d6 c70fb30c
Call Trace:
 [<c01463ed>] kmem_cache_alloc+0x55/0x6b
 [<c016389e>] alloc_buffer_head+0xd/0x22
 [<c0161458>] alloc_page_buffers+0x21/0x8b
 [<c0161d22>] create_empty_buffers+0x10/0x136
 [<c01621d6>] __block_prepare_write+0x91/0x3d2
 [<c01460ce>] cache_alloc_debugcheck_after+0xf7/0x125
 [<c01463fe>] kmem_cache_alloc+0x66/0x6b
 [<e8867652>] new_handle+0x15/0x37 [jbd]
 [<c0162b72>] block_prepare_write+0x16/0x22
 [<e887cdc7>] ext3_get_block+0x0/0x6c [ext3]
 [<e887d266>] ext3_prepare_write+0x56/0xf5 [ext3]
 [<e887cdc7>] ext3_get_block+0x0/0x6c [ext3]
 [<c013e769>] generic_file_buffered_write+0x185/0x465
 [<c011777c>] __wake_up+0x6e/0xca
 [<c0217f45>] n_tty_receive_buf+0x100d/0x1044
 [<c0217f4d>] n_tty_receive_buf+0x1015/0x1044
 [<c0217f45>] n_tty_receive_buf+0x100d/0x1044
 [<c013ed86>] __generic_file_aio_write_nolock+0x33d/0x36b
 [<c013eded>] generic_file_aio_write_nolock+0x39/0x7f
 [<c013efd5>] generic_file_aio_write+0x70/0xc2
 [<e887b0af>] ext3_file_write+0x19/0x8a [ext3]
 [<c015ebba>] do_sync_write+0x97/0xc9
 [<c0131b4a>] autoremove_wake_function+0x0/0x2d
 [<c0116c25>] recalc_task_prio+0x128/0x133
 [<c015eca2>] vfs_write+0xb6/0xe2
 [<c015ed6c>] sys_write+0x3c/0x62
 [<c010331f>] syscall_call+0x7/0xb
Code: 0f b7 46 14 ff 46 10 0f b7 0c 42 66 c7 04 42 fe ff 66 89 4e 14
8b 43 3c 39 46 10 72 a4 89 f2 89 d8 e8 e3 fd ff ff 8b 56 04 8b 
06 <89> 50 04 89 02 c7 46 04 00 02 20 00 66 83 7e 14 ff c7 06 00 01 
 <0>Kernel panic - not syncing: mm/slab.c:2196:
spin_lock(mm/slab.c:e7fed784) already locked by mm/slab.c/1976

I will try to get the same for the latest rawhide kernel.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Unknown. IO/Interrupt load seems to help.

Actual Results:  system freeze

Expected Results:  normal operation

Additional info:

Comment 1 Dave Jones 2005-01-11 16:18:16 UTC
fixed in subsequent update.

Note You need to log in before you can comment on or make changes to this bug.