linux-kernel - Re: Failed to initialize MSI interrupts && ioremap reserve

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 07 Apr 2010 17:46:31 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Mark Knecht <markknecht@...il.com>
CC:	Clemens Ladisch <clemens@...isch.de>,
	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: Failed to initialize MSI interrupts && ioremap reserve_memtype
  failed -22

On 04/07/2010 09:57 AM, Mark Knecht wrote:
> On Wed, Apr 7, 2010 at 7:54 AM, Clemens Ladisch<clemens@...isch.de>  wrote:
>> Mark Knecht wrote:
>>>     New hardware and I haven't seen these messages before so I thought
>>> I'd post them.
>>
>> Both might be harmless.  Please show the entire boot log.
>>
>>
>> Regards,
>> Clemens
>>
>
> Hopefully you mean the contents of dmesg. If it's something else let me know.
>
> If the mail server deletes the text file attachment I'll reply again
> pasting the text in by hand.

Looks like the start of the log was truncated. Can you check if your 
distro writes the bootup kernel output somewhere (like /var/log/dmesg)?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/