From: Hendrik Visage <hvjunk@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
Ion Badulescu <ionut@badula.org>
Subject: Re: Starfire (Adaptec) kernel 2.6.13+ panics on AMD64 NFS server
Date: Fri, 30 Sep 2005 18:01:32 +0200 [thread overview]
Message-ID: <d93f04c70509300901s3836b8afw4792d16c589b4fc4@mail.gmail.com> (raw)
In-Reply-To: <20050929211649.69eaddee.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 281 bytes --]
On 9/30/05, Andrew Morton <akpm@osdl.org> wrote:
> The starfire changes in 2.6.12->2.6.13 look fairly innocuous. Need that
> trace, please.
See attached :)
Will do a check without PREEMPT as I've noticed that to be the first
line of "problem" :(
--
Hendrik Visage
[-- Attachment #2: crash2.minicom --]
[-- Type: application/octet-stream, Size: 4192 bytes --]
----------- [cut here ] --------- [please bite here ] ---------
Kernel BUG at net/core/dev.c:1099
invalid operand: 0000 [1] PREEMPT
CPU 0
Modules linked in: nvidia nfsd exportfs lockd sunrpc rfcomm l2cap hci_usb bluetooth starfire mii snd_ac97_bus soundcore snd_page_alloc forcedeth i2c_nforce2 dm_mirror dm_mod sbp2 ohci1394 ieee1394 ohci_hcd uhci_hcd usb_storage usbhid ehci_hcd usbcore
Pid: 11252, comm: nfsd Tainted: P 2.6.14-rc2 #3
RIP: 0010:[<ffffffff802cc7ed>] <ffffffff802cc7ed>{skb_checksum_help+157}
RSP: 0000:ffff81003a0bd998 EFLAGS: 00010246
RAX: ffff81003ff01624 RBX: ffff81003ca7f180 RCX: 00000000b7e42194
RDX: 00000000b7e42194 RSI: ffff81003ff01624 RDI: ffff81003b026080
RBP: ffff81003a0bd9b8 R08: 0000000000000000 R09: 0000000000000004
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff81003ca7f180 R15: ffff81003d462218
FS: 00002aaaaade6ae0(0000) GS:ffffffff804fe800(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aaaaaac2000 CR3: 000000003d5a2000 CR4: 00000000000006e0
Process nfsd (pid: 11252, threadinfo ffff81003a0bc000, task ffff81003e0ed0c0)
Stack: ffffffff804cd720 ffff81003d462000 ffff81003d4623e0 ffff81003ca7f180
ffff81003a0bda08 ffffffff88104944 ffff81003d462218 000000013a2a8600
ffff81003d462000 ffff81003d462000
Call Trace:<ffffffff88104944>{:starfire:start_tx+164} <ffffffff802db0fc>{qdisc_restart+268}
<ffffffff802ccad0>{dev_queue_xmit+288} <ffffffff802d29b0>{neigh_resolve_output+672}
<ffffffff802ebb27>{ip_finish_output+455} <ffffffff802ec5ff>{ip_fragment+863}
<ffffffff802eb960>{ip_finish_output+0} <ffffffff802eca6c>{ip_output+108}
<ffffffff8035a708>{_spin_unlock_bh+24} <ffffffff802ee1e7>{ip_push_pending_frames+919}
<ffffffff80307d7e>{udp_push_pending_frames+574} <ffffffff80308658>{udp_sendpage+280}
<ffffffff8031001f>{inet_sendpage+111} <ffffffff881411ea>{:sunrpc:svc_sendto+554}
<ffffffff8818b8f9>{:nfsd:encode_post_op_attr+553} <ffffffff88141893>{:sunrpc:svc_udp_sendto+35}
<ffffffff88142327>{:sunrpc:svc_send+247} <ffffffff88140854>{:sunrpc:svc_process+1108}
<ffffffff8817e43e>{:nfsd:nfsd+462} <ffffffff8012e529>{schedule_tail+73}
<ffffffff8010f61e>{child_rip+8} <ffffffff8817e270>{:nfsd:nfsd+0}
<ffffffff8010f616>{child_rip+0}
Code: 0f 0b 68 23 d9 39 80 c2 4b 04 8b 93 8c 00 00 00 8d 42 02 44
RIP <ffffffff802cc7ed>{skb_checksum_help+157} RSP <ffff81003a0bd998>
<3>Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
in_atomic():1, irqs_disabled():0
Call Trace:<ffffffff8012db7f>{__might_sleep+191} <ffffffff80133c3c>{profile_task_exit+44}
<ffffffff801350f5>{do_exit+37} <ffffffff8035a5c3>{_spin_unlock_irqrestore+19}
<ffffffff8035a5cd>{_spin_unlock_irqrestore+29} <ffffffff80110294>{die+84}
<ffffffff8035ac1e>{do_trap+334} <ffffffff8011058c>{do_invalid_op+172}
<ffffffff802cc7ed>{skb_checksum_help+157} <ffffffff8010f469>{error_exit+0}
<ffffffff802cc7ed>{skb_checksum_help+157} <ffffffff802cc7d5>{skb_checksum_help+133}
<ffffffff88104944>{:starfire:start_tx+164} <ffffffff802db0fc>{qdisc_restart+268}
<ffffffff802ccad0>{dev_queue_xmit+288} <ffffffff802d29b0>{neigh_resolve_output+672}
<ffffffff802ebb27>{ip_finish_output+455} <ffffffff802ec5ff>{ip_fragment+863}
<ffffffff802eb960>{ip_finish_output+0} <ffffffff802eca6c>{ip_output+108}
<ffffffff8035a708>{_spin_unlock_bh+24} <ffffffff802ee1e7>{ip_push_pending_frames+919}
<ffffffff80307d7e>{udp_push_pending_frames+574} <ffffffff80308658>{udp_sendpage+280}
<ffffffff8031001f>{inet_sendpage+111} <ffffffff881411ea>{:sunrpc:svc_sendto+554}
<ffffffff8818b8f9>{:nfsd:encode_post_op_attr+553} <ffffffff88141893>{:sunrpc:svc_udp_sendto+35}
<ffffffff88142327>{:sunrpc:svc_send+247} <ffffffff88140854>{:sunrpc:svc_process+1108}
<ffffffff8817e43e>{:nfsd:nfsd+462} <ffffffff8012e529>{schedule_tail+73}
<ffffffff8010f61e>{child_rip+8} <ffffffff8817e270>{:nfsd:nfsd+0}
<ffffffff8010f616>{child_rip+0}
Kernel panic - not syncing: Aiee, killing interrupt handler!
next prev parent reply other threads:[~2005-09-30 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 3:36 Hendrik Visage
2005-09-30 4:16 ` Andrew Morton
2005-09-30 8:14 ` Hendrik Visage
2005-09-30 16:46 ` Ion Badulescu
2005-09-30 16:01 ` Hendrik Visage [this message]
2005-09-30 17:40 ` Andrew Morton
2005-09-30 20:10 ` Hendrik Visage
2005-09-30 20:55 ` Ion Badulescu
2005-09-30 22:39 ` Herbert Xu
2005-10-01 19:21 ` Hendrik Visage
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=d93f04c70509300901s3836b8afw4792d16c589b4fc4@mail.gmail.com \
--to=hvjunk@gmail.com \
--cc=akpm@osdl.org \
--cc=ionut@badula.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@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
all inboxes | Powered by JetHome®