From: "J. Bruce Fields" <bfields@fieldses.org>
To: Allard Hoeve <allard-DW70C6hi67U@public.gmane.org>
Cc: linux-nfs@vger.kernel.org, "Nilssen,
Rune" <rune.nilssen-FJFKJQU35qU@public.gmane.org>,
Gertjan Oude Lohuis <gertjan-DW70C6hi67U@public.gmane.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: Kernel 2.6.23.17 crash (Was: Kernel (2.6.24) crash on nfsd (BUG: soft lockup))
Date: Sat, 1 Mar 2008 11:39:44 -0500 [thread overview]
Message-ID: <20080301163944.GC19927@fieldses.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0802281153040.31013-FHjt3+7qfYHBZBx2VKNGNcSTQT6m/s+e@public.gmane.org>
On Thu, Feb 28, 2008 at 11:56:51AM +0100, Allard Hoeve wrote:
> After trying 2.6.23.17, the same happened. The stacktrace is a bit
> different, but they are comparable.
>
> Is this an NFS problem in the first place? Where could we go for help
> with this problem?
Thanks for the reports!
So, the summary: several people are reporting soft lockup warnings with
_generic_file_splice_read as the latest or next-to-latest function on
the stack. Sounds like 2.6.18 is good, various kernels around 2.6.23
and 2.6.24 are reported bad. Is it possible this was a regression
introduced by the splice changes?
--b.
>
> Regards,
>
> Allard Hoeve
>
>
>
> Pid: 2643, comm: nfsd
> EIP: 0060:[<c0179a3a>] CPU: 3
> EIP is at __generic_file_splice_read+0x12c/0x418
> EFLAGS: 00000206 Not tainted (2.6.23.17-fwsh-byte #3)
> EAX: f6e9dddc EBX: 00001000 ECX: 00000001 EDX: 00000000
> ESI: 00000000 EDI: f6e9dcd0 EBP: 00000095 DS: 007b ES: 007b FS: 00d8
> CR0: 8005003b CR2: b7e72cc0 CR3: 00622000 CR4: 000006f0
> DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> DR6: ffff0ff0 DR7: 00000400
> [<c0113cbb>] __check_preempt_curr_fair+0x4b/0x7d
> [<c0113dcb>] entity_tick+0x47/0x54
> [<c013006b>] getnstimeofday+0x37/0x111
> [<c0132fb6>] clockevents_program_event+0xac/0xcc
> [<c0122996>] run_timer_softirq+0x30/0x184
> [<c012f36f>] hrtimer_interrupt+0x132/0x1c4
> [<c011f0e0>] __do_softirq+0xba/0xcf
> [<c010da6a>] smp_apic_timer_interrupt+0x2c/0x35
> [<c01032bc>] apic_timer_interrupt+0x28/0x30
> [<c0179da7>] generic_file_splice_read+0x81/0xd5
> [<c017a6b0>] do_splice_to+0x75/0x97
> [<c017a771>] splice_direct_to_actor+0x9f/0x166
> [<f8f2a494>] nfsd_acceptable+0x0/0xd1 [nfsd]
> [<f8f2c247>] nfsd_direct_splice_actor+0x0/0xa [nfsd]
> [<f8f2c5ea>] nfsd_vfs_read+0x399/0x3bd [nfsd]
> [<c015d57f>] dentry_open+0x34/0x64
> [<f8f2ca1d>] nfsd_read+0xee/0xfb [nfsd]
> [<f8f332ab>] nfsd3_proc_read+0xfe/0x186 [nfsd]
> [<f8f34cd9>] nfs3svc_decode_readargs+0x0/0xeb [nfsd]
> [<f8f28847>] nfsd_dispatch+0xc5/0x1ca [nfsd]
> [<c043ab82>] svcauth_unix_set_client+0x116/0x165
> [<c0436b96>] svc_process+0x4fb/0x6d4
> [<c01164ad>] default_wake_function+0x0/0xc
> [<f8f2863d>] nfsd+0x16a/0x282 [nfsd]
> [<f8f284d3>] nfsd+0x0/0x282 [nfsd]
> [<c010343f>] kernel_thread_helper+0x7/0x10
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-01 16:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 15:48 Kernel (2.6.24) crash on nfsd (BUG: soft lockup) Gertjan Oude Lohuis
[not found] ` <47C434D2.80601-DW70C6hi67U@public.gmane.org>
2008-02-27 6:46 ` Gertjan Oude Lohuis
[not found] ` <47C50754.5030107-DW70C6hi67U@public.gmane.org>
2008-02-27 7:01 ` Gertjan Oude Lohuis
[not found] ` <47C50ABB.8050700-DW70C6hi67U@public.gmane.org>
2008-02-28 10:56 ` Kernel 2.6.23.17 crash (Was: Kernel (2.6.24) crash on nfsd (BUG: soft lockup)) Allard Hoeve
[not found] ` <Pine.LNX.4.62.0802281153040.31013-FHjt3+7qfYHBZBx2VKNGNcSTQT6m/s+e@public.gmane.org>
2008-03-01 16:39 ` J. Bruce Fields [this message]
2008-03-01 17:03 ` Jens Axboe
2008-03-05 10:25 ` Gertjan Oude Lohuis
2008-02-28 11:08 ` Kernel (2.6.24) crash on nfsd (BUG: soft lockup) Gertjan Oude Lohuis
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=20080301163944.GC19927@fieldses.org \
--to=bfields@fieldses.org \
--cc=allard-DW70C6hi67U@public.gmane.org \
--cc=gertjan-DW70C6hi67U@public.gmane.org \
--cc=jens.axboe@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=rune.nilssen-FJFKJQU35qU@public.gmane.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