Bug #2485

panic: already on wildcardhash

Added by isenmann almost 2 years ago. Updated almost 2 years ago.

Status:ResolvedStart date:01/10/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi!

With the lastest fixes from ftigeot I was able to build dports/openjdk7 and to run jenkins on this java vm.
After doing some configuration in jenkins and browsing through the many plugins I and got this "already on wildcardhash" panic.

After reboot I got a second panic within few seconds after using the jenkins web interface.

Called dumpsys this time and got crash dump (about 2GB).

Stopped jenkins, did a git pull (fetching 211d436..839fbab) and a build{world,kernel}.

After reboot and using jenkins I got this panic again within seconds.

Calling dumpsys this time, I got no dump but more panics (see attached dmesg output).

After reboot I got the same situation, with jenkins started during system startup but without using it.
Again no crash dump but more panics.

Attachments:
- dmesg.txt: Removed lots of those mld6_input messages at the beginning, maybe about 30 during the 1h uptime for buildworld and some at the end.
Not sure if it is significant, that there is exactly one of these messages between the reboot and the panic within about one and a half minute.
- core.txt.0: Removed some cruft, especially the mld6_input spam.
- jenkins.log: Add this log, since it contains two "java.net.SocketException: Invalid argument". Maybe those multicast attempts are somehow related.

dmesg.txt Magnifier (43.7 KB) isenmann, 01/10/2013 04:57 AM

core.txt.0 (96.3 KB) isenmann, 01/10/2013 04:57 AM

jenkins.log (3.32 KB) isenmann, 01/10/2013 04:57 AM

History

#1 Updated by sepherosa almost 2 years ago

On Thu, Jan 10, 2013 at 8:57 PM, Goetz Isenmann via Redmine
<> wrote:
>
> Issue #2485 has been reported by Goetz Isenmann.
>
> ----------------------------------------
> Bug #2485: panic: already on wildcardhash

Please test following patch:
http://leaf.dragonflybsd.org/~sephe/udp6_usrreq.diff

Best Regards,
sephe

> http://bugs.dragonflybsd.org/issues/2485
>
> Author: Goetz Isenmann
> Status: New
> Priority: Normal
> Assignee:
> Category:
> Target version:
>
>
> Hi!
>
> With the lastest fixes from ftigeot I was able to build dports/openjdk7 and to run jenkins on this java vm.
> After doing some configuration in jenkins and browsing through the many plugins I and got this "already on wildcardhash" panic.
>
> After reboot I got a second panic within few seconds after using the jenkins web interface.
>
> Called dumpsys this time and got crash dump (about 2GB).
>
> Stopped jenkins, did a git pull (fetching 211d436..839fbab) and a build{world,kernel}.
>
> After reboot and using jenkins I got this panic again within seconds.
>
> Calling dumpsys this time, I got no dump but more panics (see attached dmesg output).
>
> After reboot I got the same situation, with jenkins started during system startup but without using it.
> Again no crash dump but more panics.
>
> Attachments:
> - dmesg.txt: Removed lots of those mld6_input messages at the beginning, maybe about 30 during the 1h uptime for buildworld and some at the end.
> Not sure if it is significant, that there is exactly one of these messages between the reboot and the panic within about one and a half minute.
> - core.txt.0: Removed some cruft, especially the mld6_input spam.
> - jenkins.log: Add this log, since it contains two "java.net.SocketException: Invalid argument". Maybe those multicast attempts are somehow related.
>
>
>
>
> --
> You have received this notification because you have either subscribed to it, or are involved in it.
> To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

--
Tomorrow Will Never Die

#2 Updated by isenmann almost 2 years ago

Ok, rebuilt with your patch, and started jenkins.

Accessed the jenkins web interface, and saw five mld6_input messages since I started jenkins about 10min ago.

Will play around with jenkins tomorrow again and will report if the system is still running.

#3 Updated by isenmann almost 2 years ago

Still no further panic...

After 19:16 uptime, with some configuration done in the jenkins web
interface, with a dummy job running every 7min and with autorefresh on
the build status every few seconds, and with one of those mld6_input
messages about every 2min.

#4 Updated by isenmann almost 2 years ago

  • Status changed from New to Resolved

Also available in: Atom PDF