Date: Thu, 23 Oct 2014 22:30:16 +0300 From: Mailing lists <gprs@paladin.bulgarpress.com> To: Alan Somers <asomers@freebsd.org> Cc: stable@freebsd.org Subject: Re: FreeBSD 9.1 + Supermicro IPMI + reboot = kernel crash Message-ID: <54495748.7090604@paladin.bulgarpress.com> In-Reply-To: <CAOtMX2hxEwRUmDaZzaK-sRE0QJjqg976GfYLawgOiK-wFr7GGA@mail.gmail.com> References: <5448C35C.5080600@paladin.bulgarpress.com> <CAOtMX2hxEwRUmDaZzaK-sRE0QJjqg976GfYLawgOiK-wFr7GGA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Alan, appreciated! Todor On 10/23/2014 07:03 PM, Alan Somers wrote: > On Thu, Oct 23, 2014 at 2:59 AM, Mailing lists > <gprs@paladin.bulgarpress.com> wrote: >> Hi people, >> I've three machines - FreeBSD 9.1 (i386+amd64) - at reboot usually the >> kernel dump and therefore gmirror rebuilds, etc. >> >> After reboot - kldload show the module is inserted but /dev/ipmi* is not >> populated, kldunload + kldload of the module fixes the access + >> /dev/ipmi* population. >> >> Any ideas (except upgrade which I plan to 9.3 soon)? >> >> +Waiting (max 60 seconds) for system process `vnlru' to stop...done >> +Waiting (max 60 seconds) for system process `bufdaemon' to stop...done >> + >> +Waiting (max 60 seconds) for system process `syncer' to stop...Syncing >> disks, vnodes remaining...9 Sleeping thread (tid 100093, pid 16) owns a >> non-sleepable lock >> +KDB: stack backtrace of thread 100093: >> +#0 0xffffffff808f3196 at mi_switch+0x186 >> +#1 0xffffffff8092bfa2 at sleepq_wait+0x42 >> +#2 0xffffffff808f3926 at _sleep+0x376 >> +#3 0xffffffff81551227 at ipmi_submit_driver_request+0x97 >> +#4 0xffffffff815519df at ipmi_set_watchdog+0xaf >> +#5 0xffffffff81551c8f at ipmi_wd_event+0x8f >> +#6 0xffffffff807bbdef at kern_do_pat+0x9f >> +#7 0xffffffff80984187 at sched_sync+0x1e7 >> +#8 0xffffffff808bbe3f at fork_exit+0x11f >> +#9 0xffffffff80bc3d9e at fork_trampoline+0xe >> +panic: sleeping thread >> +cpuid = 0 >> +KDB: stack backtrace: >> +#0 0xffffffff80920cf6 at kdb_backtrace+0x66 >> +#1 0xffffffff808ead0e at panic+0x1ce >> +#2 0xffffffff8092f172 at propagate_priority+0x1d2 >> +#3 0xffffffff8092fe9e at turnstile_wait+0x1be >> +#4 0xffffffff808d9198 at _mtx_lock_sleep+0xd8 >> +#5 0xffffffff8097d9b3 at vn_syncer_add_to_worklist+0x143 >> +#6 0xffffffff80981ac4 at reassignbuf+0xe4 >> +#8 0xffffffff8096a232 at bdwrite+0x52 >> +#7 0xffffffff809661c2 at bdirty+0x42 >> +#9 0xffffffff80af4ba9 at ffs_freefile+0x269 >> +#10 0xffffffff80b09711 at handle_workitem_freefile+0x101 >> +#11 0xffffffff80b09ba7 at process_worklist_item+0x377 >> +#12 0xffffffff80b0d8d6 at softdep_process_worklist+0x96 >> +#13 0xffffffff80b0fee7 at softdep_flush+0x197 >> +#14 0xffffffff808bbe3f at fork_exit+0x11f > You want to pull in r272366 from head and rebuild your kernel. That > change hasn't yet been MFCd to stable/9, but I don't think you'll have > any trouble merging it. > > https://svnweb.freebsd.org/base?view=revision&revision=272366 > > -Alan > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54495748.7090604>