[DragonFlyBSD - Bug #2652] 189a0ff3761b47 ... ix: Implement MSI-X support locks up Lenovo S10 Intel Atom n270

bugtracker-admin at leaf.dragonflybsd.org bugtracker-admin at leaf.dragonflybsd.org
Thu Mar 6 00:09:11 PST 2014

Issue #2652 has been updated by swildner.

On Thu, 06 Mar 2014 08:38:14 +0100,  
<bugtracker-admin at leaf.dragonflybsd.org> wrote:

> Issue #2652 has been updated by davshao.
> I built the kernel multiple times git reset --hard-ing commits  
> one-by-one and the problems began exactly with the mentioned commit.
> Furthermore I would not make any assumption the hpt27xx driver can't be  
> partially responsible as does not the hpt_init() call in  
> sys/dev/raid/hpt27xx/osm_bsd.c call an init_config() function that is in  
> turn I believed defined as hpt27xx_init_config in hpt27xx_config.h?  But  
> hpt27xx_init_config() is not defined in the source -- is it a function  
> called from the HighPoint binary blob?

Yes, but I've had the exact same issue (random hangs at boot) independent  
of whether the hpt* drivers were compiled in or not. It would just hang at  
the "md0: ..." message then.

But a check would be easy. Just move the os_printk() in hpt_init() below  
init_config(), or add another message after hpt_init(), and look (in the  
case when it hangs) if the message wasn't printed.


Bug #2652: 189a0ff3761b47 ... ix: Implement MSI-X support locks up Lenovo S10 Intel Atom n270

* Author: davshao
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
For a i386 Lenovo S10 Intel Atom n270 netbook, bisection indicates using
189a0ff3761b47 ... ix: Implement MSI-X support and enable multiple TX rings
locks up the machine on booting at the point:

md0: invalid primary partition table: no magic
Math emulator present
hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2
hpt27xx: RocketRAID 27xx controller driver v1.0 (Feb 28 2014 21:38:19)

Attached is a full verbose dmesg from the same machine running with master
previous to the above commit.  The machine only fully boots with
acpi disabled using hint.acpi.0.disabled=1, but even with acpi enabled the
lockup with the problematic commit occurs sooner than the normal lockup
with acpi enabled.  "Normally" on this machine booting with acpi halts at

acpi0: <LENOVO CB-01> [tentative] on motherboard
ACPI: All ACPI Tables successfully acquired
ACPI FADT: SCI testing interrupt mode ...
ACPI FADT: SCI testing level/high
IOAPIC: irq 9, gsi 9 edge/high -> level/high

lenovo_s10_dmesg.txt (36.5 KB)

You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account

More information about the Bugs mailing list