Bug #1380

panic: assertion _tp->tt_msg->tt_cpuid == mycpuid

Added by ftigeot over 5 years ago. Updated over 5 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi,

This one is 100% reproductible.

System is a Core 2 Duo machine, 3GB RAM running today's 2.3.1.

Pushing the ATX power button to shut down the machine results in the following
panic:
[I have skipped the function arguments in the panic message.]

panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
mp_lock: 00000001; cpuid = 1
Trace beginning at frame 0xdceb6cbc

panic
panic
tcp_close
tcp_disconnect
tcp_user_detach
netmsg_pru_detach
netmsg_service
tcpmsg_service
lwkt_exit()
Debugger("panic")

[...]

History

#1 Updated by sepherosa over 5 years ago

On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
> Hi,
>
> This one is 100% reproductible.
>
> System is a Core 2 Duo machine, 3GB RAM running today's 2.3.1.
>
> Pushing the ATX power button to shut down the machine results in the following
> panic:
> [I have skipped the function arguments in the panic message.]
>
> panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
> mp_lock: 00000001; cpuid = 1
> Trace beginning at frame 0xdceb6cbc
>
> panic
> panic
> tcp_close
> tcp_disconnect
> tcp_user_detach
> netmsg_pru_detach
> netmsg_service
> tcpmsg_service
> lwkt_exit()
> Debugger("panic")

Could you generate a coredump?

BTW, did you set extra network MPSAFE tunables?

Best Regards,
sephe

#2 Updated by ftigeot over 5 years ago

On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
> >
> > Pushing the ATX power button to shut down the machine results in the following
> > panic:
> >
> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
>
> Could you generate a coredump?

I'm trying.
I called dumpsys at the ddb prompt and the kernel seemed to dump but during
the following boot I got nothing in /var/crash.

> BTW, did you set extra network MPSAFE tunables?

I didn't. Here's the sysctl list:

# sysctl -a | grep mpsafe
net.inet.tcp.mpsafe_thread: 1
net.inet.udp.mpsafe_thread: 1
net.netisr.mpsafe_thread: 1

The only difference with an out of the box 2.3.1 is the kernel:
I started from GENERIC, enabled SMP (without APIC), disabled I486_CPU and
I586_CPU, and disabled most unneeded drivers.

#3 Updated by sepherosa over 5 years ago

On Fri, May 22, 2009 at 2:56 PM, Francois Tigeot <> wrote:
> On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
>> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
>> >
>> > Pushing the ATX power button to shut down the machine results in the following
>> > panic:
>> >
>> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
>>
>> Could you generate a coredump?
>
> I'm trying.
> I called dumpsys at the ddb prompt and the kernel seemed to dump but during
> the following boot I got nothing in /var/crash.

will "shutdown now" trigger the panic?

>
>> BTW, did you set extra network MPSAFE tunables?
>
> I didn't. Here's the sysctl list:
>
> # sysctl -a | grep mpsafe
> net.inet.tcp.mpsafe_thread: 1
> net.inet.udp.mpsafe_thread: 1
> net.netisr.mpsafe_thread: 1
>
> The only difference with an out of the box 2.3.1 is the kernel:
> I started from GENERIC, enabled SMP (without APIC), disabled I486_CPU and
> I586_CPU, and disabled most unneeded drivers.
>
> --
> Francois Tigeot
>

#4 Updated by sepherosa over 5 years ago

On Fri, May 22, 2009 at 4:14 PM, Sepherosa Ziehau <> wrote:
> On Fri, May 22, 2009 at 2:56 PM, Francois Tigeot <> wrote:
>> On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
>>> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
>>> >
>>> > Pushing the ATX power button to shut down the machine results in the following
>>> > panic:
>>> >
>>> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
>>>
>>> Could you generate a coredump?
>>
>> I'm trying.
>> I called dumpsys at the ddb prompt and the kernel seemed to dump but during
>> the following boot I got nothing in /var/crash.
>
> will "shutdown now" trigger the panic?

BTW, do you have:
kern.sync_on_panic=0
in /etc/sysctl.conf
and
dumpdev="your_swap_device"
in /etc/rc.conf

Best Regards,
sephe

#5 Updated by ftigeot over 5 years ago

On Fri, May 22, 2009 at 07:39:50PM +0800, Sepherosa Ziehau wrote:
> On Fri, May 22, 2009 at 4:14 PM, Sepherosa Ziehau <> wrote:
> > On Fri, May 22, 2009 at 2:56 PM, Francois Tigeot <> wrote:
> >> On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
> >>> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
> >>> >
> >>> > Pushing the ATX power button to shut down the machine results in the following
> >>> > panic:
> >>> >
> >>> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
> >
> > will "shutdown now" trigger the panic?

Yes, as well as all forms of shutdown:
shutdown -p now
shutdown -h now
pressing ctrl-alt-del

> BTW, do you have:
> kern.sync_on_panic=0
> in /etc/sysctl.conf
> and
> dumpdev="your_swap_device"
> in /etc/rc.conf

I didn't have the sync_on_panic line; it works much better now.

I have put the vmcore here:
http://www.wolfpond.org/crash.dfly/

#6 Updated by sepherosa over 5 years ago

