From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 10374] sym53c8xx: weird behavior with udev
Date: Tue, 1 Apr 2008 12:05:26 -0700 (PDT) [thread overview]
Message-ID: <20080401190526.AE96E11D108@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-10374-11613@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=10374
------- Comment #5 from seraph@xs4all.nl 2008-04-01 12:05 -------
Hello all,
I did a bit more testing, and I think this may be related to the order in which
modules are loaded.
If I let udev load sungem, and load sym53c8xx manually, everything works.
If I let udev load sym53c8xx, and load sungem manually, I get the
non-functional network.
If I let udev load both modules, I also get the non-functional network. While
udev loads sungem first and sym53c8xx later, I don't suppose it waits for one
module to 'settle' before loading the next. :-)
So to sum it up, the bug is triggered if sym53c8xx is loaded before sungem is.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-04-01 19:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10374-11613@http.bugzilla.kernel.org/>
2008-04-01 8:12 ` [Bug 10374] sym53c8xx: weird behavior with udev bugme-daemon
2008-04-01 8:15 ` bugme-daemon
2008-04-01 8:58 ` bugme-daemon
2008-04-01 14:12 ` bugme-daemon
2008-04-01 14:48 ` bugme-daemon
2008-04-01 19:05 ` bugme-daemon [this message]
2008-04-01 20:20 ` bugme-daemon
2008-04-01 20:57 ` bugme-daemon
2008-04-01 21:14 ` bugme-daemon
2008-04-01 22:30 ` bugme-daemon
2008-04-02 10:29 ` bugme-daemon
2008-04-02 12:07 ` bugme-daemon
2008-04-02 14:09 ` bugme-daemon
2008-04-02 15:50 ` bugme-daemon
2008-04-02 16:07 ` bugme-daemon
2008-05-17 15:52 ` bugme-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=20080401190526.AE96E11D108@picon.linux-foundation.org \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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