From: Bill Fink <billfink@mindspring•com>
To: Josip Rodin <joy@entuzijast•net>
Cc: Michael Chan <mchan@broadcom•com>,
Ben Hutchings <bhutchings@solarflare•com>,
netdev <netdev@vger•kernel.org>,
mirrors@debian•org
Subject: Re: bnx2_poll panicking kernel
Date: Sat, 21 Jun 2008 11:34:06 -0400 [thread overview]
Message-ID: <20080621113406.5f89ae8d.billfink@mindspring.com> (raw)
In-Reply-To: <20080621111842.GA32667@orion.carnet.hr>
On Sat, 21 Jun 2008, Josip Rodin wrote:
> On Tue, Jun 17, 2008 at 03:47:22PM -0700, Michael Chan wrote:
> > On Wed, 2008-06-18 at 00:37 +0200, Josip Rodin wrote:
> > > After applying this patch, two rsync runs went through without any problem,
> > > yay.
> > >
> > > Yet, there were no alerts from the new printk in the patch...?
> >
> > Please keep monitoring the printks during future rsyncs with those HTB
> > rules. May be we're just lucky and not hitting the problem this time.
>
> Still nothing after four days. I'm starting to wonder...
>
> The only thing that I did that was slightly out of the ordinary was that
> I applied your patch, ran make modules and then modules_install, and then
> modprobe -r bnx2, modprobe bnx2; IOW I didn't reboot the whole kernel or
> reinitialize HTB. Should I try to do any of that?
Wouldn't the "modprobe -r bnx2" destroy the HTB info for that device?
-Bill
next prev parent reply other threads:[~2008-06-21 15:34 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 12:57 bnx2_poll panicking kernel Josip Rodin
2008-06-16 14:04 ` Ben Hutchings
2008-06-16 15:52 ` Michael Chan
2008-06-16 19:13 ` Josip Rodin
2008-06-16 21:38 ` Josip Rodin
2008-06-16 21:48 ` Josip Rodin
2008-06-16 23:45 ` Michael Chan
2008-06-17 22:37 ` Josip Rodin
2008-06-17 22:47 ` Michael Chan
2008-06-21 11:18 ` Josip Rodin
2008-06-21 15:34 ` Bill Fink [this message]
2008-06-21 16:11 ` Michael Chan
2008-06-23 18:04 ` Josip Rodin
2008-06-23 21:36 ` Josip Rodin
2008-06-23 22:48 ` Michael Chan
2008-06-24 22:58 ` Michael Chan
2008-06-25 0:04 ` David Miller
2008-06-26 11:01 ` Josip Rodin
2008-06-26 18:04 ` Michael Chan
2008-07-09 16:46 ` Josip Rodin
2008-07-09 16:57 ` Michael Chan
2008-07-09 23:46 ` David Miller
2008-07-10 9:45 ` Aviv Greenberg
2008-07-10 10:09 ` David Miller
2008-07-10 21:00 ` Michael Chan
2008-07-10 21:00 ` David Miller
2008-07-10 21:23 ` Josip Rodin
2008-07-10 21:38 ` Michael Chan
2008-07-10 22:00 ` Josip Rodin
2008-07-10 22:26 ` Michael Chan
2008-07-10 22:31 ` Josip Rodin
2008-07-10 23:20 ` David Miller
2008-07-11 9:24 ` Josip Rodin
2008-07-11 9:56 ` David Miller
2008-07-11 12:19 ` Patrick McHardy
2008-07-12 9:49 ` Jarek Poplawski
2008-07-12 13:21 ` Jarek Poplawski
2008-07-14 15:27 ` Patrick McHardy
2008-07-14 17:20 ` Jarek Poplawski
2008-07-14 17:25 ` Jarek Poplawski
2008-07-14 20:21 ` Josip Rodin
2008-07-14 21:22 ` Jarek Poplawski
2008-07-14 21:26 ` Josip Rodin
2008-07-14 21:48 ` Jarek Poplawski
2008-07-17 21:30 ` Josip Rodin
2008-07-17 21:44 ` David Miller
2008-07-18 5:12 ` Jarek Poplawski
2008-08-02 12:28 ` bad htb_{en,re}queue return codes causing corrupt data in drivers [was Re: bnx2_poll panicking kernel] Josip Rodin
2008-08-03 7:06 ` bad htb_{en,re}queue return codes causing corrupt data in drivers David Miller
2008-07-14 22:05 ` bnx2_poll panicking kernel Jarek Poplawski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080621113406.5f89ae8d.billfink@mindspring.com \
--to=billfink@mindspring$(echo .)com \
--cc=bhutchings@solarflare$(echo .)com \
--cc=joy@entuzijast$(echo .)net \
--cc=mchan@broadcom$(echo .)com \
--cc=mirrors@debian$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox