From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org, manfred@colorfullife.com
Subject: Re: OOPS in __copy_user_zeroing_intel
Date: Wed, 12 Sep 2007 17:54:27 +0200 [thread overview]
Message-ID: <6bffcb0e0709120854m69878efav8d6f3d638e82c890@mail.gmail.com> (raw)
In-Reply-To: <46E6B797.8050605@nortel.com>
Hi Chris,
On 11/09/2007, Chris Friesen <cfriesen@nortel.com> wrote:
>
> Hi all,
>
> We're running a modified 2.6.10 on a dual-Xeon system. We've had a
> number of instances where we've seen oopses in the pipe code. I've
> included the most recent one below. This bug left us with a hung
> process as the pipe code bailed out while pipe_writev() was holding a
> sema, and another process was blocked waiting for the sema.
>
> Is anyone aware of bugs that were fixed in the pipe code since 2.6.10?
Eh, this is a pretty ancient kernel.
You may want to use one of the long time support kernel 2.6.16.x or 2.6.20.x.
>
> Thanks,
>
> Chris
>
>
> Unable to handle kernel paging request at virtual address 450004a2
> printing eip:
> c028fb7a
> *pde = 2a716001
> Kcore timestamp : 1188871029.530900
> Kcore HighResolution timestamp : 2B7FA3FD52C48
> Oops: 0002 [#1]
> SMP
> Modules linked in: fuse tipc pmemfs bond2 bond1 bond0 fault
> ipmi_watchdog vmc vMCstub ipmibus ipmi_serial ipmi_devintf ipmi_msghandler
>
> CPU: 3
> EIP: 0060:[<c028fb7a>] Not tainted VLI
> EFLAGS: 00010206 (2.6.10-pne)
> EIP is at __copy_user_zeroing_intel+0x28/0xac
> eax: 20202020 ebx: 00000049 ecx: 00000049 edx: 74656e69
> esi: b7e2c000 edi: 450004a2 ebp: f04f9eac esp: f04f9ea4
> ds: 007b es: 007b ss: 0068
> Process grep (pid: 28955, threadinfo=f04f8000 task=f0420c70)
> Stack: b7e2c000 450004a2 f04f9ec8 c028fcd0 450004a2 b7e2c000 00000049
> 00000000
> 450004a2 f04f9ee8 c028fd67 450004a2 b7e2c000 00000049 f04f9f48
> 00000049
> babbb0bb f04f9f30 c01733c6 450004a2 b7e2c000 00000049 ea309ddc
> 8ecc000e
> 450004a2 babbb0bb f04f8000 00000049 00000001 00000049 00000000
> f72d83f0
> c01735f6 ea37b180 f04f9f94 f04f9f50 c0173629 ea37b180 f04f9f48
> 00000001
> f04f9f94 b7e2c000 00000049 f04f9f7c c0167af3 ea37b180 b7e2c000
> 00000049
> f04f9f94 00000003 0b000000 ea37b180 00000001 fffffff7 f04f9fbc
> c0167c4c
> ea37b180 b7e2c000 00000049 f04f9f94 00000000 00000000 00000000
> 00000107
> 00004900 00000000 b7e2c000 00000001 00000049 b7e2c000 f04f8000
> c0102554
> 00000001 b7e2c000 00000049 00000049 b7e2c000 bfffe4d8 00000004
> 0000007b
> 0000007b 00000004 ffffe410 00000073 00000246 bfffe4a4 0000007b
> Call Trace:
> [<c010340f>] show_stack+0x80/0x96
> [<c01035a2>] show_registers+0x15d/0x1d6
> [<c0103900>] die+0x106/0x194
> [<c0112602>] do_page_fault+0x594/0x8e9
> [<c01030bb>] error_code+0x2b/0x30
> [<c028fcd0>] __copy_from_user_ll+0x62/0x70
> [<c028fd67>] copy_from_user+0x3f/0x68
> [<c01733c6>] pipe_writev+0x107/0x337
> [<c0173629>] pipe_write+0x33/0x35
> [<c0167af3>] vfs_write+0xe0/0x11e
> [<c0167c4c>] sys_write+0x77/0xa4
> [<c0102554>] no_dpa_vsyscall_enter+0x8/0x1b
> Code: c8 5d c3 55 89 e5 83 ec 08 89 34 24 89 7c 24 04 8b 75 0c 8b 7d 08
> 8b 4d 10 8b 46 20 83 f9 43 76 04 8b 46 40 90 8b 46 00 8b 56 04 <89> 47
> 00 89 57 04 8b 46 08 8b 56 0c 89 47 08 89 57 0c 8b 46 10
>
> fuse tipc pmemfs bond2 bond1 bond0 fault ipmi_watchdog vmc vMCstub
> ipmibus ipmi_serial ipmi_devintf ipmi_msghandler
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
next prev parent reply other threads:[~2007-09-12 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 15:43 Chris Friesen
2007-09-12 15:54 ` Michal Piotrowski [this message]
2007-09-12 20:45 ` Chris Friesen
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=6bffcb0e0709120854m69878efav8d6f3d638e82c890@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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®