From: Jos van der Ende <seraph@xs4all.nl>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-scsi@vger.kernel.org, sparclinux@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev
Date: Tue, 1 Apr 2008 21:05:21 +0200 [thread overview]
Message-ID: <20080401210521.abbb443c.seraph@xs4all.nl> (raw)
In-Reply-To: <1207059115.3100.9.camel@localhost.localdomain>
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.
--
Jos van der Ende <seraph@xs4all.nl>
next prev parent reply other threads:[~2008-04-01 19:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-10374-10286@http.bugzilla.kernel.org/>
2008-04-01 8:15 ` [Bugme-new] [Bug 10374] New: sym53c8xx: weird behavior with udev Andrew Morton
2008-04-01 8:58 ` Jos van der Ende
2008-04-01 14:11 ` James Bottomley
2008-04-01 14:47 ` Jos van der Ende
2008-04-01 19:05 ` Jos van der Ende [this message]
2008-04-01 20:19 ` James Bottomley
2008-04-01 20:57 ` Jos van der Ende
2008-04-01 21:14 ` James Bottomley
2008-04-01 22:30 ` Jos van der Ende
2008-04-02 10:29 ` Jos van der Ende
2008-04-02 12:06 ` Matthew Wilcox
2008-04-02 14:09 ` Jos van der Ende
2008-04-02 15:49 ` James Bottomley
2008-04-02 16:06 ` Jos van der Ende
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=20080401210521.abbb443c.seraph@xs4all.nl \
--to=seraph@xs4all.nl \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sparclinux@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