30 Nov 17:23
Bug#497692: linux-image-2.6.26-1-686: In my case adding pci=nomsi made the system bootable, but ...
From: Gerrit Jan Baarda <gjbaarda <at> xs4all.nl>
Subject: Bug#497692: linux-image-2.6.26-1-686: In my case adding pci=nomsi made the system bootable, but ...
Newsgroups: gmane.linux.debian.devel.kernel
Date: 2008-11-30 16:25:58 GMT
Subject: Bug#497692: linux-image-2.6.26-1-686: In my case adding pci=nomsi made the system bootable, but ...
Newsgroups: gmane.linux.debian.devel.kernel
Date: 2008-11-30 16:25:58 GMT
Package: linux-image-2.6.26-1-686 Version: 2.6.26-11 Followup-For: Bug #497692 I had exactly the same behaviour when upgrading to 2.6.26. I managed to make my system bootable by adding pci=nomsi to the kernel startup line. However I see the following messages in dmesg: [ 797.309745] +------ PCI-Express Device Error ------+ [ 797.309745] Error Severity : Uncorrected (Non-Fatal) [ 797.309745] PCIE Bus Error type : Transaction Layer [ 797.309745] Flow Control Protocol : First [ 797.309745] Receiver ID : 0010 [ 797.309745] VendorID=1106h, DeviceID=a327h, Bus=00h, Device=02h, Function=00h [ 797.309745] Broadcast error_detected message [ 797.309745] Broadcast mmio_enabled message [ 797.309745] Broadcast resume message [ 797.309745] AER driver successfully recovered It looks like this error is also related to the console. For example, an entry is inserted almost everytime a debconf dialog is opened. And if I run less <somefile> in a console, and then scroll beyond the last line I get this message most every 'beep'. During my struggles to get the system bootable again I noticed that the current (lenny) installer apparently has similar problems. I tried to run the console rescue mode, but that results in a blank screen. However running the graphical rescue mode works just fine.(Continue reading)
RSS Feed