From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26219 invoked by alias); 1 Mar 2006 14:41:41 -0000 Received: (qmail 26202 invoked by uid 48); 1 Mar 2006 14:41:35 -0000 Date: Wed, 01 Mar 2006 14:41:00 -0000 Message-ID: <20060301144135.26201.qmail@sourceware.org> From: "guanglei at cn dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20060223094047.2387.guanglei@cn.ibm.com> References: <20060223094047.2387.guanglei@cn.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug kprobes/2387] system crash on ppc64/2.6.15.4 X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2006-q1/txt/msg00663.txt.bz2 ------- Additional Comments From guanglei at cn dot ibm dot com 2006-03-01 14:41 ------- I tried the 2.6.15.1-2.6.15.4 and 2.6.16-rc5 kernels, and all of them gave almost the same error like: Unable to handle kernel paging request for data at address ... And if I don't use -b option of systemtap, it seemed that it could run for a long time without kernel panic. And I also noticed that the kernel reported the I/O error even when I wasn't running systemtap and only did some simple writing operations: end_request: I/O error, dev sda, sector 17445 end_request: I/O error, dev sda, sector 17447 end_request: I/O error, dev sda, sector 17449 Aborting journal on device sda2. ext3_abort called. EXT3-fs error (device sda2): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only The same version of systemtap could run very well with 2.6.9-30EL, so it is a bug of the mainline kernel. -- http://sourceware.org/bugzilla/show_bug.cgi?id=2387 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.