[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#417333: FYI, may be have similar problem on another type of HW



> From: Olivier Berger
> Newsgroups: gmane.linux.debian.devel.kernel
> Subject: Bug#417333: FYI, may be have similar problem on another type of HW
> Date: Mon, 02 Apr 2007 13:35:28 +0200
>
> Hi.
>
> FYI, I entered a report (#417333) for a problem which show traces
> similar to that one...

Well, i think #391955 may be closed, because it seems to be fixed in
2.6.18-stable by the patch from this report:

<http://permalink.gmane.org/gmane.linux.network/48625> (debug)
<http://permalink.gmane.org/gmane.linux.network/48703> (patch)

> I'm not sure though it's solved in latest kernel version.

Please look at suggested in the link debugging tools, in case you will hit
*your* bug again, because it has some traces of other fault:

,-*-
| [<.......>] dst_output
| [<.......>] ip_queue_xmit
| [<.......>] dst_output
| [<.......>] tcp_transmit_skb
| [<.......>] tcp_push_one
| [<.......>] tcp_sendmsg
| [<.......>] inet_sendmsg
| [<.......>] do_sock_write
| [<.......>] sock_writev
| [<.......>] do_wp_page
| [<.......>] __handle_mm_fault             <-- here
| [<.......>] autoremove_wake_function
| [<.......>] __next_cpu
| [<.......>] sock_writev
| [<.......>] do_readv_writev
| [<.......>] vfs_writev
| [<.......>] sys_writev
| [<.......>] sysenter_past_esp
|Code: ....
|EIP: [<c024c735>] tcp_tso_segment ...
| <0>Kernel panic - not syncing: Fatal exception in interrupt
`-*-

And that fault was preempted by the interrupt, thus we see a panic.

So, this is my view on that. Hope it helps, also.
____



Reply to: