Re: IRQ problems on new Toshiba Libretto

Re: IRQ problems on new Toshiba Libretto

[Aron Lentsch]

Dear Linus, Alan and Jeff,

thank you very much for your replies. I though it is
best, if I respond with one email so we have all in one
place.


On Sat, 9 Jun 2001, Linus Torvalds wrote:

> Can you add the output of "dump_pirq" to your logs? 
> ... 
> together with "lspci -vvvxx" would be useful.

dump_irq returns the following:
-----------------------------------------------------------------------
No PCI interrupt routing table was found.

Interrupt router at 00:07.0: AcerLabs Aladdin M1533
PCI-to-ISA bridge
  INT1 (link 1): irq 11
  INT2 (link 2): unrouted
  INT3 (link 3): unrouted
  INT4 (link 4): unrouted
  INT5 (link 5): unrouted
  INT6 (link 6): unrouted
  INT7 (link 7): unrouted
  INT8 (link 8): unrouted
  Serial IRQ: [enabled] [continuous] [frame=21]
[pulse=8]
-----------------------------------------------------------------------

The output of lspci -vvvxx is a bit longer, so I
have put it in:
http://launchers.tripod.com/linux/lspci_vvvxx.txt


On Sat, 9 Jun 2001, Alan Cox wrote:
> 
> Did you try the pci=biosirq boot option btw ?
> 

Yes, I tried 'pci=biosirq' as well as
'pci=irqmask=0xfff8', but unfortunately I couldn't see
any change.


On Sat, 9 Jun 2001, Jeff Garzik wrote:

> I request two additional outputs:
>  
> 1) lspci -vvvxxx

The putput of lspci -vvvxxx is in:
http://launchers.tripod.com/linux/lspci_vvvxxx.txt              

> 2) Change arch/i386/kernel/pci-i386.h near the top to enable debugging:
> -#undef DEBUG
> +#define DEBUG 1
> 
> and then provide dmesg output as before.  

OK, I recompiled the kernel with this change and the
output of 'dmesg' is in 

http://launchers.tripod.com/linux/dmesg.wDEBUG1.txt


Hope this helps to trace back my problem!
Thank you very much again for your help!

Aron

Re: IRQ problems on new Toshiba Libretto

[Jeff Garzik]

Aron,

Can you also include your kernel .config?

Looking at your dmesg output, there is no mention of a PCI BIOS at all. 
That either implies there is no kernel support for PCI BIOS built in
(ok) or your BIOS doesn't support PCI BIOS (ug).

Further, there is no PCI interrupt routing table found by direct scan of
memory, so it looks like your BIOS is not providing interrupt routing
info at all.  Without that, we can only route irqs on "a wing and a
prayer"


Suggestions:
* Build kernel with CONFIG_PCI_GOANY config option.
* Do not build an SMP kernel (CONFIG_SMP) unless you are really using a
multiprocessor machine.
* Go through BIOS setup.  Check for and enable "PNP OS" setting, and
similar settings which reflect an automatically assignment of machine
resources.

It is also possible that this machine's interrupt routing info is in
ACPI tables..  though I do not believe the Linux ACPI can make use of
this yet.


-- 
Jeff Garzik      | Andre the Giant has a posse.
Building 1024    |
MandrakeSoft     |

Re: IRQ problems on new Toshiba Libretto

[Linus Torvalds]

On Mon, 11 Jun 2001, Aron Lentsch wrote:
> 
> dump_irq returns the following:
> -----------------------------------------------------------------------
> No PCI interrupt routing table was found.

Hey, you don't have a pirq table, no wonder Linux cannot find the
information.

It's probably an ACPI-only system - rather uncommon, but I bet it will
become fairly common especially in laptops with WindowsME and higher only.

There's a ACPI dump utility in the ACPI tools, that might give people some
idea on what's up. Right now Linux ACPI only does irq routing on ia64, if
I remember correctly, so ACPI per se won't fix the problem, but it would
definitely be the next thing to look at.

Oh, well..

		Linus

Re: IRQ problems on new Toshiba Libretto

[Aron Lentsch]

Hi Jeff,

The latest version of my kernel '.config' file is
at the end of the file:
http://launchers.tripod.com/linux/libretto_logs_n_kernelconfig.txt

> Suggestions:
> * Build kernel with CONFIG_PCI_GOANY config option.

Originally CONFIG_PCI_GOANY was set by default. I tried
to unset and I have set it again as you suggest, but
there seems to be no difference in dmesg and dump_irq.

> * Go through BIOS setup.  Check for and enable "PNP
> OS" setting, and similar settings which reflect an
> automatically assignment of machine resources.

