Kernal Panic Clarification

[nivek1612]

I saw the hot fix for Kernal panics which suggests the correct version
identifies itself as "stable/24.7-n267981-8375762712f" using uname - v

I get the following
root@home:~ # uname -v
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267979-0d692990122 SMP

I have tried to issue the
opnsense-update -fk
and reboot but no change.

Am I miss reading the update notes

[franco]

Depends on mirror and if it already synced. If in doubt use default mirror.


Cheers,
Franco

[nivek1612]

sorry to be dumb how do I ensure its the default mirror from the shell

[franco]

Which one is it then?

# opnsense-update -M

To make quick work of it...

# opnsense-update -sd
# opnsense-update -M

Note setting defaults with opnsense-update is not permanent.


Cheers,
Franco

[nivek1612]

changed the mirror to default in GUI then tried again from console

root@home:~ # uname -v
FreeBSD 14.1-RELEASE-p6 stable/24.7-n267981-8375762712f SMP

All is good again.

Thanks

[franco]

always nice to hear from you although it's only when I screw up :D

[nivek1612]

That is why we don't speak often it's very rare you do

Oh and Orange France is behaving themselves now which makes life much easier.

[franco]

> Oh and Orange France is behaving themselves now which makes life much easier.

Splendid, when did that happen? Or just no more custom changes on their end to make our lives harder?


Cheers,
Franco

[nivek1612]

Orange published a list of connection requirements some time ago. If you stick to them (various send options in defined format etc), the connections are very stable.

TLDR

https://lafibre.info/remplacer-livebox/durcissement-du-controle-de-loption-9011-et-de-la-conformite-protocolaire/

[franco]

Ah neat to have this on file, thanks!

[Malmoth]

Interestingly, I'm facing the exact same issue even though I'm on the default mirror.

[passeri]

For info, none of my upgrades picked up the new kernel although I think all are using the default mirror, to which I had returned after a previous problem.

I have two production (bravely titled for a home user) routers, one being perimeter and one internal, and a backup/test machine. All were updated from 24.7.9 to 24.7.10_1, then _2 and none finished with the newer kernel. Only the perimeter router kept panicking, slipping past my prior updates on the less critical machines which did not at all. It was stable overnight but panicky in use. All the machines/CPUs are different, not ideal for QC.

The terminal procedures for kernel update appear to have fixed it, and the others updated likewise.

[Malmoth]

The terminal procedures for kernel update appear to have fixed it, and the others updated likewise.

Can you clarify "the terminal procedures for kernel update" so that I can give that a shot myself?

[AhnHEL]

Can you clarify "the terminal procedures for kernel update" so that I can give that a shot myself?

See this link
https://forum.opnsense.org/index.php?topic=44413.msg221775#msg221775

[franco]

> Interestingly, I'm facing the exact same issue even though I'm on the default mirror.

"uname -v" please. We've already had one user using "opnsense-update -fk" wondering why they land on a 24.7.8 kernel which is entirely correct when you are not on 24.7.10 yet in which case the kernel hotfix procedure doesn't matter anyway. :)


Cheers,
Franco