Linux ATA/IDE development
 help / color / mirror / Atom feed
From: Adko Branil <adkobranil@yahoo.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: HDD problem, software bug, bios bug, or hardware ?
Date: Wed, 29 Aug 2012 10:31:43 -0700 (PDT)	[thread overview]
Message-ID: <1346261503.91611.YahooMailNeo@web124703.mail.ne1.yahoo.com> (raw)
In-Reply-To: <20120827215952.GA18719@liondog.tnic>

And one more thing i forgot - during kernel compilation i noticed this:

WARNING: modpost: Found 1 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'



And when i compiled with "make CONFIG_DEBUG_SECTION_MISMATCH=y", somewhere at the end was:


WARNING: drivers/scsi/fcoe/libfcoe.o(.init.text+0x1f): Section mismatch in reference from the function libfcoe_init() to the function .exit.text:fcoe_transport_exit()
The function __init libfcoe_init() references
a function __exit fcoe_transport_exit().
This is often seen when error handling in the init function
uses functionality in the exit path.
The fix is often to remove the __exit annotation of
fcoe_transport_exit() so it may be used outside an exit section.



It should not be related with the crash during "make modules_install", as the default slackware kernel 3.2.27 also crashes during it, but it may be important for any other things, i don't know.


Thanks !
Adko.


  parent reply	other threads:[~2012-08-29 17:31 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25 13:36 HDD problem, software bug, bios bug, or hardware ? Adko Branil
2012-08-25 17:46 ` Adko Branil
2012-08-26 13:01 ` Borislav Petkov
2012-08-27 17:01   ` Adko Branil
2012-08-27 17:21     ` Felix Miata
2012-08-27 21:59     ` Borislav Petkov
2012-08-29 17:02       ` Adko Branil
2012-08-29 17:31       ` Adko Branil [this message]
2012-08-30 10:12         ` Borislav Petkov
     [not found]       ` <1346259574.81504.YahooMailNeo@web124706.mail.ne1.yahoo.com>
2012-08-30  9:58         ` Borislav Petkov
2012-08-30 10:11           ` Borislav Petkov
2012-08-30 11:10           ` Adko Branil
2012-09-02 20:04             ` Mikael Pettersson
2012-09-03 21:46               ` Adko Branil
2012-09-07 11:32               ` Adko Branil
2012-09-08 16:30                 ` Mikael Pettersson
2012-09-08 17:22                   ` Adko Branil
2012-09-11 13:38                   ` Adko Branil
2012-09-10  9:15                 ` Borislav Petkov
2012-09-10  9:17               ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2012-08-25  1:31 Adko Branil
2012-08-25 11:33 ` Borislav Petkov
2012-08-27  7:50   ` Rafael J. Wysocki
2012-09-01 12:45   ` Dan Merillat
2012-09-02  7:24     ` Borislav Petkov
2012-09-03  0:38       ` Dan Merillat
2012-09-10 20:51         ` Borislav Petkov
2012-09-10 21:29           ` Dan Merillat
2012-09-10 21:59             ` Borislav Petkov
2012-09-15  1:34               ` Dan Merillat
2012-09-15 10:34                 ` Borislav Petkov
2012-08-25  0:54 Adko Branil
2012-08-25  2:58 ` Felix Miata

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=1346261503.91611.YahooMailNeo@web124703.mail.ne1.yahoo.com \
    --to=adkobranil@yahoo.com \
    --cc=bp@alien8.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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