The problem is that there is no documented way to enter
a BIOS setup for this machine. Settings such as the
boot sequence are done from a Windows application :-(
I will try to ask Toshiba if there are any undocumented
possibilities - but it would be a surprise.

Thanks & Cheers!
Aron

Re: IRQ problems on new Toshiba Libretto

[Aron Lentsch]

On Sun, 10 Jun 2001, Linus Torvalds wrote:

> It's probably an ACPI-only system - rather uncommon,
> ...

It seems so - at least APM doesn't work, but ACPI does
- at least to so some extent.

> ... so ACPI per se won't fix the problem, but it
> would definitely be the next thing to look at.

If I understand correctly, I have to wait until someone
is taking up this task? Unfortunately I have now clue
about kernel proramming - well, in fact I am not even a
real programmer (I'm doing rocket engines and reusable
launch vehicle stuff).  Well in this case, whoever is
going to pick-up on this and reading this lines now,
please send you your patches, I would be pleased to do
some testing on the Libretto.

Question 2: Is there any possible workaround for the
moment? Can I e.g. "hardwire" IRQs, e.g. reading them
under Windows and hardcoding them? In this case, there
could be at least a kernel for the Libretto - the
hardware can not be modified anyway.

Thanks,
Aron

Re: IRQ problems on new Toshiba Libretto

[Alan Cox]

> about half of my devices are unusable. I am getting the
> message "PCI: No IRQ known for interrupt pin A of
> device 00:00.0. Please try using pci=biosirq." This
> message is repeated for the following devices:

That sounds like IRQ routing problems. Im sure Linus as the crusoe expert and
the irq routing guru would like to know

Did you try the pci=biosirq boot option btw ?

IRQ problems on new Toshiba Libretto

[Aron Lentsch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi there!

I am trying to install Linux 2.4.4 on the new Toshiba
Libretto, the one with the Crusoe CPU, 1280x600 screen,
1kg (I think it is currently only sold in Japan).

I am having problems with IRQs and the recognition of
system components, which I suspect is the reason, why
about half of my devices are unusable. I am getting the
message "PCI: No IRQ known for interrupt pin A of
device 00:00.0. Please try using pci=biosirq." This
message is repeated for the following devices:

00:00.0 Host bridge: Transmeta Corporation LongRun Northbridge
00:06.0 Multimedia audio controller: Acer Laboratories Inc.
00:0f.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8020
00:10.0 IDE interface: Acer Laboratories Inc. [ALi] M5229 IDE (rev c3)
00:12.0 CardBus bridge: Toshiba ToPIC95 PCI to Cardbus Bridge
01:00.0 Ethernet controller: DECchip 21142/43

I have put the details of /var/log/messages, lspci, /proc/pci, 
pnpdump and the kernel configuration into the file
http://launchers.tripod.com/linux/libretto_logs_n_kernelconfig.txt

I searched the mailing-list archives for this error
message for the last days, applying suggested kernel
parameters and kernel-patches, but without success.
Unfortunately the Libretto seems to have no common
BIOS - didn't find how to enter and change anything
- - all settings are done from Windows :-(

Now I have a number of problems, which I suspect are a
consequence of the above error message:

o   PCMCIA cards are not initialized and return the
above error message (for device 01:00.0) when inserted.
Therefore I can currently not use any PCMCIA device 
(modem, ethernet, CD-Rom !!!) - THIS IS CRITICAL!

o   ACPI output is bogus, showing a remaining battery
capacity, which jumps every few seconds to levels
somewhere between 0 and 100%. The Librtto only supports
ACPI. I am using version acpi-20010518 patched
against kernel 2.4.4, so it should be up-to-date.

o   I can not find my internal (win)modem. Neither
lspci -vvv, pnpdump nor /proc/pci give any evidence
- - but the modem works fine under windows - I mean it is
really there.

o   I fail to initialize the ASLA-sound module for my
ALi-chip (same error message). 

At the moment the core system (CPU, memory, harddisk,
screen and keyboard) is working well. But I would like
to make the whole system work properly - just don't
know what else I can do. I'm not a kernel hacker. Can
anybody help?

THANKS!
Aron

PS:   Because I am not subscribed to the mailing-list,
      could you please CC any comments to me directly.

             _______________________________________
             A  r  o  n    L   E   N   T   S   C   H
             N A L  -  National Aerospace Laboratory
             7-44-1 Jindaiji-Higashi           Chofu
             Tokyo 182-8522                    JAPAN
             phone  +81-422-40-3173    (fax ..-3138)
 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6

iD8DBQE7IjplTHIdV6Tf0iQRAvwCAJ92Es7Ut0MVewlbtwCA/N9uD8EuHgCgvNyU
0z1NKdZOrFEKGxn2VGdnma0=
=4yKd
-----END PGP SIGNATURE-----