On Fri, 20 Aug 2010 08:03:21 +0300 Plamen Petrov [off-list ref] wrote:

(responding via emailed reply-to-all)

____ 20.8.2010 __. 01:21, Andrew Morton ____________:

quoted

(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Thu, 19 Aug 2010 09:57:25 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

quoted

https://bugzilla.kernel.org/show_bug.cgi?id=16626

            Summary: Machine hangs with EIP at skb_copy_and_csum_dev
            Product: Drivers
            Version: 2.5
     Kernel Version: 2.6.36-rc1-00127-g763008c
           Platform: All
         OS/Version: Linux
               Tree: Mainline
             Status: NEW
           Severity: blocking
           Priority: P1
          Component: PCI
         AssignedTo: drivers_pci@kernel-bugs.osdl.org
         ReportedBy: pvp-lsts@fs.uni-ruse.bg
         Regression: Yes

A post-2.6.35 regression.

quoted

After upgrade from 2.6.33.7 to 2.6.35.2 a server hanged twice, so
continued on 2.6.33.7.

Today decided to try lates Linus' tree with no luck.

The first time I started on 2.6.36-rc1-00127-g763008c it ran for a few
minutes, then whent dead with this on the screen:
[picture 1]
http://picpaste.com/9cfb03116d41f27568e1bb2a67b7f4dc.jpg

[picture 2]
Then I power-cycled the machine, only two get this:
http://picpaste.com/6d70f453e462d1aed038781ad4bdb741.jpg

And because [picture 2] seemed too bad on the lower half of the screen,
here is
[picture 3]
http://picpaste.com/0a51ae079ace2e4abd9e9d29226069f7.jpg

Might have triggered the BUG_ON() in skb_copy_and_csum_dev().  Might be
a tg3 thing.  Hard to tell.

It'd be really nice to get that first screenful.  Sigh.  How long have
we had this oops-scrolls-off problem??  Perhaps you could set
/proc/sys/kernel/printk_delay to 100 (it's in milliseconds) so that the
oops scrolls past nice and slowly?

So you need the begining of the oops screen - I will try to get that
with the proposed pirntk_delay setting.

Thanks.

But wich kernel should I use? Linus' latest tree or 2.6.35.2 ? They
both fail the same way here, as far as I can say.

Current mainline would be best, because we'd fix the bug there first
then backport the fix into -stable.  But it doesn't matter a lot in
this case - whatever's most convenient for you, I'd say.