From: Per Pascal Grube <pgrube@informatik.uni-wuerzburg.de>
To: linux-kernel@vger.kernel.org
Subject: [BUG] Probably ext3
Date: Sun, 27 Apr 2003 11:17:47 +0200 [thread overview]
Message-ID: <3EABA03B.9070309@informatik.uni-wuerzburg.de> (raw)
Hello
My system could not access the filesystem anymore for writting after the
following message appeared in the syslog. Unmount also didn't work anymore.
Apr 27 01:09:01 cybercom kernel: kernel BUG at buffer.c:509!
Apr 27 01:09:01 cybercom kernel: invalid operand: 0000
Apr 27 01:09:01 cybercom kernel: CPU: 0
Apr 27 01:09:01 cybercom kernel: EIP:
0010:[__insert_into_lru_list+30/96]
Tainted: P
Apr 27 01:09:01 cybercom kernel: EFLAGS: 00010282
Apr 27 01:09:01 cybercom kernel: eax: f4392d40 ebx: 00000002 ecx:
da6076c0
edx: c03cefac
Apr 27 01:09:01 cybercom kernel: esi: da6076c0 edi: 00000001 ebp:
da6076c0
esp: d1ad5e7c
Apr 27 01:09:01 cybercom kernel: ds: 0018 es: 0018 ss: 0018
Apr 27 01:09:01 cybercom kernel: Process bzip2 (pid: 687,
stackpage=d1ad5000)
Apr 27 01:09:01 cybercom kernel: Stack: 00000002 c013ca58 da6076c0
00000002 da60
76c0 00001000 c013d582 da6076c0
Apr 27 01:09:01 cybercom kernel: 00001000 00000000 09758000
00000000 c20e
4580 ca22c740 c013dd4f ca22c740
Apr 27 01:09:01 cybercom kernel: c20e4580 00000000 00001000
c20e4580 ca22
c740 c20e4580 00001000 c0163d3c
Apr 27 01:09:01 cybercom kernel: Call Trace: [__refile_buffer+88/112]
[__bloc
k_commit_write+178/208] [generic_commit_write+63/160]
[ext3_commit_write+348/672
] [journal_dirty_sync_data+0/160]
Apr 27 01:09:01 cybercom kernel: [generic_file_write+1127/1952]
[ext3_file_wri
te+57/208] [sys_write+163/304] [system_call+51/56]
Apr 27 01:09:01 cybercom kernel:
Apr 27 01:09:01 cybercom kernel: Code: 0f 0b fd 01 57 f8 2f c0 8b 02 85
c0 75 07
89 0a 89 49 24 8b
reply other threads:[~2003-04-27 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EABA03B.9070309@informatik.uni-wuerzburg.de \
--to=pgrube@informatik.uni-wuerzburg.de \
--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;
as well as URLs for NNTP newsgroup(s).