http://bugzilla.kernel.org/show_bug.cgi?id=10374 ------- Comment #2 from seraph@xxxxxxxxx 2008-04-01 01:58 ------- On Tue, 1 Apr 2008 01:15:18 -0700 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > (switched to email. Please respond via emailed reply-to-all, not via the > bugzilla web interface). > > 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. Alright, here goes. Attached three files. dmesg-2.6.22.9-good.txt is the dmesg output from 2.6.22.9 where everything works as it should. dmesg-2.6.24.4-bad.txt is the dmesg output from 2.6.24.4 with sym53cxx loaded by udev and the network not responding. dmesg-2.6.24.4-good.txt is the dmesg output from 2.6.24.4 with sym53cxx blacklisted and the network working fine. -- 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