On Sat, May 23, 2009 at 4:05 PM, Francois Tigeot <> wrote:
> On Fri, May 22, 2009 at 07:39:50PM +0800, Sepherosa Ziehau wrote:
>> On Fri, May 22, 2009 at 4:14 PM, Sepherosa Ziehau <> wrote:
>> > On Fri, May 22, 2009 at 2:56 PM, Francois Tigeot <> wrote:
>> >> On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
>> >>> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
>> >>> >
>> >>> > Pushing the ATX power button to shut down the machine results in the following
>> >>> > panic:
>> >>> >
>> >>> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
>> >
>> > will "shutdown now" trigger the panic?
>
> Yes, as well as all forms of shutdown:
>  shutdown -p now
>  shutdown -h now
>  pressing ctrl-alt-del
>
>> BTW, do you have:
>> kern.sync_on_panic=0
>> in /etc/sysctl.conf
>> and
>> dumpdev="your_swap_device"
>> in /etc/rc.conf
>
> I didn't have the sync_on_panic line; it works much better now.
>
> I have put the vmcore here:
> http://www.wolfpond.org/crash.dfly/

I got the kernel. However, the vmcore's permisssion is not correctly
setup, so I could not download it.

Best Regards,
sephe

#7 Updated by ftigeot over 5 years ago

On Sat, May 23, 2009 at 08:44:14AM +0000, Sepherosa Ziehau (via DragonFly issue tracker) wrote:
>
> Sepherosa Ziehau <> added the comment:
>
> On Sat, May 23, 2009 at 4:05 PM, Francois Tigeot <> wrote:
> > On Fri, May 22, 2009 at 07:39:50PM +0800, Sepherosa Ziehau wrote:
> >> On Fri, May 22, 2009 at 4:14 PM, Sepherosa Ziehau <> wrote:
> >> > On Fri, May 22, 2009 at 2:56 PM, Francois Tigeot <> wrote:
> >> >> On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
> >> >>> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
> >> >>> >
> >> >>> > Pushing the ATX power button to shut down the machine results in the following
> >> >>> > panic:
> >> >>> >
> >> >>> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
> >> >
> >> > will "shutdown now" trigger the panic?
> >
> > Yes, as well as all forms of shutdown:
> >  shutdown -p now
> >  shutdown -h now
> >  pressing ctrl-alt-del
> >
> >> BTW, do you have:
> >> kern.sync_on_panic=0
> >> in /etc/sysctl.conf
> >> and
> >> dumpdev="your_swap_device"
> >> in /etc/rc.conf
> >
> > I have put the vmcore here:
> > http://www.wolfpond.org/crash.dfly/
>
> I got the kernel. However, the vmcore's permisssion is not correctly
> setup, so I could not download it.

Sorry about that.
I just modified the permissions, please try again.

#8 Updated by sepherosa over 5 years ago

On Sat, May 23, 2009 at 4:52 PM, Francois Tigeot <> wrote:
> On Sat, May 23, 2009 at 08:44:14AM +0000, Sepherosa Ziehau (via DragonFly issue tracker) wrote:
>>
>> Sepherosa Ziehau <> added the comment:
>>
>> On Sat, May 23, 2009 at 4:05 PM, Francois Tigeot <> wrote:
>> > On Fri, May 22, 2009 at 07:39:50PM +0800, Sepherosa Ziehau wrote:
>> >> On Fri, May 22, 2009 at 4:14 PM, Sepherosa Ziehau <> wrote:
>> >> > On Fri, May 22, 2009 at 2:56 PM, Francois Tigeot <> wrote:
>> >> >> On Fri, May 22, 2009 at 09:23:15AM +0800, Sepherosa Ziehau wrote:
>> >> >>> On Fri, May 22, 2009 at 2:48 AM, Francois Tigeot <> wrote:
>> >> >>> >
>> >> >>> > Pushing the ATX power button to shut down the machine results in the following
>> >> >>> > panic:
>> >> >>> >
>> >> >>> > panic: assertion: _tcp->tt_msg->tt_cpuid == mycpuid in tcp_callout_stop
>> >> >
>> >> > will "shutdown now" trigger the panic?
>> >
>> > Yes, as well as all forms of shutdown:
>> >  shutdown -p now
>> >  shutdown -h now
>> >  pressing ctrl-alt-del
>> >
>> >> BTW, do you have:
>> >> kern.sync_on_panic=0
>> >> in /etc/sysctl.conf
>> >> and
>> >> dumpdev="your_swap_device"
>> >> in /etc/rc.conf
>> >
>> > I have put the vmcore here:
>> > http://www.wolfpond.org/crash.dfly/
>>
>> I got the kernel.  However, the vmcore's permisssion is not correctly
>> setup, so I could not download it.
>
> Sorry about that.
> I just modified the permissions, please try again.

Thank you very much for the coredump. Please test HEAD, I believe I
have fixed it.

Best Regards,
sephe

#9 Updated by ftigeot over 5 years ago

On Sat, May 23, 2009 at 11:40:26AM +0000, Sepherosa Ziehau (via DragonFly issue tracker) wrote:
>
> Thank you very much for the coredump. Please test HEAD, I believe I
> have fixed it.

Well, thank *you* for fixing the bug.

I have just tested the new HEAD. It doesn't crash anymore.

#10 Updated by luxh over 5 years ago

fixed with 697aadcd03f60a7715f28694a62840c6148eacf3

Also available in: Atom PDF