6.4-beta, panic: mii_phy_setmedia (BCM762)

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

6.4-beta, panic: mii_phy_setmedia (BCM762)

geannie
System: HP EliteDesk 705 G1 DM Business PC
Network card: Broadcom BCM762

Unable to do trace as USB keyboard is not working at ddb.

How do I enable USB keyboard in ddb?

I searched the archives and recent commits and was unable to find
anything pertaining to this.

I was able to choose bge0 during installation to pull files, but in
6.3-release and 6.4-beta, I get this panic during boot, and bsd.sp causes
the same: pf enabled starting network panic: mii_phy_setmedia Stopped at
db_enter+0x5: popq %rbp TID PID UID PRFLAGS PFLAGS CPU COMMAND *502360
43328 0 0x3 0 0K dhclient db_enter() at db_enter+0x5 panic() at panic+0x129
mii_phy_setmedia(2) at mii_phy_setmedia+0x11b
ukphy_service(ffff80000047b660,0,ffff8000001ad600) at ukphy_service+0x86
mii_mediachg(8803) at mii_mediachg+0x4c bge_stop(7,ffff80000047b000) at
bge_stop+0x889 bge_init(ffff80000047b00) at bge_init+0x28
bge_ioctl(ffffff03b98fd188,fff80000047b048,80206910) at bge_ioctl+0x31b
ifioctl(ffff8000221f6a30,ffff8000ffffb1d0,ffffff042cb740e0,20) at
ifioctl+0x500 sys_ioctl(360,ffff8000ffffb1d0,0) at sys_ioctl+0x346
syscall() at syscall+0x279 --- syscall (number 54) --- end of kernel end
trace fram: 0x7f7fffff27d0, count: 4 0x1a076d516d6a:
https://www.openbsd.org/ddb.html describes the minimum info required in bug
repots. Insufficient info makes it difficult to find and fix bugs. ddb{0}>
Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

Stuart Henderson
On 2018/08/14 13:24, geannie wrote:
> System: HP EliteDesk 705 G1 DM Business PC
> Network card: Broadcom BCM762
>
> Unable to do trace as USB keyboard is not working at ddb.
>
> How do I enable USB keyboard in ddb?

sysctl machdep.forceukbd=1 (or add machdep.forceukbd=1 to /etc/sysctl.conf)
if you're able .. But what you included did have a trace.

> I searched the archives and recent commits and was unable to find
> anything pertaining to this.
>
> I was able to choose bge0 during installation to pull files, but in
> 6.3-release and 6.4-beta, I get this panic during boot, and bsd.sp causes
> the same:

I'll insert some spaces to make this easier to read:

> pf enabled
> starting network
> panic: mii_phy_setmedia
> Stopped at db_enter+0x5: popq %rbp
> TID PID UID PRFLAGS PFLAGS CPU COMMAND
> *502360 43328 0 0x3 0 0K dhclient
> db_enter() at db_enter+0x5
> panic() at panic+0x129
> mii_phy_setmedia(2) at mii_phy_setmedia+0x11b
> ukphy_service(ffff80000047b660,0,ffff8000001ad600) at ukphy_service+0x86
> mii_mediachg(8803) at mii_mediachg+0x4c
> bge_stop(7,ffff80000047b000) at bge_stop+0x889
> bge_init(ffff80000047b00) at bge_init+0x28
> bge_ioctl(ffffff03b98fd188,fff80000047b048,80206910) at bge_ioctl+0x31b
> ifioctl(ffff8000221f6a30,ffff8000ffffb1d0,ffffff042cb740e0,20) at ifioctl+0x500
> sys_ioctl(360,ffff8000ffffb1d0,0) at sys_ioctl+0x346
> syscall() at syscall+0x279
> --- syscall (number 54) ---
> end of kernel
> end trace fram: 0x7f7fffff27d0, count: 4 0x1a076d516d6a:
> https://www.openbsd.org/ddb.html describes the minimum info required in bug
> repots. Insufficient info makes it difficult to find and fix bugs. ddb{0}>

Have you tried older versions as well or just 6.3 / 6.4-beta? If you've
tried older, are they also failing on this machine? Or, if older ones are
working, what's the first one that fails?

Did bsd.rd work? Or did you do the install some other way (not directly
on the machine, or with bge disabled)?

Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

geannie
>Have you tried older versions as well or just 6.3 / 6.4-beta? If you've
>tried older, are they also failing on this machine? Or, if older ones are
>working, what's the first one that fails?

Working backwards, I wound up trying 5.5 and 5.6, but I was unable to
type at the install prompt.

Next, I successfully installed 5.7 through 6.2. Each of these then
panicked on mii_phy_setmedia on first boot.

>Did bsd.rd work? Or did you do the install some other way (not directly
>on the machine, or with bge disabled)?

