Home > Apic Error > Apic Error On Cpu0 40 40 Debian

Apic Error On Cpu0 40 40 Debian

des IT-Zentrums)

Please attempt to reproduce this bug with a current version of Fedora (presently Fedora 8). I would guess that booting with "noapic" would suppress the problem. Now i am confused as to how to permanently change it. Tom Verdaat (tom-verdaat) wrote on 2007-01-14: #26 full dmesg output Edit (73.4 KiB, text/plain) Download full text (8.1 KiB) I've got the same errors on my Asus L5800C laptop. Discover More

Also, the occur evenly on CPU0 and CPU1. However, if I resort to safe boot - and then "do nothing" and an exit, the xserver comes up fine (though app launch times are quite large) Checked logs and saw If it isn't necessary, why is it on in the first place? Check vendor BIOS [ 20.285410] assign_interrupt_mode Found MSI capability [ 20.285430] Allocate Port Service[0000:00:06.0:pcie00] [ 20.285455] Allocate Port Service[0000:00:06.0:pcie01].. .. [ 26.887398] irq 233: nobody cared (try booting with the "irqpoll"

Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. Could my problem be due to some hardware incompatibility with Jaunty? Seems it did for others. I have Core 2 Duo.

the bug fix is to change machine and update BIOS? With that options, DSL boots but displays maybe a thousand times "APIC error on CPU0: 40(40)". Comment 12 wax 2008-05-21 08:41:18 UTC i am glad i could help but... Please re-open this bug or file a new one if you can provide the requested data, and thanks for filing the original report!

How about also adding noapic to the list of parameters? Closing this issue out as it was hardware specific and the original reporter is no longer having the problem. If you need to reset your password, click here. RTL-8139/8139C/8139C+ (rev 10) 02:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd.

  1. You should be presented with the current boot options, something along the lines of "/boot/vmlinuz root=UUID=e9c019e5-d78a-4cc0-8c4a-129eadbe0e3b ro quiet splash" although the line is so long it will probably have been wrapped
  2. Ralf Hildebrandt (ralf-hildebrandt) wrote on 2006-12-03: #11 The bug also occurs on $ uname -a Linux knarzkiste 2.6.19-7-lowlatency #2 SMP Wed Nov 29 03:36:17 UTC 2006 x86_64 GNU/Linux in Feisty Cristian
  3. Affecting: linux-source-2.6.22 (Ubuntu) Filed here by: James Tait When: 2008-06-16 Completed: 2008-06-16 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu

That would make it easier to ask for support from HP. RTL-8029(AS) Comment 1 Kyle Pablo 2007-08-20 12:15:30 EDT I am getting the same ACPI dump in my log. If there is any other information I can provide, please let me know. ---------- $ cat /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 15 model : 36 model adding it with nopaic caused system stop at very beginning of boot process.

Dyson (dyson) wrote on 2007-06-29: #51 Try recompiling the kernel without IDE support. http://lanprolab.net/apic-error/apic-error-on-cpu0-40-40.php Seems to start only if the system is put to some load, though (launching Eclipse, VMWare or a database server). Use the cursor keys > to select the kernel line. > > Press 'e' to edit the boot options. Thanks, Richard Seguin Ralf Hildebrandt (ralf-hildebrandt) wrote on 2008-06-17: #84 * Richard Seguin

See attached dmesg output. Having a problem logging in? When you first boot, before the Ubuntu splash/progress > screen, GRUB should present you with a list of options. http://lanprolab.net/apic-error/apic-error-on-cpu0-4040-debian.php Changed in linux: importance: Medium → Undecided status: Triaged → Invalid Launchpad Janitor (janitor) wrote on 2008-12-23: Kernel team bugs #86 Per a decision made by the Ubuntu Kernel Team, bugs

I always says APIC error on CPU(0): 40(40) Comment 1 Thomas Gleixner 2008-01-15 23:21:18 UTC APIC error on CPU0: 40(40): The APIC received an illegal interrupt vector. James Tait (jamestait) wrote on 2007-01-22: #28 However, the BIOS update coupled with the irqpoll kernel option at boot does appear to have stopped the APIC error messages. Even worse: i've had no problems running breezy and dapper but I am since recently experiencing random hangups in Edgy.

The original fix was a bios upgrade... > > What kernel are you running now?

Update BIOS and not problem. James Tait (jamestait) wrote on 2007-01-22: #27 Ben, Cristian: As Alvin pointed out above, updating the BIOS on Acer Ferrari 4005 WLMi does not solve this problem. many thanks stderr. acpidump.txt > Downloaded: - pmtools-20071116.tar.gz 20-Nov-2007 17:55 50K Files: - http://gigabox.org/pub/dmesg - http://gigabox.org/pub/acpidump.txt - http://gigabox.org/pub/config lspci: - http://gigabox.org/pub/lspci cat /proc/interrupt - http://gigabox.org/pub/inter Comment 16 Zhang Rui 2008-06-04 18:49:41 UTC >APIC error

Krzysztof Wyszyński (goomior) wrote on 2007-06-26: #50 BIOS upgrade on Toshiba Tecra A8-183 to version 3.40 fixes this issue. I'm not too familiar with GRUB (I usually use LILO), but it should tell you a key to press to edit the kernel boot parameters before it times out - might It now reads "kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=7fa103ed-2bbe-4b75-9685-ca02cd31254e ro single acpi=off pci=noacpi apm=force" I am pretty new to linux but think I did that right. this page I disabled ACPI Fan (and Processor) in kernel like this: /usr/src/linux -> make menuconfig Power Management Options -> ACPI( Advanced Configuration and Power Interface) Support -> here you have item, Fan

I kind of a newby Thx in advance, Robbert robberttheman View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by robberttheman 07-30-2004, 07:55 AM mp (m-p) wrote on 2008-06-16: #82 Download full text (3.6 KiB) Richard Seguin wrote: > This is where this bug gets confusing, there are few people here with > the same Read more... could you please explain how to dissable acpi for the fan?

Affecting: linux-source-2.6.17 (Ubuntu) Filed here by: Ralf Hildebrandt When: 2006-10-19 Completed: 2007-03-20 Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu I tried blacklisting my firewire modules as i assumed they were the problem but the are not. However, it seems to be working OK but at a lower resolution. Edit bug mail Other bug subscribers Subscribe someone else Bug attachments Output of "sudo lspci -vv" (edit) Output of dmesg shortly after a clean bootup (edit) dmesg output (edit) full dmesg

This seems to tally with Richard Seguin's link above, but can anyone verify my assumption that this BIOS will be safe to use with Ubuntu?