From: Andrew Morton <andrewm@uow.edu.au>
To: Carlos Laviola <claviola@ajato.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Weird bug in kernel (invalid operand?)
Date: Tue, 22 May 2001 22:52:47 +1000 [thread overview]
Message-ID: <3B0A611F.B0A554AA@uow.edu.au> (raw)
In-Reply-To: <20010521171108.2fe854ab.claviola@ajato.com.br>
Carlos Laviola wrote:
>
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c48fb709>]
> EFLAGS: 00010282
> eax: 00000019 ebx: 00000000 ecx: c1272000 edx: c3f7bc20
> esi: 00206c60 edi: c3ca5240 ebp: c0695aa0 esp: c1273e68
> ds: 0018 es: 0018 ss: 0018
> Process snarf (pid: 324, stackpage=c1273000)
> Stack: c48fe965 c48fea27 00000045 000001f0 00000200 00040d8c c1273ec0 c012cf56
> c3ca5240 00206c60 c0695aa0 00000001 000001f0 c1273f64 00040d8c 000002e5
> c0605000 c0695aa0 00000200 00206c60 00000000 c0695aa0 0000004b 0000004b
> Call Trace: [<c48fe965>] [<c48fea27>] [<c012cf56>] [<c012d553>] [<c48fb6ac>] [<c48fcf1c>] [<c48fb6ac>]
> [<c012179a>] [<c48fb7d2>] [<c48fb7b0>] [<c012ac5a>] [<c0106a63>]
>
> Code: 0f 0b 83 c4 0c b8 fb ff ff ff eb 6d 8b 87 8c 00 00 00 0f b7
> Segmentation fault
>
> This seems to be a bug in the kernel, maybe because the file is too big,
> and VFAT partitions don't like that.
It used to be that fatfs would hit the second BUG() in fat_get_block()
when a file reaches two gig. But I can't make that happen in testing,
because the s_maxbytes stuff restricts it to 2gig-1. What you *should*
have seen was `wget' locking up because of a different bug :)
Are you sure you got this with 2.4.4? If so, please run the
output through
ksymoops -m System.map < oops-text
next prev parent reply other threads:[~2001-05-22 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 20:11 Carlos Laviola
2001-05-22 12:52 ` Andrew Morton [this message]
2001-05-23 2:39 ` Carlos Laviola
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=3B0A611F.B0A554AA@uow.edu.au \
--to=andrewm@uow.edu.au \
--cc=claviola@ajato.com.br \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®