From: "Tony.Ho" <linux@idccenter.cn>
To: nathans@sgi.com
Cc: jesper.juhl@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Sun, 06 Aug 2006 12:05:43 +0800 [thread overview]
Message-ID: <44D56A97.2070603@idccenter.cn> (raw)
In-Reply-To: <44D55CE8.3090202@idccenter.cn>
I'm sorry about prev mail. I test on a wrong kernel.
The panic is not appear again, but random delete performance looks very bad.
Version 1.03 ------Sequential Output------ --Sequential Input-
--Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP
/sec %CP
test 4G 50317 99 232444 54 109507 25 52287 98 329821 29
1169 2
------Sequential Create------ --------Random
Create--------
-Create-- --Read--- -Delete-- -Create-- --Read---
-Delete--
files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP
/sec %CP
16 104 1 +++++ +++ 87 1 103 1 +++++ +++
100 1
test,4G,50317,99,232444,54,109507,25,52287,98,329821,29,1169.4,2,16,104,1,+++++,+++,87,1,103,1,+++++,+++,100,1
Tony.Ho wrote:
> I'vs tested this patch, but the XFS panic is also reproducible, error
> message is same as before.
>
>
> Nathan Scott wrote:
>> On Fri, Aug 04, 2006 at 10:22:21AM +0200, Jesper Juhl wrote:
>>
>>> I just hit a BUG that looks XFS related.
>>>
>>> The machine is running 2.6.18-rc3-git3
>>>
>>> (more info below the BUG messages)
>>>
>>>
>>
>> Thanks for reporting, Jesper - is it reproducible? Could you try this
>> patch for me? We had a couple of other reports of this, but the earlier
>> reporters have vanished ... could you let me know if this helps?
>>
>> cheers.
>>
>>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2006-08-06 4:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 8:22 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078 Jesper Juhl
2006-08-04 10:05 ` Nathan Scott
2006-08-04 10:43 ` Jesper Juhl
2006-08-06 3:07 ` Tony.Ho
2006-08-06 4:05 ` Tony.Ho [this message]
2006-08-07 4:34 ` Nathan Scott
[not found] ` <3aa654a40608072039r2b5c5a19hbd3e68e4fee40869@mail.gmail.com>
2006-08-08 3:44 ` Nathan Scott
[not found] ` <9a8748490608080137k596a6290r3567096668449a64@mail.gmail.com>
2006-08-08 8:54 ` Nathan Scott
[not found] ` <9a8748490608100431m244207b1v9c9c5087233fcf3a@mail.gmail.com>
2006-08-10 12:25 ` Jesper Juhl
2006-08-10 22:35 ` Nathan Scott
[not found] ` <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
2006-08-10 22:52 ` Jesper Juhl
2006-08-11 8:33 ` Jesper Juhl
2006-08-11 10:25 ` Jesper Juhl
2006-08-14 2:00 ` Nathan Scott
2006-08-14 7:49 ` Jesper Juhl
2006-08-15 9:03 ` Nathan Scott
2006-08-15 11:42 ` Jesper Juhl
2006-08-16 1:26 ` Nathan Scott
2006-08-17 21:23 ` Jesper Juhl
2006-08-15 14:37 ` Chris Wedgwood
2006-08-15 14:47 ` Jan Engelhardt
2006-08-16 12:38 ` Paul Slootman
2006-08-16 22:47 ` Nathan Scott
2006-08-17 9:01 ` Paul Slootman
2006-08-23 8:42 ` Paul Slootman
2006-08-24 6:55 ` Nathan Scott
2006-08-24 9:07 ` Paul Slootman
2006-08-10 23:01 ` Jesper Juhl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D56A97.2070603@idccenter.cn \
--to=linux@idccenter.cn \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.