From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 16142] r8169: Kernel Panic when a lot of data is transferred through network interface
Date: Tue, 15 Jun 2010 11:50:06 GMT [thread overview]
Message-ID: <201006151150.o5FBo6jE014160@demeter.kernel.org> (raw)
In-Reply-To: <bug-16142-11633@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16142
--- Comment #11 from Borislav Petkov <bbpetkov@yahoo.de> 2010-06-15 11:49:59 ---
(In reply to comment #10)
> If you are still interested in the bug, I would try to help you as far as I
> can.
Cool.
> Answers to your questions:
> 1. Proprietary drivers: I am using the nvidia driver, but it was not loaded
> when the bug occurred. (for the 2.6.34 kernel I didn't even installed them)
Ok, please remove the proprietary drivers when reproducing the oops.
> 2. Serial console: sorry this computer does not have an serial port (there is
> one on the motherboard, but I don't have the matching adapter.)
>
> 3. Netconsole: I tried to use it; normal dmesg logging worked, but I did not
> receive the oops messages.
was the netconsole built-in or a module? Try building it into the kernel if
not.
> Right now my questions are:
> 1. Do you still want to take care of this bug?
Sure, I'll give it a try.
> 2. If so, is there a possibility to use firewire to capture the oops messages?
There is something related in <Documentation/debugging-via-ohci1394.txt>
but I haven't tried it yet.
Ok, so what we need now is a cleaner OOPS. If nothing else works, try
making a picture but make sure it is readable and complete. Also, send me the
objdump part I asked you for in the earlier message.
Thanks,
Boris.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-06-15 11:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16142-11633@https.bugzilla.kernel.org/>
2010-06-14 22:17 ` [Bug 16142] r8169: Kernel Panic when a lot of data is transferred through network interface bugzilla-daemon
2010-06-15 6:39 ` bugzilla-daemon
2010-06-15 11:17 ` bugzilla-daemon
2010-06-15 11:50 ` bugzilla-daemon [this message]
2010-06-15 15:19 ` bugzilla-daemon
2010-06-15 15:20 ` bugzilla-daemon
2010-06-15 15:21 ` bugzilla-daemon
2010-06-15 15:21 ` bugzilla-daemon
2010-06-15 15:22 ` bugzilla-daemon
2010-06-15 15:22 ` bugzilla-daemon
2010-06-15 15:26 ` bugzilla-daemon
2010-06-15 19:12 ` bugzilla-daemon
2010-06-15 19:39 ` bugzilla-daemon
2010-07-03 8:26 ` bugzilla-daemon
2012-07-20 12:55 ` bugzilla-daemon
2010-06-17 8:07 Borislav Petkov
[not found] ` <20100617150008.16a5e653@cpc>
2010-06-18 7:45 ` Borislav Petkov
2010-06-18 13:08 ` Hans Mueller
2010-06-18 15:02 ` Borislav Petkov
2010-06-18 22:50 ` Hans Mueller
2010-06-19 10:05 ` Borislav Petkov
2010-06-19 11:27 ` Hans Mueller
2010-06-23 8:02 ` Borislav Petkov
2010-06-25 16:58 ` Hans Mueller
2010-06-30 6:54 ` Borislav Petkov
2010-06-30 18:02 ` Hans Mueller
2010-06-30 18:31 ` Borislav Petkov
2010-07-03 7:49 ` Hans Mueller
2010-07-03 8:23 ` Borislav Petkov
2010-07-03 11:41 ` Hans Mueller
2010-07-03 11:53 ` Borislav Petkov
2010-07-05 11:44 ` Hans Mueller
2010-07-05 12:11 ` Borislav Petkov
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=201006151150.o5FBo6jE014160@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ide@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.