On 02/24/2013 06:39 AM, Tilman Schmidt wrote:
> Am 22.02.2013 21:10, schrieb Robert Moskowitz:
>> On 02/22/2013 03:04 PM, Reindl Harald wrote:
>>> Am 22.02.2013 20:58, schrieb Robert Moskowitz:
>>>
Once before (5+ years back) I had to add a kernel param and did it wrong
and
it was
Am 22.02.2013 21:10, schrieb Robert Moskowitz:
>
> On 02/22/2013 03:04 PM, Reindl Harald wrote:
>>
>> Am 22.02.2013 20:58, schrieb Robert Moskowitz:
>>
>>> Once before (5+ years back) I had to add a kernel param and did it wrong and
>>> it was a big recovery challenge
>> what is the challenge?
>>
On 02/22/2013 03:04 PM, Reindl Harald wrote:
>
> Am 22.02.2013 20:58, schrieb Robert Moskowitz:
>> Kernel param. I really should have caught that.
>>
>> So I was all ready to edit grub.conf and then slapped my hand.
>> You TEST it out first, adding the command at boot time. ARGH!
> one option
>
On 02/22/2013 02:32 PM, Reindl Harald wrote:
>
> Am 22.02.2013 20:28, schrieb Robert Moskowitz:
>>> on a similar/identical bug with Fedora FC17, someone suggested booting
>>> with iommu=off to work around this.
>> Where do I add this?
> like every other kernel param in /boot/grub/grub.conf at
> th
Robert Moskowitz wrote:
>
> On 02/22/2013 01:38 PM, John R Pierce wrote:
>> On 2/21/2013 12:43 PM, Robert Moskowitz wrote:
>>> :[Firmware Warn]: Your BIOS is broken; DMAR reported at address
>>> fed9
>>> returns all ones!
>> I googled "Your BIOS is broken; DMAR reported at address fed9
>> r
On 02/22/2013 01:38 PM, John R Pierce wrote:
> On 2/21/2013 12:43 PM, Robert Moskowitz wrote:
>> :[Firmware Warn]: Your BIOS is broken; DMAR reported at address fed9
>> returns all ones!
> I googled "Your BIOS is broken; DMAR reported at address fed9
> returns all ones!" and got some relat
On 2/21/2013 12:43 PM, Robert Moskowitz wrote:
> :[Firmware Warn]: Your BIOS is broken; DMAR reported at address fed9
> returns all ones!
I googled "Your BIOS is broken; DMAR reported at address fed9
returns all ones!" and got some related results.
this bug report (on FC12) says... "yes
On 02/21/2013 06:55 PM, John R Pierce wrote:
> On 2/21/2013 3:20 PM, Robert Moskowitz wrote:
>>> :Hardware name: HP Compaq dc7800 Small Form Factor
>>> ...
> Should I worry?
>>> yes.
>>>
>>> You should update bios .
> hmmm, thats a 2007 vintage economy business desktop ?
>
> looks to be a Dece
On 02/21/2013 06:55 PM, John R Pierce wrote:
> On 2/21/2013 3:20 PM, Robert Moskowitz wrote:
>>> :Hardware name: HP Compaq dc7800 Small Form Factor
>>> ...
> Should I worry?
>>> yes.
>>>
>>> You should update bios .
> hmmm, thats a 2007 vintage economy business desktop ?
>
> looks to be a Dece
On 2/21/2013 3:20 PM, Robert Moskowitz wrote:
>> :Hardware name: HP Compaq dc7800 Small Form Factor
>> ...
>> >>Should I worry?
> >yes.
> >
> >You should update bios .
hmmm, thats a 2007 vintage economy business desktop ?
looks to be a December 2011 rev 1.32A BIOS, here
http://h2.www2.hp.com/
On 02/21/2013 06:13 PM, Eero Volotinen wrote:
> 2013/2/21 Robert Moskowitz :
>> I am getting the following on my 'new box' for my DNS server:
>>
>> Date: Wed, 20 Feb 2013 13:58:04 -0500
>> From:
>> To:
>> Subject: [abrt] full crash report
>> User-Agent: Heirloom mailx 12.4 7/29/08
>>
>> abrt_versi
2013/2/21 Robert Moskowitz :
> I am getting the following on my 'new box' for my DNS server:
>
> Date: Wed, 20 Feb 2013 13:58:04 -0500
> From:
> To:
> Subject: [abrt] full crash report
> User-Agent: Heirloom mailx 12.4 7/29/08
>
> abrt_version: 2.0.8
> cmdline:ro root=/dev/mapper/vg_onlo3
I am getting the following on my 'new box' for my DNS server:
Date: Wed, 20 Feb 2013 13:58:04 -0500
From:
To:
Subject: [abrt] full crash report
User-Agent: Heirloom mailx 12.4 7/29/08
abrt_version: 2.0.8
cmdline:ro root=/dev/mapper/vg_onlo3-root_01 rd_NO_LUKS
rd_LVM_LV=vg_onlo3/root_01
13 matches
Mail list logo