bsd.rd worked.

Booting without hostname.bge0 is enough to boot normally, but dhclient
or ifconfig causes panic.

Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

Stuart Henderson
On 2018/08/15 10:28, geannie wrote:
> >Have you tried older versions as well or just 6.3 / 6.4-beta? If you've
> >tried older, are they also failing on this machine? Or, if older ones are
> >working, what's the first one that fails?
>
> Working backwards, I wound up trying 5.5 and 5.6, but I was unable to
> type at the install prompt.
>
> Next, I successfully installed 5.7 through 6.2. Each of these then
> panicked on mii_phy_setmedia on first boot.

Thanks for testing those, if one of them had booted it would point us
in the direction of a commit that broke things.

> >Did bsd.rd work? Or did you do the install some other way (not directly
> >on the machine, or with bge disabled)?
>
> bsd.rd worked.
>
> Booting without hostname.bge0 is enough to boot normally, but dhclient
> or ifconfig causes panic.

Next suggestion is to boot -current (without hostname.bge0) and get
a dmesg that you can copy into an email (either transferring it via
USB stick or another NIC if you have one - USB NICs are often handy
for this) so we can see what the hardware is.

I think the NIC you mentioned as being "Broadcom 762" is actually
BCM5762 but the dmesg would give more accurate information about this.

Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

geannie
dmesg.txt is attached.
On Wed, 15 Aug 2018 at 10:41, Stuart Henderson <[hidden email]> wrote:

>
> On 2018/08/15 10:28, geannie wrote:
> > >Have you tried older versions as well or just 6.3 / 6.4-beta? If you've
> > >tried older, are they also failing on this machine? Or, if older ones are
> > >working, what's the first one that fails?
> >
> > Working backwards, I wound up trying 5.5 and 5.6, but I was unable to
> > type at the install prompt.
> >
> > Next, I successfully installed 5.7 through 6.2. Each of these then
> > panicked on mii_phy_setmedia on first boot.
>
> Thanks for testing those, if one of them had booted it would point us
> in the direction of a commit that broke things.
>
> > >Did bsd.rd work? Or did you do the install some other way (not directly
> > >on the machine, or with bge disabled)?
> >
> > bsd.rd worked.
> >
> > Booting without hostname.bge0 is enough to boot normally, but dhclient
> > or ifconfig causes panic.
>
> Next suggestion is to boot -current (without hostname.bge0) and get
> a dmesg that you can copy into an email (either transferring it via
> USB stick or another NIC if you have one - USB NICs are often handy
> for this) so we can see what the hardware is.
>
> I think the NIC you mentioned as being "Broadcom 762" is actually
> BCM5762 but the dmesg would give more accurate information about this.
>

dmesg.txt (6K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

geannie
I realized after the fact that was from the last bsd.rd boot. Here is
the latest dmesg after a regular boot.
On Wed, 15 Aug 2018 at 15:10, geannie <[hidden email]> wrote:

>
> dmesg.txt is attached.
> On Wed, 15 Aug 2018 at 10:41, Stuart Henderson <[hidden email]> wrote:
> >
> > On 2018/08/15 10:28, geannie wrote:
> > > >Have you tried older versions as well or just 6.3 / 6.4-beta? If you've
> > > >tried older, are they also failing on this machine? Or, if older ones are
> > > >working, what's the first one that fails?
> > >
> > > Working backwards, I wound up trying 5.5 and 5.6, but I was unable to
> > > type at the install prompt.
> > >
> > > Next, I successfully installed 5.7 through 6.2. Each of these then
> > > panicked on mii_phy_setmedia on first boot.
> >
> > Thanks for testing those, if one of them had booted it would point us
> > in the direction of a commit that broke things.
> >
> > > >Did bsd.rd work? Or did you do the install some other way (not directly
> > > >on the machine, or with bge disabled)?
> > >
> > > bsd.rd worked.
> > >
> > > Booting without hostname.bge0 is enough to boot normally, but dhclient
> > > or ifconfig causes panic.
> >
> > Next suggestion is to boot -current (without hostname.bge0) and get
> > a dmesg that you can copy into an email (either transferring it via
> > USB stick or another NIC if you have one - USB NICs are often handy
> > for this) so we can see what the hardware is.
> >
> > I think the NIC you mentioned as being "Broadcom 762" is actually
> > BCM5762 but the dmesg would give more accurate information about this.
> >

dmesg.txt (10K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

geannie
Is there anything else I can provide that may help identify the source
of this issue?

Reply | Threaded
Open this post in threaded view
|

Re: 6.4-beta, panic: mii_phy_setmedia (BCM762)

geannie
Hello,

I just updated to 6.4-current, and I am just following up with this.
The bug is still present. I've attached the latest dmesg.

Thank you.

dmesg.txt (11K) Download Attachment