mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hendrik Visage <hvjunk@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
	ionut@badula.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Starfire (Adaptec) kernel 2.6.13+ panics on AMD64 NFS server
Date: Fri, 30 Sep 2005 22:10:59 +0200	[thread overview]
Message-ID: <d93f04c70509301310y4bde1189wbcaef40124af6766@mail.gmail.com> (raw)
In-Reply-To: <20050930104046.4685e975.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 727 bytes --]

On 9/30/05, Andrew Morton <akpm@osdl.org> wrote:
> > ----------- [cut here ] --------- [please bite here ] ---------
> > Kernel BUG at net/core/dev.c:1099
> > invalid operand: 0000 [1] PREEMPT
>
> yep, there's something wrong with the skb which starfire fed into
> skb_checksum_help().
>
<snip>
>
> And that's a post-2.6.12 driver change.  You can probably work around
> it by deleting the #define ZEROCOPY line.

:)
Anycase, here is a non-PREEMPT traceback. What makes this one
interesting, is that
in the preempt case, I had to push the NFS output to get the panic, but the
non-preempt case attached, sorta just happened, ie. when the clients
just checked on the server's status :(


--
Hendrik Visage

[-- Attachment #2: non-prempt --]
[-- Type: application/octet-stream, Size: 4110 bytes --]

Kernel BUG at net/core/dev.c:1099
invalid operand: 0000 [1] 
CPU 0 
Modules linked in: nfs 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: 11169, comm: nfsd Not tainted 2.6.14-rc2 #4
RIP: 0010:[<ffffffff802c803d>] <ffffffff802c803d>{skb_checksum_help+157}
RSP: 0018:ffff81003d3bda08  EFLAGS: 00010246
RAX: ffff81003ac51c24 RBX: ffff81003ac4cd80 RCX: 000000005459cd0b
RDX: 000000005459cd0b RSI: ffff81003ac51c24 RDI: ffff81003d272080
RBP: ffff81003d3bda28 R08: 0000000000000000 R09: 0000000000000006
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff81003ac4cd80 R15: ffff81003a31c218
FS:  00002aaaaade6ae0(0000) GS:ffffffff804f7800(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002aaaaabc1190 CR3: 000000003b22b000 CR4: 00000000000006e0
Process nfsd (pid: 11169, threadinfo ffff81003d3bc000, task ffff81003f7c5100)
Stack: ffff81003d3bda48 ffff81003a31c000 ffff81003a31c3e0 ffff81003ac4cd80 
       ffff81003d3bda78 ffffffff88104944 ffff8100b00000d0 0000000100000000 
       ffff81003a31c000 ffff81003a31c000 
Call Trace:<ffffffff88104944>{:starfire:start_tx+164} <ffffffff802d6583>{qdisc_restart+243}
       <ffffffff802c8325>{dev_queue_xmit+293} <ffffffff802e64c7>{ip_finish_output+455}
       <ffffffff802e6f9f>{ip_fragment+863} <ffffffff802e6300>{ip_finish_output+0}
       <ffffffff802e740c>{ip_output+108} <ffffffff8035404e>{_spin_unlock_bh+14}
       <ffffffff802e8b87>{ip_push_pending_frames+919} <ffffffff803024de>{udp_push_pending_frames+574}
       <ffffffff80302db8>{udp_sendpage+280} <ffffffff8030a39f>{inet_sendpage+111}
       <ffffffff881411ca>{:sunrpc:svc_sendto+554} <ffffffff8818b879>{:nfsd:encode_post_op_attr+553}
       <ffffffff88141873>{:sunrpc:svc_udp_sendto+35} <ffffffff88142307>{:sunrpc:svc_send+247}
       <ffffffff88140834>{:sunrpc:svc_process+1108} <ffffffff8817e3c0>{:nfsd:nfsd+448}
       <ffffffff8012dfa9>{schedule_tail+73} <ffffffff8010f50e>{child_rip+8}
       <ffffffff8817e200>{:nfsd:nfsd+0} <ffffffff8010f506>{child_rip+0}
       

Code: 0f 0b 68 0b 6f 39 80 c2 4b 04 8b 93 8c 00 00 00 8d 42 02 44 
RIP <ffffffff802c803d>{skb_checksum_help+157} RSP <ffff81003d3bda08>
 <3>Debug: sleeping function called from invalid context at include/linux/rwsem.h:43
in_atomic():1, irqs_disabled():0

Call Trace:<ffffffff8012d6af>{__might_sleep+191} <ffffffff801333dc>{profile_task_exit+44}
       <ffffffff80134895>{do_exit+37} <ffffffff80353ff3>{_spin_unlock_irqrestore+19}
       <ffffffff80110184>{die+84} <ffffffff8035431e>{do_trap+334}
       <ffffffff8011047c>{do_invalid_op+172} <ffffffff802c803d>{skb_checksum_help+157}
       <ffffffff802c27e5>{__alloc_skb+133} <ffffffff802c06dd>{sock_alloc_send_skb+109}
       <ffffffff802e179d>{__ip_route_output_key+1517} <ffffffff8010f359>{error_exit+0}
       <ffffffff802c803d>{skb_checksum_help+157} <ffffffff802c8025>{skb_checksum_help+133}
       <ffffffff88104944>{:starfire:start_tx+164} <ffffffff802d6583>{qdisc_restart+243}
       <ffffffff802c8325>{dev_queue_xmit+293} <ffffffff802e64c7>{ip_finish_output+455}
       <ffffffff802e6f9f>{ip_fragment+863} <ffffffff802e6300>{ip_finish_output+0}
       <ffffffff802e740c>{ip_output+108} <ffffffff8035404e>{_spin_unlock_bh+14}
       <ffffffff802e8b87>{ip_push_pending_frames+919} <ffffffff803024de>{udp_push_pending_frames+574}
       <ffffffff80302db8>{udp_sendpage+280} <ffffffff8030a39f>{inet_sendpage+111}
       <ffffffff881411ca>{:sunrpc:svc_sendto+554} <ffffffff8818b879>{:nfsd:encode_post_op_attr+553}
       <ffffffff88141873>{:sunrpc:svc_udp_sendto+35} <ffffffff88142307>{:sunrpc:svc_send+247}
       <ffffffff88140834>{:sunrpc:svc_process+1108} <ffffffff8817e3c0>{:nfsd:nfsd+448}
       <ffffffff8012dfa9>{schedule_tail+73} <ffffffff8010f50e>{child_rip+8}
       <ffffffff8817e200>{:nfsd:nfsd+0} <ffffffff8010f506>{child_rip+0}
       
Kernel panic - not syncing: Aiee, killing interrupt handler!
 

  reply	other threads:[~2005-09-30 20:11 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
2005-09-30 17:40     ` Andrew Morton
2005-09-30 20:10       ` Hendrik Visage [this message]
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=d93f04c70509301310y4bde1189wbcaef40124af6766@mail.gmail.com \
    --to=hvjunk@gmail.com \
    --cc=akpm@osdl.org \
    --cc=ionut@badula.org \
    --cc=jgarzik@pobox.com \
    --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®