netdev - Re: [Bugme-new] [Bug 12484] New: Kernel panic 1gb lan connection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 26 Jan 2009 23:09:02 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	nice10150@...il.com
Cc:	bugme-daemon@...zilla.kernel.org, netdev@...r.kernel.org
Subject: Re: [Bugme-new] [Bug 12484] New: Kernel panic 1gb lan connection


(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@...zilla.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@...nel-bugs.osdl.org
>         ReportedBy: nice10150@...il.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.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html