public inbox for ecos-bugs@sourceware.org help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org To: unassigned@bugs.ecos.sourceware.org Subject: [Bug 1001668] Fix: phy_read() function returns bad values if interrupt occurs Date: Sun, 09 Sep 2012 09:37:00 -0000 [thread overview] Message-ID: <20120909093712.A12242F78009@mail.ecoscentric.com> (raw) In-Reply-To: <bug-1001668-777@http.bugs.ecos.sourceware.org/> Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001668 Bernd Edlinger <bernd.edlinger@hotmail.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernd.edlinger@hotmail.de --- Comment #1 from Bernd Edlinger <bernd.edlinger@hotmail.de> 2012-09-09 10:37:09 BST --- Well, when I look at that code I wonder if this can really happen. The reason for this is: phy_read() and phy_write() are static functions which are only called from fec_eth_init(). And as far as I know the fec_eth_deliver should never be called within fec_eth_init(), even if Interrupts are enabled. The dsr function eth_drv_dsr() should only trigger the execution of fec_eth_deliver() in the ethernet handler thread, but threading is not enabled when fec_eth_init() is called. Right? Are you using FreeBSD or lwIP? Are you able to reproduce this in a debugger? -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
next prev parent reply other threads:[~2012-09-09 9:37 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-06 22:32 [Bug 1001668] New: " bugzilla-daemon 2012-09-09 9:37 ` bugzilla-daemon [this message] 2012-09-20 22:34 ` [Bug 1001668] " bugzilla-daemon
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=20120909093712.A12242F78009@mail.ecoscentric.com \ --to=bugzilla-daemon@bugs.ecos.sourceware.org \ --cc=unassigned@bugs.ecos.sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).