From: Greg KH <greg@kroah.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.0-test9-bk12 oops in file_ra_state_init
Date: Mon, 10 Nov 2003 13:44:22 -0800 [thread overview]
Message-ID: <20031110214422.GA1910@kroah.com> (raw)
Ok, this laptop doesn't seem to like to stay up on a 2.6 kernel for more
than a few days. Usually it locks up overnight and I can't catch any
oopses, but this morning I caught the following:
Unable to handle kernel paging request at virtual address 050d0000
printing eip:
c013ab39
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<c013ab39>] Not tainted
EFLAGS: 00010246
EIP is at file_ra_state_init+0x19/0x20
eax: 050d0000 ebx: ccac0d20 ecx: 00000000 edx: ccac0d6c
esi: d5942c04 edi: ccac0d90 ebp: ffffffe9 esp: cf22bf30
ds: 007b es: 007b ss: 0068
Process ssh (pid: 7905, threadinfo=cf22a000 task=c1a57350)
Stack: d6fd4260 c014cb42 ccac0d6c d1942c98 00000003 00001000 40032000 00000000
00000000 00000003 d09d9000 cf22a000 c014cacd d5b424e0 d6fd4260 00000000
d5b424e0 d6fd4260 d193a460 00001000 fffffff4 00000101 00000001 00000001
Call Trace:
[<c014cb42>] dentry_open+0x62/0x1a0
[<c014cacd>] filp_open+0x4d/0x60
[<c014ce55>] sys_open+0x35/0x70
[<c0108fb3>] syscall_call+0x7/0xb
Which then spireled off into lots of other oopses, all in the same file
at the same location. Then these fun messages:
attempt to access beyond end of device
hda6: rw=0, want=2195953118, limit=20482812
Buffer I/O error on device hda6, logical block 3245460206
attempt to access beyond end of device
hda6: rw=0, want=2900596198, limit=20482812
Buffer I/O error on device hda6, logical block 3597781746
attempt to access beyond end of device
hda6: rw=0, want=2867041774, limit=20482812
Buffer I/O error on device hda6, logical block 3581004534
and then two more oopses in the same location. hda6 is my /home drive.
Anyone have any ideas?
thanks,
greg k-h
reply other threads:[~2003-11-10 21:45 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=20031110214422.GA1910@kroah.com \
--to=greg@kroah.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