Date: Fri, 11 Sep 2009 15:01:10 +0200 From: Raul <raul@pop.isdefe.es> To: Chris Ruiz <yr.retarded@gmail.com> Cc: Andrew Tulloch <andrew@flarn.com>, freebsd-current@freebsd.org Subject: Re: Boot-time hang with the CISS driver on HP 385 Message-ID: <4AAA4A16.4060709@pop.isdefe.es> In-Reply-To: <4AA797D1.9050409@pop.isdefe.es> References: <54854a7a0907150322n52a3595el5352a3987d2c75ac@mail.gmail.com> <58c737d70907151035ya9a829eyf4945d1fadc4ce0e@mail.gmail.com> <4A5EFFF7.4060708@pop.isdefe.es> <4AA797D1.9050409@pop.isdefe.es>
next in thread | previous in thread | raw e-mail | index | archive | help
Raul escribió: [....] > ciss0: PERFORMANT Transport > ciss0: can't allocate interrupt > panic: mtx_unlock() of spin mutex (null) @ > /usr/src/sys/dev/ciss/ciss.c:1903 > cpuid = 0 > KBD: enter: panic > .... [....] After (some) re-reading and comparing dmesg's of other colleagues with this hardware (hp dl 385) something wrong was happening with the irq mapping on my boxes (acpi?). Several upgrades of bios, other OS running on them before ... whatever. As a quick and dirty try i've erased nvram leaving behind all previous settings. As a result, boot process goes further ... and stop setting something about ipv6. I'll see more tomorrow. Maybe this can also help on other systems with similar ciss controllers. Regars, Raul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4AAA4A16.4060709>