From: Stephen Crowley <stephenc@digitalpassage.com>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at fs.c:567
Date: Sat, 28 Oct 2000 18:43:42 -0500 [thread overview]
Message-ID: <20001028184342.A1525@intolerance.digitalpassage.com> (raw)
kernel 2.4.0-test10-pre6, but this has been here as long as I can
remember.
starting wine triggers the bug, C: points to /win2k which is an NTFS
filesystem.
The offending code..
/* It's fscking broken. */
static int ntfs_get_block(struct inode *inode, long block, struct buffer_head *bh, int create)
{
BUG();
return -1;
}
Heh. is there something else can be done there instead of just taking a crap
on itself? I can no longer read anything from /proc after this happens.
Oct 28 18:27:54 intolerance kernel: kernel BUG at fs.c:567!
Oct 28 18:27:54 intolerance kernel: invalid operand: 0000
Oct 28 18:27:54 intolerance kernel: CPU: 0
Oct 28 18:27:54 intolerance kernel: EIP: 0010:[ntfs_get_block+20/32]
Oct 28 18:27:54 intolerance kernel: EFLAGS: 00210282
Oct 28 18:27:54 intolerance kernel: eax: 00000018 ebx: cc95e2c0 ecx: c6bc2000 edx: cf974520
Oct 28 18:27:54 intolerance kernel: esi: 00000000 edi: 0000000b ebp: 00000800 esp: c6bc3dfc
Oct 28 18:27:54 intolerance kernel: ds: 0018 es: 0018 ss: 0018
Oct 28 18:27:54 intolerance kernel: Process wine (pid: 1502, stackpage=c6bc3000)
Oct 28 18:27:54 intolerance kernel: Stack: c0215e52 c0216278 00000237 c012f904 c70f7340 00000000 cc95e2c0 00000000
Oct 28 18:27:54 intolerance kernel: 00000000 c11c6170 00000000 c70f73dc 00000000 00000000 00000000 cc95e2c0
Oct 28 18:27:54 intolerance kernel: 000002a4 c70f7340 00000000 c0122263 c11c6170 c11c6170 c1480eb4 00000000
Oct 28 18:27:54 intolerance kernel: Call Trace: [tvecs+44350/74220] [tvecs+45412/74220] [block_read_full_page+236/488] [add_to_p age_cache_unique+267/280] [ntfs_readpage+15/20] [ntfs_get_block+0/32] [read_cluster_nonblocking+258/324]
Oct 28 18:27:54 intolerance kernel: [filemap_nopage+304/776] [filemap_nopage+0/776] [do_no_page+80/176] [handle_mm_fault+ 231/340] [do_page_fault+315/992] [do_page_fault+0/992] [old_mmap+192/240] [old_mmap+224/240]
Oct 28 18:27:54 intolerance kernel: [error_code+52/60]
Oct 28 18:27:54 intolerance kernel: Code: 0f 0b 83 c4 0c b8 ff ff ff ff c3 90 8b 44 24 08 68 90 fb 14
Please CC: responses, I'm not subscribed to the list.
--
Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-10-28 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-28 23:43 Stephen Crowley [this message]
2000-10-29 10:27 ` kernel BUG at fs.c:567 David Weinehall
2000-10-29 17:25 ` Stephen Crowley
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=20001028184342.A1525@intolerance.digitalpassage.com \
--to=stephenc@digitalpassage.com \
--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