netdev - Re: Tulip 21142 panic on physical link disconnect

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <70660feba172c7933cd5521527df523c@wizardsworks.org>
Date: Tue, 10 Jun 2025 11:33:35 -0700
From: Greg Chandler <chandleg@...ardsworks.org>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: stable@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Tulip 21142 panic on physical link disconnect


Thanks!  I appreciate you getting back to me.  I've got about 30 huge 
bugs I am shaking down, and this one just cropped up, so I haven't been 
able to put a lot of time into it yet.
I rolled a full debug kernel last night to troubleshoot what appears to 
be a spinlock/mutex issue with something else, but I'm sure it'll help 
with this too.

If I find anything out I will also reply with the details....



On 2025/06/10 09:27, Florian Fainelli wrote:
> Howdy!
> 
> On 6/9/25 15:43, Greg Chandler wrote:
>> 
>> This is a from-scratch build (non-vendor/non-distribution)
>> Host/Target = alpha ev6
>> Kernel source = 6.12.12
>> 
>> My last working kernel on this was a 2.6.x, it's been a while since 
>> I've had time to bring this system up to date, so I don't know when 
>> this may have started.
>> I had a 3.0.102 in there, but I didn't test the networking while using 
>> it.
>> 
>> Please let me know what I can do to help out with figuring this one 
>> out.
> 
> I don't have an Alpha machine to try this on, but I do have a 
> functional Cobalt Qube2 (MIPS 32/64) with these adapters connected 
> directly over PCI:
> 
> 00:07.0 Ethernet controller: Digital Equipment Corporation DECchip 
> 21142/43 (rev 41)
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr+ Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 64 (5000ns min, 10000ns max), Cache Line Size: 32 
> bytes
>         Interrupt: pin A routed to IRQ 19
>         Region 0: I/O ports at 1000 [size=128]
>         Region 1: Memory at 12082000 (32-bit, non-prefetchable) 
> [size=1K]
>         Expansion ROM at 12000000 [disabled] [size=256K]
>         Kernel driver in use: tulip
> 
> 
> 00:0c.0 Ethernet controller: Digital Equipment Corporation DECchip 
> 21142/43 (rev 41)
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
> ParErr- Stepping- SERR- FastB2B- DisINTx-
>         Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium 
> >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
>         Latency: 64 (5000ns min, 10000ns max), Cache Line Size: 32 
> bytes
>         Interrupt: pin A routed to IRQ 20
>         Region 0: I/O ports at 1080 [size=128]
>         Region 1: Memory at 12082400 (32-bit, non-prefetchable) 
> [size=1K]
>         Expansion ROM at 12040000 [disabled] [size=256K]
>         Kernel driver in use: tulip
> 
> the machine is not currently on a switch that I can control, but I can 
> certainly try to plug in the cable and see what happens, give me a 
> couple of days to get back to you, and if you don't hear back,  please 
> holler. Here are the bits of kernel configuration:
> 
> CONFIG_NET_TULIP=y
> CONFIG_TULIP=y
> # CONFIG_TULIP_MWI is not set
> # CONFIG_TULIP_MMIO is not set
> # CONFIG_TULIP_NAPI is not set