From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugme-daemon@bugzilla.kernel.org Subject: [Bug 10374] sym53c8xx: weird behavior with udev Date: Tue, 1 Apr 2008 12:05:26 -0700 (PDT) Message-ID: <20080401190526.AE96E11D108@picon.linux-foundation.org> References: Return-path: Received: from smtp1.linux-foundation.org ([140.211.169.13]:55928 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755399AbYDATF5 (ORCPT ); Tue, 1 Apr 2008 15:05:57 -0400 Received: from picon.linux-foundation.org (picon.linux-foundation.org [140.211.169.79]) by smtp1.linux-foundation.org (8.14.2/8.13.5/Debian-3ubuntu1.1) with ESMTP id m31J5Q5x004790 for ; Tue, 1 Apr 2008 12:05:27 -0700 In-Reply-To: Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: linux-scsi@vger.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.