2005-05-04 21:05:12

by Jim Faulkner

[permalink] [raw]
Subject: Re: strange 3c59x behaviour under 2.6.11.7


Some background for the linux-kernel folks:

http://www.scyld.com/pipermail/vortex/2005-May/002483.html

http://www.scyld.com/pipermail/vortex/2005-May/002484.html

On Tue, 3 May 2005, Bogdan Costescu wrote:

> > Any ideas on what is causing this problem, and how to fix it?
>
> Try booting with acpi=off.
> Try updating BIOS and/or modify power related options in BIOS.

I've tried disabling ACPI in the kernel, turning on APM support in the
BIOS, and the combination of the two, and unfortunately the problem
persisted.

However, I found this patch (the one at the very bottom of the page):
http://www.mail-archive.com/[email protected]/msg78894.html

And after adapting it to the 2.6.11.7 kernel, everything works again!
I've rebooted the machine several times, and the 3com cards initialized
successfully every time.

I'm CC'ing linux-kernel in the hopes that this fix can make it into the
mainstream kernel sometime soon. I'm sure my mother would appreciate it
greatly. :)

Please CC my e-mail address in any replies as I am not subscribed to this
list.

thanks,
Jim Faulkner


2005-05-04 21:36:51

by Alexander Nyberg

[permalink] [raw]
Subject: Re: strange 3c59x behaviour under 2.6.11.7

> Some background for the linux-kernel folks:
>
> http://www.scyld.com/pipermail/vortex/2005-May/002483.html
>
> http://www.scyld.com/pipermail/vortex/2005-May/002484.html
>
> On Tue, 3 May 2005, Bogdan Costescu wrote:
>
> > > Any ideas on what is causing this problem, and how to fix it?
> >
> > Try booting with acpi=off.
> > Try updating BIOS and/or modify power related options in BIOS.
>
> I've tried disabling ACPI in the kernel, turning on APM support in the
> BIOS, and the combination of the two, and unfortunately the problem
> persisted.
>
> However, I found this patch (the one at the very bottom of the page):
> http://www.mail-archive.com/[email protected]/msg78894.html
>
> And after adapting it to the 2.6.11.7 kernel, everything works again!
> I've rebooted the machine several times, and the 3com cards initialized
> successfully every time.
>
> I'm CC'ing linux-kernel in the hopes that this fix can make it into the
> mainstream kernel sometime soon. I'm sure my mother would appreciate it
> greatly. :)
>
> Please CC my e-mail address in any replies as I am not subscribed to this
> list.

[netdev needs to be up on the CC on this too]

Yeah I get the same behaviour reliably when doing kexec on a box with
the 3c59x, lspci shows:

0000:00:0f.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 74)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management NIC
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (2500ns min, 2500ns max), Cache Line Size: 0x08 (32 bytes)
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at b000 [size=128]
Region 1: Memory at ef004000 (32-bit, non-prefetchable) [size=128]
Capabilities: [dc] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=2 PME-
00: b7 10 00 92 07 00 10 02 74 00 00 02 08 20 00 00
10: 01 b0 00 00 00 40 00 ef 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 b7 10 00 10
30: 00 00 00 00 dc 00 00 00 00 00 00 00 05 01 0a 0a


2005-05-04 21:44:39

by Andrew Morton

[permalink] [raw]
Subject: Re: strange 3c59x behaviour under 2.6.11.7

Jim Faulkner <[email protected]> wrote:
>
> However, I found this patch (the one at the very bottom of the page):
> http://www.mail-archive.com/[email protected]/msg78894.html
>
> And after adapting it to the 2.6.11.7 kernel, everything works again!
> I've rebooted the machine several times, and the 3com cards initialized
> successfully every time.
>
> I'm CC'ing linux-kernel in the hopes that this fix can make it into the
> mainstream kernel sometime soon. I'm sure my mother would appreciate it
> greatly. :)

I was planning on merging that post-2.6.12, but I guess it looks fairly
safe...