[Xen-ia64-devel] [Patch] fix warnings while rebooting

[Akio Takebe <takebe_akio@xxxxxxxxxxxxxx>]

Hi,

I have warnings in RHEL5/FC6 at reboot time.
This patch fix the only following warning.
"free_irq_vector: double free!"

BTW, the Call Trace is fixed by the following patch.
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=edd106fc8ac1826dbe231b70ce0762db24133e5c;hp=e78181feb0b94fb6afeaef3b28d4f5df1b847c98

I'm not sure yet which is better A or B.
A. "# /etc/xen/scripts/network-bridge stop" before reboot
B. apply the above e1000 patch

Best Regards,

Akio Takebe

>Hi, Aron and RHEL5 guys
>
>I found e1000_shutdown of 2.6.18 don't call e1000_free_irq().
>e1000_shutdown of 2.6.19 call e1000_free_irq().
>
>I'm testing now, and I'll post the patch to Aron.
>
>BTW, 2.6.16.29 of xen-ia64-unstable don't call .shutdown handler.
>So this issue is not occurred on it.
>
>Best Regards,
>
>Akio Takebe
>
>>Hi,
>>
>>I'm debugging the following Bugzilla now.
>>    RH Bugzilla#203032: xen/ia64 kernel BUG while rebooting
>>    https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=203032
>>
>>RHEL5beta and FC6 still show the CallTrace while rebooting.
>>I check why it is shown.
>>I found thd CallTrace is not shown if we reboot after doing the below.
>># /etc/xen/scripts/network-bridge stop
>>
>>I think it should be happened also by using source of xen-ia64-unstable. 
>>(not RH source)
>>But e1000_shutdown() is not called when I use source of xen-ia64-unstable.
>>I don't know why yet.
>>I'll continue to debug it.
>>
>>If you have comments, please tell me.
>>
>>Best Regards,
>>
>>Akio Takebe
>>
>>
>>_______________________________________________
>>Xen-ia64-devel mailing list
>>Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>>http://lists.xensource.com/xen-ia64-devel

free_irq.patch
Description: Binary data

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel