Ubuntu
linux-source-2.6.20 package

[Feisty] Linux 2.6.20 spams 'Intel ISA PCIC probe: not found.' all over /var/log/messages

Bug #76341 reported by Randakar
40
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: linux-source-2.6.20

When booting in 2.6.20, suddenly /var/log/messages is spammed with:

Dec 18 21:52:45 localhost kernel: [ 163.416320] Intel ISA PCIC probe: not found.
Dec 18 21:52:45 localhost kernel: [ 163.435252] Intel ISA PCIC probe: not found.
Dec 18 21:52:45 localhost kernel: [ 163.482263] Intel ISA PCIC probe: not found.
Dec 18 21:52:45 localhost kernel: [ 163.531793] Intel ISA PCIC probe: not found.
Dec 18 21:52:45 localhost kernel: [ 163.579588] Intel ISA PCIC probe: not found.
Dec 18 21:52:45 localhost kernel: [ 163.627409] Intel ISA PCIC probe: not found.
Dec 18 21:52:46 localhost kernel: [ 163.671705] Intel ISA PCIC probe: not found.
Dec 18 21:52:46 localhost kernel: [ 163.719473] Intel ISA PCIC probe: not found.
Dec 18 21:52:46 localhost kernel: [ 163.769181] Intel ISA PCIC probe: not found.
....

I'll attach lspci + boot log shortly.

Revision history for this message
Randakar (randakar) wrote :
Revision history for this message
Randakar (randakar) wrote :
Revision history for this message
Adam Klobukowski (adamklobukowski) wrote :

I had similar problem. Turning off pcmcia in /etc/defaults/pcmcia and /etc/defaults/pcmciautils solved it for me.

Revision history for this message
Ben Collins (ben-collins) wrote :

Needs testing against 2.6.20-3

Changed in linux-source-2.6.20:
status: Unconfirmed → Needs Info
Ben Collins (ben-collins)
Changed in linux-source-2.6.20:
importance: Undecided → High
status: Needs Info → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

still the same with -5

Revision history for this message
joe (joerg-unglaub) wrote :

Same problem for me via kt266 with athlon.

Disableing pcmcia works for me too.

But why does this help, if there is no pcmcia hardware in my system.

Revision history for this message
José M. López-Cepero (cepe) wrote :

I can confirm the error. 2.6.20-4-generic kernel, AMD Sempron 2800+, VIA chipset (I don't remember the exact model right now, but I think it's a KT266 or KT333). Turning off pcmcia also worked for me. With the bug active, almost half of the processor time was wasted because of it (more specifically, because of dd copying the klogd output to /var/log/messages), so I'd bump up its priority.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

for me this makes it impossible to install machines which suffer from this

Revision history for this message
Matt MacLeod (mmacleod) wrote :

This happens to be on a P4 system as well.

Revision history for this message
Colin Watson (cjwatson) wrote :

See http://lkml.org/lkml/2006/11/29/260 for further details on this.

Revision history for this message
Colin Watson (cjwatson) wrote :

You can work around this during installation by adding "hw-detect/start_pcmcia=false" to the kernel command line.

Revision history for this message
André FL Ribeiro (andre-fl-ribeiro) wrote :

same error here ... feisty daily build 24-01-2007

not only in P4 but also on intel core processors

tested with HP Compaq nc6320 (intel core duo) and P4

Revision history for this message
Ben Collins (ben-collins) wrote :

Used the patch in the lkml link. Not ideal, but no other solution made it into upstream yet.

Changed in linux-source-2.6.20:
status: Confirmed → Fix Committed
Revision history for this message
Dave Gilbert (ubuntu-treblig) wrote :

This is still happening on a feisty beta3 on a Dell Optiplex 745 - it eventually gets there but takes ages.
(Core 2 Duo, modern Intel chipset)

Ben Collins (ben-collins)
Changed in linux-source-2.6.20:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.