Bug 12484 - Kernel panic 1gb lan connection
Summary: Kernel panic 1gb lan connection
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: Other
Classification: Unclassified
Component: Modules (show other bugs)
Hardware: All Linux
: P1 high
Assignee: other_modules
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-19 02:10 UTC by Richard Leeuw
Modified: 2009-03-23 08:56 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.27
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Richard Leeuw 2009-01-19 02:10:36 UTC
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.
Comment 1 Anonymous Emailer 2009-01-26 23:09:23 UTC
Reply-To: akpm@linux-foundation.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.
Comment 2 Alan 2009-03-23 08:56:50 UTC
No response, closing. Please re-open this bug if its still a problem

Note You need to log in before you can comment on or make changes to this bug.