On Tue, 18 Oct 2011 14:23:59 +0700, Sthu Deus wrote:
>>>>http://www.google.com/webhp?complete=0&hl=en#q=debian+MP-BIOS+bug:+8254+timer+not+connected+to+IO-APIC&hl=en&tbo=1&complete=0&prmd=imvns&tbas=0&source=lnt&sa=X&ei=2RKbTrePHMfAswbhocmUBA&ved=0CAkQpwUoAA&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=bd638b897581bb57&biw=1280&bih=888
>>>
>>> Uhh. Why chromium does not open the link? :/
>>
>>It can't? :-?
>
> It does, but shows me their start page rather than a search results list
> - as I supposed it should deliver, should not?
Mmm... yes, the URL should be passed "as is" (without breaking) from your
e-mail client to your browser.
(...)
> (I have enclosed the URI between "<...>" to avoid it breaks)
>
> I have checked before for breaks - so, Still the same.
>
> OK. I will make a new request - fetching things from the URL. Please
> don't mind. It was just strange to me - such chromium behavior.
Okay :-)
>>> I do not say that, just saw that - as we are talking on performance, I
>>> thought may that timer bug has any affect on HDD too. :\
>>
>>Okay. Anyway, being related or not, true is that there are lots of ACPI
>>errors :-(
>
> Yes, You are right... And w/ the kernels, acpi-related programs, the
> situation does not change...
>
> In case I want to change the situation - not w/ my problem only but the
> software as a whole - what should bug report against - which package(s):
> acpi, acpid, something else?
I think those errors come from the kernel itself, not from a particular
package.
You can try to pass the kernel some arguments to deal with that messages,
as I said earlier ("pci=use_crs" was suggested by the log but there are
others -many- you can try related to acpi or apic). If you open the URL
for the Google search I passed before, you can see lots of suggestions
awaiting for you to try :-)
>>Lastly, there is a log for an ext4 error:
>>
>>[ 304.096062] EXT4-fs (sda2): error count: 15 [ 304.096073] EXT4-fs
>>(sda2): initial error at 1313766195: ext4_mb_generate_buddy:736 [
>>304.096083] EXT4-fs (sda2): last error at 1315801717:
>>ext4_reserve_inode_write:5619
>>
>>If those errors are logged frequently it may indicate a problem with the
>>filesystem.
>
> I would say it was the first time. Rather weird remounts accur at boot:
>
> [ 11.010837] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
> [ 19.630649] EXT4-fs (dm-0): mounted filesystem with ordered data mode.
> Opts: errors=remount-ro
>
> [ 82.183242] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro,commit=0
>
> [ 84.304981] EXT4-fs (dm-0): re-mounted. Opts: errors=remount-ro,commit=0
I'd say those are normal entries for an ext4 filesystem if they occur at
booting (for fsck tasks) and not once the system is loaded.
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.10.18.13.19...@gmail.com
