From: Loiseleur Michel <mloiseleur@linagora.com>
To: linux-fsdevel@vger.kernel.org
Cc: Erik Mouw <erik@harddisk-recovery.com>
Subject: Re: Kernel Panic in ext3
Date: Fri, 04 Aug 2006 15:09:34 +0200 [thread overview]
Message-ID: <44D3470E.4040708@linagora.com> (raw)
In-Reply-To: <20060804114850.GK31998@harddisk-recovery.com>
Erik Mouw wrote:
> On Fri, Aug 04, 2006 at 12:36:52PM +0200, Loiseleur Michel wrote:
>
>> I work with a Red Hat AS kernel (2.6.9-11-smp) on a bi-proc AMD.
>>
>
> Ask Red Hat for support.
>
I am the support, or more correct, I try to be it :).
>> I had a kernel panic this night, you will find an extract of the
>> /var/log/messages in the attached file. The server is a backup one, and
>> it was during really big batch processing. you will see too that's SMART
>> seems wrong, the hdds are not so hot.
>>
>
> The temperature attribute doesn't have to tell the temperature in
> degrees Celcius (or Fahrenheit). There's sometimes a little calculation
> needed to get to something humans understand. hddtemp can do that for
> you.
>
thanks for the tip.
>
>> I have looked at the code and all seems to be in fs/ext3. It "seems"
>> that during an " ext3_ordered_writepage"
in fs/ext3/inode.c:1262,
>> the fs tries to walk along the
>> page (walk_page_buffers) but he can't because the "page" is null. that's
>> what the trace told me.
>>
>> My first idea is to correct it with something like this :
>> if (!page)
>> goto out_fail;
>>
>>
>> But I feel that's not the good way or maybe my thought is wrong. Is
>> there an ext3 maintener in the plane ? :)
>>
>
> There are, but...
>
>
>> Aug 4 01:08:09 ju kernel: Modules linked in: nfsd exportfs lockd sunrpc basp(U) md5 ipv6 i2c_dev i2c_core dm_mod button battery ac hw_random e1000 floppy ext3 jbd raid1 aic7xxx sd_mod scsi_mod
>> Aug 4 01:08:09 ju kernel: CPU: 0
>> Aug 4 01:08:09 ju kernel: EIP: 0060:[<f891bc87>] Tainted: P VLI
>>
>
> Your kernel is tainted by a proprietary module (I guess the "basp"
> module) so it's impossible to debug your problem. The only one able to
> debug your problem is the vendor of that proprietary module.
>
Oops, I didn't notice it. After some search, I saw it's a module for
load-balancing over network made by broadcom. basp stands for "Broadcom
Advanced Server Program". More info here :
http://support.3com.com/infodeli/tools/nic/linux/linuxasp996release.txt.
It don't seem to be related to my problem, but I will remove it, I don't
need it anyway.
Thanks for your advice,
--
Loiseleur Michel - TM2L (08000LINUX)
LINAGORA
27, rue de Berri
1er étage
75008 PARIS
Tél : 01 58 18 68 28
Fax : 01 58 18 68 29
"Si hoc legere scis nimium eruditionis habes"
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2006-08-04 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 10:36 Kernel Panic in ext3 Loiseleur Michel
2006-08-04 11:48 ` Erik Mouw
2006-08-04 13:09 ` Loiseleur Michel [this message]
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=44D3470E.4040708@linagora.com \
--to=mloiseleur@linagora.com \
--cc=erik@harddisk-recovery.com \
--cc=linux-fsdevel@vger.kernel.org \
/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.