Created attachment 24651 [details] ls -l /dev (before crash) I formerly used 2.6.20 and 2.6.24 with a couple of starfire 4 port ethernet cards. On 2.6.32 the interfaces don't start on boot and when I issue "ifconfig ethX up" (where X is a starfire port). Sometimes the exception causes the whole kernel to freeze. Sometimes the kernel keeps going. On the occasion that the kernel kept going I was able to retrieve syslog, which has the full kernel information. Note that in syslog, you can see that I inserted a USB memory stick in order to copy off the attached files. The kernel oops happens without the USB memory stick inserted. I can reproduce this at will. At the moment I simply can't use my two four port starfire network cards. This PC is a root-over-NFS system.
Created attachment 24652 [details] dmesg (post crash)
Created attachment 24653 [details] lsmod (post crash)
Created attachment 24654 [details] lspci (before crash)
Created attachment 24655 [details] /var/log/messages (post crash)
Created attachment 24656 [details] /var/log/syslog (post crash)
That first paragraph should read: I formerly used 2.6.20 and 2.6.24 with a couple of starfire 4 port ethernet cards. On 2.6.32 the interfaces don't start on boot and when I issue "ifconfig ethX up" (where X is a starfire port) *there is an exception*.
Any chance you can try a few kernels in between to see where it broke, at that point we can try and narrow down which change caused the problem better
marked as a regression.
(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Wed, 20 Jan 2010 04:29:20 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=15091 > > Summary: starfire causes kernel BUG when interface goes up > Product: Drivers > Version: 2.5 > Kernel Version: 2.6.32 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Network > AssignedTo: drivers_network@kernel-bugs.osdl.org > ReportedBy: michael@moffatt.org.nz > Regression: No > > > Created an attachment (id=24651) > --> (http://bugzilla.kernel.org/attachment.cgi?id=24651) > ls -l /dev (before crash) > > I formerly used 2.6.20 and 2.6.24 with a couple of starfire 4 port ethernet > cards. On 2.6.32 the interfaces don't start on boot and when I issue > "ifconfig > ethX up" (where X is a starfire port). > > Sometimes the exception causes the whole kernel to freeze. Sometimes the > kernel > keeps going. On the occasion that the kernel kept going I was able to > retrieve > syslog, which has the full kernel information. > > Note that in syslog, you can see that I inserted a USB memory stick in order > to > copy off the attached files. The kernel oops happens without the USB memory > stick inserted. > > I can reproduce this at will. At the moment I simply can't use my two four > port > starfire network cards. > > This PC is a root-over-NFS system. > Starfire is triggering the BUG_ON(!test_bit(NAPI_STATE_SCHED, &n->state)); in napi_enable(). This is a regression somewhere between 2.6.24 and 2.6.32(!).
Hi Andrew, I believe that this is a regression, yes. I will attempt to compile up some kernels this week and provide more info. Should I start at 26 and go up or at 31 and go down? I can't use anything lower than 26 according to udev. I was running 24 but compiled 32 when I upgraded udev. Regards, Michael. Andrew Morton wrote: > (switched to email. Please respond via emailed reply-to-all, not via the > bugzilla web interface). > > On Wed, 20 Jan 2010 04:29:20 GMT > bugzilla-daemon@bugzilla.kernel.org wrote: > > >> http://bugzilla.kernel.org/show_bug.cgi?id=15091 >> >> Summary: starfire causes kernel BUG when interface goes up >> Product: Drivers >> Version: 2.5 >> Kernel Version: 2.6.32 >> Platform: All >> OS/Version: Linux >> Tree: Mainline >> Status: NEW >> Severity: normal >> Priority: P1 >> Component: Network >> AssignedTo: drivers_network@kernel-bugs.osdl.org >> ReportedBy: michael@moffatt.org.nz >> Regression: No >> >> >> Created an attachment (id=24651) >> --> (http://bugzilla.kernel.org/attachment.cgi?id=24651) >> ls -l /dev (before crash) >> >> I formerly used 2.6.20 and 2.6.24 with a couple of starfire 4 port ethernet >> cards. On 2.6.32 the interfaces don't start on boot and when I issue >> "ifconfig >> ethX up" (where X is a starfire port). >> >> Sometimes the exception causes the whole kernel to freeze. Sometimes the >> kernel >> keeps going. On the occasion that the kernel kept going I was able to >> retrieve >> syslog, which has the full kernel information. >> >> Note that in syslog, you can see that I inserted a USB memory stick in order >> to >> copy off the attached files. The kernel oops happens without the USB memory >> stick inserted. >> >> I can reproduce this at will. At the moment I simply can't use my two four >> port >> starfire network cards. >> >> This PC is a root-over-NFS system. >> >> > > Starfire is triggering the BUG_ON(!test_bit(NAPI_STATE_SCHED, > &n->state)); in napi_enable(). > > This is a regression somewhere between 2.6.24 and 2.6.32(!). > > >
On Tue, 26 Jan 2010 14:44:31 +1300 Michael <michael@moffatt.org.nz> wrote: > Hi Andrew, > > I believe that this is a regression, yes. > > I will attempt to compile up some kernels this week and provide more > info. Should I start at 26 and go up or at 31 and go down? > > I can't use anything lower than 26 according to udev. I was running 24 > but compiled 32 when I upgraded udev. > Thanks. Starfire is a pretty rarely-used driver, I suspect. Hopefully someone who understands the NAPI stuff can look at the code and go "ah-hah", and save you all that work. But if that doesn't happen then yup, a bisection would be good, thanks. The best way to do it really is with git. http://landley.net/writing/git-quick.html has an explanation.
Added starfire-clean-up-properly-if-firmware-loading-fails.patch to -mm.