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] [day] [month] [year] [list]
Date:	Mon, 2 Jul 2007 13:22:20 +0200 (CEST)
From:	<skyball000@...esurf.fr>
To:	<g.liakhovetski@....de>
Cc:	<linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21-rt9 problem : xruns

> On Fri, 29 Jun 2007 skyball000@...esurf.fr wrote:
>
>> Hi,
>>
>> I've recently compiled a "vanilla" 2.6.21 kernel, patched with Ingo
>> Molnar's rt-8 patch, as I was unable to compile with rt-7.
>>
>> I needed it because I'm using audio applications (tests were made with
>> FrugalWare, but I don't think it's a distro issue).
>>
>> Everything was allright until I changed my motherboard for an  Asrock
>> 4coreDual-Vsta (I formerly used a Nforce4 one), with VIA PT880 Ultra
>> chipset.
>>
>> I've justed switched the hardware, as Linux is neat enough to boot
>> without having to reinstall the whole OS.
>>
>> Since, I get tons of xruns when using RT applications, and the only
>> solution I've found to "fix" it was to disable ACPI at boot time.
>
> Interestingly, this looks very similar to a problem I had... Could you,
>  please, verify if acpid is running (with ACPI configured on), and if
> yes -  stop it and retest for xruns?
>
> Thanks
> Guennadi
>
I've only seen a "kacpid" (unkillable), managed to stop ACPI services with
init scripts but xruns are still there (a few less).

>> Moreover, I get this message at boot time :
>> PCI: BIOS bug: MCFG area@...00000 is not E820 reserved
>> PCI: not using MMCONFIG
>>
>> I've also tested this hardware setup with a UbuntoStudio kernel
>> (2.6.19), and everything works flawlessy (no XRUNS, no kernel
>> messages) !
>>
>> So here is my question (I'd like to understand what's happening) :
>>    - is it a kernel (or patch) issue ?
>>    - is it a bad chipset support in the latest kernel versions ? -
>>    could this be related to BIOS issues only (I've tried all available
>> versions without any change) ?
>>    - should I use special settings in the ".config" in order to avoid
>>    these
>> problems ?
>>
>> I wasn't able to detect what causes these XRUNS, so if anyone has
>> clues ...
>>
>> Regards
>> skb
>>
>>
>>
>>
>>
>> -
>> 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/
>>
>
> ---
> Guennadi Liakhovetski



-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