lkml.org 
[lkml]   [2004]   [Oct]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch] VP-2.6.9-rc4-mm1-T8

    * K.R. Foley <kr@cybsft.com> wrote:

    > Booted part way this time but then soft locked. [...]

    the soft lock it seems was due to a mutex assert in the TCP code. Now i
    see that you have the ipv6 module loaded. Would it be possible to
    disable ipv6 briefly, to see whether there are other issues?

    > Mouse was still working but not KB. Any idea why the KB is not working
    > with these? I am rebuilding with all of the pwr managment off because
    > I am still getting acpi messages in the boot :-/ [...]

    hm, the keyboard should be working - i have not seen any specific
    keyboard problems with PREEMPT_REALTIME enabled (except in the very
    early stages of this feature). So it must be something else. Is this a
    PS2 or an USB keyboard?

    > Oct 12 15:33:39 swdev14 kernel: NET: Registered protocol family 10
    > Oct 12 15:33:39 swdev14 kernel: IPv6 over IPv4 tunneling driver
    > Oct 12 15:33:40 swdev14 kernel: ------------[ cut here ]------------
    > Oct 12 15:33:40 swdev14 kernel: kernel BUG at kernel/mutex.c:185!

    > Oct 12 15:33:40 swdev14 kernel: EIP is at _rw_mutex_write_unlock+0x25/0x2f

    > Oct 12 15:33:40 swdev14 kernel: Call Trace:
    > Oct 12 15:33:40 swdev14 kernel: [<c0253738>] tcp_listen_start+0x175/0x1d1
    > Oct 12 15:33:40 swdev14 kernel: [<c029a33a>] _spin_unlock_bh+0x1a/0x34
    > Oct 12 15:33:40 swdev14 kernel: [<c0275a8c>] inet_listen+0x65/0x7a
    > Oct 12 15:33:40 swdev14 kernel: [<c02287ea>] sys_listen+0x5c/0x74
    > Oct 12 15:33:40 swdev14 kernel: [<c02294a4>] sys_socketcall+0xb1/0x239
    > Oct 12 15:33:40 swdev14 kernel: [<c015ae81>] sys_close+0x75/0x91

    this assert says that a write_unlock() was done before the mutex was
    initialized - which is a no-no. Note that the stock kernel does not do
    this checking and there's a chance that it has a true bug here which it
    ignores silently. The more likely scenario is that the kernel mutex code
    somewhere changed an assumption which broke the code. I'll try to
    reproduce this.

    Ingo
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:07    [W:0.039 / U:125.736 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site