From: Andrew Morton <akpm@osdl.org>
To: marian.eichholz@freenet-ag.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.9-rc3 does not like diablo news reader daemon
Date: Thu, 7 Oct 2004 01:23:53 -0700 [thread overview]
Message-ID: <20041007012353.237c5e6f.akpm@osdl.org> (raw)
In-Reply-To: <20041007071930.GB27228@urmel.freenet-ag.de>
Marian Eichholz <marian.eichholz@freenet-ag.de> wrote:
>
> the kernel 2.6.9-rc3 tends to crash when executing our NNTP
> reader daemon (dreaderd from diablo).
>
> 2.6.3-rc1 runs on the sibling machine like a charm.
Impressive.
> [...]
> Oct 6 22:48:39 newsread5 kernel: c0132eb1
> Oct 6 22:48:39 newsread5 kernel: *pde = 00000000
> Oct 6 22:48:39 newsread5 kernel: Oops: 0002 [#1]
> Oct 6 22:48:39 newsread5 kernel: SMP
> Oct 6 22:48:39 newsread5 kernel: CPU: 0
> Oct 6 22:48:39 newsread5 kernel: EIP: 0060:[<c0132eb1>] Not tainted VLI
> Oct 6 22:48:39 newsread5 kernel: EFLAGS: 00010246 (2.6.9-rc3)
> Oct 6 22:48:39 newsread5 kernel: EIP is at generic_file_aio_write_nolock+0x1d1/0x500
> Oct 6 22:48:39 newsread5 kernel: eax: 00014c38 ebx: 00000000 ecx: 00000000 edx: 00000000
> Oct 6 22:48:39 newsread5 kernel: esi: de8fe000 edi: 00014c38 ebp: 00000000 esp: de8ffe38
> Oct 6 22:48:39 newsread5 kernel: ds: 007b es: 007b ss: 0068
> Oct 6 22:48:39 newsread5 kernel: Process dreaderd (pid: 166, threadinfo=de8fe000 task=de86d000)
> Oct 6 22:48:39 newsread5 kernel: Stack: 00014c38 00000040 00000000 de8ffe48 00000000 ca258200 de8ffee0 c02a8f05
> Oct 6 22:48:39 newsread5 kernel: de8ffee0 00000001 de8ffe8c ffffffff df37f3ec 00000000 00000000 df37f3ec
> Oct 6 22:48:39 newsread5 kernel: 00000048 df37f490 de961560 00000048 00014c38 00000000 de8ffeb4 de961560
> Oct 6 22:48:39 newsread5 kernel: Call Trace:
> Oct 6 22:48:39 newsread5 kernel: [<c02a8f05>] sock_aio_read+0xf5/0x110
> Oct 6 22:48:39 newsread5 kernel: [<c013328a>] generic_file_write_nolock+0xaa/0xd0
> Oct 6 22:48:39 newsread5 kernel: [<c0118460>] autoremove_wake_function+0x0/0x60
> Oct 6 22:48:39 newsread5 kernel: [<c0133406>] generic_file_write+0x56/0xd0
> Oct 6 22:48:39 newsread5 kernel: [<c01333b0>] generic_file_write+0x0/0xd0
> Oct 6 22:48:39 newsread5 kernel: [<c014f738>] vfs_write+0xb8/0x130
> Oct 6 22:48:39 newsread5 kernel: [<c014f881>] sys_write+0x51/0x80
> Oct 6 22:48:39 newsread5 kernel: [<c010422f>] syscall_call+0x7/0xb
It got a null-pointer deref right in the heart of the write(2) syscall.
Everybody is using that all the time. So I'd say that either there's
something unusual about your setup or your hardware is failing.
- Are the oopses always the same? Please send some more.
- What types of filesytem are in use?
- Are you using any unusual mount options?
- Are you using any uncommon hardware?
- Does the application do anything unusual such as O_DIRECT I/O?
- Are any other machines running the same application and kernel? If so,
are they failing? If not, are you able to use a different machine with
2.6.9-rc3? That'll help us work out whether it's a hardware or software
failure.
prev parent reply other threads:[~2004-10-07 8:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-07 7:19 2.6.9-rc3 does not like diablo news reader daemon Marian Eichholz
2004-10-07 8:03 ` Jeff Garzik
2004-10-07 8:23 ` Andrew Morton [this message]
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=20041007012353.237c5e6f.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marian.eichholz@freenet-ag.de \
/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