From: Andrew Morton <akpm@linux-foundation.org>
To: nice10150@gmail.com
Cc: bugme-daemon@bugzilla.kernel.org, netdev@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 12484] New: Kernel panic 1gb lan connection
Date: Mon, 26 Jan 2009 23:09:02 -0800 [thread overview]
Message-ID: <20090126230902.85af7ea9.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12484-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 19 Jan 2009 02:10:36 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12484
>
> Summary: Kernel panic 1gb lan connection
> Product: Other
> Version: 2.5
> KernelVersion: 2.6.27
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: high
> Priority: P1
> Component: Modules
> AssignedTo: other_modules@kernel-bugs.osdl.org
> ReportedBy: nice10150@gmail.com
>
>
> Latest working kernel version:?
> Earliest failing kernel version:2.6.27
> Distribution: Fedora 10, Ubuntu, etc...
> Hardware Environment: Asus P4S800D-E Delux mother board with Marvell Yukon
> giga-lan chipset.
> Software Environment:
> Problem Description: The combination of Marvel 1gb Lan connection and kernel
> 2.6.27 generates a kernel panic at boot. The identical setup connected to a
> 10/100 network boots regular.
>
> Steps to reproduce: Boot system equipped with (Asus motherboard) Marvell Yukon
> network chipset connected to a 1gb Lan enabled network.
>
We'd like a bit more information about the panic please.
Ideally, set up a serial console and capture the entire kernel output.
If that is not practical, perhaps a digital photograph of the screen?
Setting the screen into 50-row mode beforehand is often useful.
Worst-case, just type it all in again :( Usually all the hexadecimal
numbers can just be omitted when doing this.
Thanks.
parent reply other threads:[~2009-01-27 7:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-12484-10286@http.bugzilla.kernel.org/>]
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=20090126230902.85af7ea9.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nice10150@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).