http://bugzilla.kernel.org/show_bug.cgi?id=10374 ------- Comment #3 from anonymous@xxxxxxxxxxxxxxxxxxxx 2008-04-01 07:12 ------- Reply-To: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx On Tue, 2008-04-01 at 01:15 -0700, Andrew Morton wrote: > (switched to email. Please respond via emailed reply-to-all, not via the > bugzilla web interface). > > Steps to reproduce: > > > > Let udev load sym53c8xx in kernel 2.6.23 or newer. > > urgh. Perhaps it's related to platform IRQ routing or something. > > I'd suggest that the next step would be to send us the `dmesg -s 1000000' > output for both good and bad kernels. A comparison might show where things > went bad. Yes, that would be my guess too ... although I don't see anything amiss in the dmesg I note you have two ethernet interfaces: eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:03:ba:08:61:7c eth1394: eth1: IPv4 over IEEE 1394 (fw-host0) I'm assuming eth0 is the problem? Could you also send us the output of /proc/interrupts, /proc/iomem and /proc/ioports just to see if we have a problem. Also, if eth0 is on its own interrupt line, does the interrupt count rise even while the interface is non functional? Thanks, James -- 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. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
