All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Areca Support" <support@areca.com.tw>
To: gbakos@cfa.harvard.edu
Cc: Linux SMP List <linux-smp@vger.kernel.org>
Subject: Re: ARECA: oops when removing arcmsr module
Date: Wed, 27 Dec 2006 11:17:04 +0800	[thread overview]
Message-ID: <003301c72965$7d156ba0$2900a8c0@arecakevin> (raw)
In-Reply-To: Pine.SOL.4.58.0612261305170.13284@cfa0.cfa.harvard.edu

Dear Sir,

This is Kevin Wang from Areca Technology, Tech-Support Team.
regarding your problem, do you means the problem happen only if the
archttp64 running while you remove the arcmsr module ?


Best Regards,


Kevin Wang

Areca Technology Tech-support Division
Tel : 886-2-87974060 Ext. 223
Fax : 886-2-87975970
Http://www.areca.com.tw
Ftp://ftp.areca.com.tw

----- Original Message ----- 
From: "Gaspar Bakos" <gbakos@cfa.harvard.edu>
To: <support@areca.com.tw>
Cc: "Linux SMP List" <linux-smp@vger.kernel.org>
Sent: Wednesday, December 27, 2006 2:14 AM
Subject: ARECA: oops when removing arcmsr module


> Dear Support,
>
> The following bug is reported on a 2.6.17.6 (kernel.org) kernel, SMP
> system with 4 (dual core) AMD 64 Opteron CPUs.
> When I remove the arcmsr module, the following kernel oops comes up:
>
> -------------
>
> Unable to handle kernel paging request at ffffffff88064608 RIP:
> <ffffffff80249e54>{do_ioctl+36}
> PGD 203027 PUD 205027 PMD 2fbd7f067 PTE 0
> Oops: 0000 [1] SMP
> CPU 7
> Modules linked in: autofs4 sunrpc ip_conntrack_netbios_ns ipt_REJECT
xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables
dm_mirror dm_mod sg floppy tg3 i2c_nforce2 i2c_core sata_nv libata sd_mod
scsi_mod
> Pid: 2806, comm: areca_archttp64 Not tainted 2.6.17.6-GB4 #2
> RIP: 0010:[<ffffffff80249e54>] <ffffffff80249e54>{do_ioctl+36}
> RSP: 0018:ffff8102f6475ee8  EFLAGS: 00010286
> RAX: ffffffff880645c0 RBX: ffff8102fbb2b840 RCX: 00002ba15df7cb40
> RDX: 00002ba15df7cb40 RSI: 0000000090000804 RDI: ffff8102fbb2b840
> RBP: 00002ba15df7cb40 R08: ffff8102f6475dc8 R09: 0000000000000000
> R10: 0000000000000003 R11: 0000000000000246 R12: 0000000090000804
> R13: 0000000000000006 R14: 0000000090000804 R15: 00002ba15ce01fc0
> FS:  00002ba15ce01fc0(0000) GS:ffff810300227640(0000)
knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffffff88064608 CR3: 00000001f9bf4000 CR4: 00000000000006e0
> Process areca_archttp64 (pid: 2806, threadinfo ffff8102f6474000, task
ffff810200358780)
> Stack: ffff8102fbb2b840 00002ba15df7cb40 0000000000000006 ffffffff8023501b
>        0000000090000804 0000000000000000 0000000000000000 ffff8102fbb2b840
>        00002ba15df7cb40 0000000000000006
> Call Trace: <ffffffff8023501b>{vfs_ioctl+683}
<ffffffff8025683c>{sys_ioctl+108}
>        <ffffffff8026bc01>{tracesys+209}
>
> Code: 48 8b 48 48 48 85 c9 74 17 ff d1 48 c7 c1 ea ff ff ff 48 63
> RIP <ffffffff80249e54>{do_ioctl+36} RSP <ffff8102f6475ee8>
> CR2: ffffffff88064608
>  <3>BUG: sleeping function called from invalid context at
/usr/local/myper/usr/src/linux-2.6.17.6/include/linux/rwsem.h:43
> in_atomic():0, irqs_disabled():1
>
> Call Trace: <ffffffff802a164c>{blocking_notifier_call_chain+44}
>        <ffffffff80216a52>{do_exit+34}
<ffffffff80428eb5>{do_unblank_screen+133}
>        <ffffffff80273f75>{do_page_fault+2037}
<ffffffff803ae2ca>{avc_has_perm+90}
>        <ffffffff803ae2ca>{avc_has_perm+90}
<ffffffff8026c965>{error_exit+0}
>        <ffffffff80249e54>{do_ioctl+36} <ffffffff8023501b>{vfs_ioctl+683}
>        <ffffffff8025683c>{sys_ioctl+108} <ffffffff8026bc01>{tracesys+209}
> Unable to handle kernel paging request at ffffffff88064628 RIP:
> <ffffffff80226d09>{filp_close+57}
> PGD 203027 PUD 205027 PMD 2fbd7f067 PTE 0
> Oops: 0000 [2] SMP
> CPU 7
> Modules linked in: autofs4 sunrpc ip_conntrack_netbios_ns ipt_REJECT
xt_state ip_conntrack nfnetlink xt_tcpudp iptable_filter ip_tables x_tables
dm_mirror dm_mod sg floppy tg3 i2c_nforce2 i2c_core sata_nv libata sd_mod
scsi_mod
> Pid: 2804, comm: areca_archttp64 Not tainted 2.6.17.6-GB4 #2
> RIP: 0010:[<ffffffff80226d09>] <ffffffff80226d09>{filp_close+57}
> RSP: 0018:ffff8102f6471cd8  EFLAGS: 00010286
> RAX: ffffffff880645c0 RBX: ffff8102fbb2b840 RCX: 0000000000000020
> RDX: 0000000000000000 RSI: ffff8103fbd64700 RDI: ffff8102fbb2b840
> RBP: ffff8103fbcd4f40 R08: 0000000000000001 R09: 0000000000000001
> R10: 0000000000000001 R11: ffffffff802400c0 R12: ffff8103fbd64700
> R13: ffff8103fbd64700 R14: 0000000000000000 R15: 0000000000000000
> FS:  00000000006e6c00(0000) GS:ffff810300227640(0000)
knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: ffffffff88064628 CR3: 0000000000201000 CR4: 00000000000006e0
> Process areca_archttp64 (pid: 2804, threadinfo ffff8102f6470000, task
ffff810200398140)
> Stack: 00000000000007bf ffff8103fbcd4f40 0000000000000000 ffffffff8023f32e
>        0000000000000030 ffff8103fbd64700 ffff810200398140 ffff810200398778
>        0000000000000001 0000000000000009
> Call Trace: <ffffffff8023f32e>{put_files_struct+110}
>        <ffffffff80216ca9>{do_exit+633}
<ffffffff8029f07e>{__dequeue_signal+478}
>        <ffffffff80252cb8>{do_group_exit+200}
<ffffffff8022f6ad>{get_signal_to_deliver+1197}
>        <ffffffff8022deb1>{do_signal+129}
<ffffffff8029f29e>{signal_wake_up+30}
>        <ffffffff8023003c>{sys_recvfrom+332}
<ffffffff8029fdd6>{kill_proc_info+86}
>        <ffffffff802b877d>{audit_syscall_exit+109}
<ffffffff8026bca2>{int_signal+18}
>
> Code: 48 8b 40 68 48 85 c0 74 06 ff d0 89 c5 eb 02 31 ed 48 89 df
> RIP <ffffffff80226d09>{filp_close+57} RSP <ffff8102f6471cd8>
> CR2: ffffffff88064628
>  <1>Fixing recursive fault but reboot is needed!
>
> -------------
>
> I note that the poor user-space areca_archttp64 daemon was indeed
> running when the module was removed from below, but the kernel oops
> still should not happen.
>
> The kernel config is at :
>
> http://www.cfa.harvard.edu/~gbakos/cf7/config
>
> Best Regards,
> Gaspar


      reply	other threads:[~2006-12-27  3:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26 18:14 ARECA: oops when removing arcmsr module Gaspar Bakos
2006-12-27  3:17 ` Areca Support [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='003301c72965$7d156ba0$2900a8c0@arecakevin' \
    --to=support@areca.com.tw \
    --cc=gbakos@cfa.harvard.edu \
    --cc=linux-smp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.