linux-kernel - Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 7 Jun 2007 12:34:47 -0600
From:	Bjorn Helgaas <bjorn.helgaas@...com>
To:	Andrey Borzenkov <arvidjaar@...l.ru>
Cc:	"Linus Walleij (LD/EAB)" <linus.walleij@...csson.com>,
	"Samuel Ortiz" <samuel@...tiz.org>, linux-kernel@...r.kernel.org,
	"Michal Piotrowski" <michal.k.k.piotrowski@...il.com>,
	ambx1@....rr.com
Subject: Re: 2.6.22-rc: regression: no irda0 interface (2.6.21 was OK), smsc does not find chip

On Wednesday 06 June 2007 02:45:01 pm Andrey Borzenkov wrote:
> I am beginning to doubt whether drier 
> works on my system at all (i.e. before PnP change); have to find time to 
> test.

In 2.6.21, smsc-ircc2 at least found the device.  So we definitely have
a problem because in 2.6.22-rc, we don't find the device.

What laptop do you have?  Maybe I can find one to play with.

I think Windows always calls _SRS, even if it doesn't need to change
the current resource settings.  Linux doesn't do that, and my HP nw8240
firmware has a bug that leaves the IR device partly-enabled until _SRS
is called.  Maybe yours has a similar bug.

Can you set CONFIG_ACPI_DEBUG=y, make it so smsc-ircc2 isn't loaded
automatically, and try this (along with my previous patch to swap
FIR and SIR):

  # dmesg -n 8
  # echo 0x200 > /sys/module/acpi/parameters/debug_level
  # echo disable > /sys/bus/pnp/devices/00:0a/resources
  # echo activate > /sys/bus/pnp/devices/00:0a/resources
  # modprobe smsc-ircc2

If you try this, can you collect the whole dmesg log?

It's also possible that some other driver like i2c is messing with
the ISA/LPC bridge configuration and breaking the IR device config.
Your lspnp output doesn't show any other ISA devices down there,
but I know i2c likes to poke around and discover things that kinda,
sorta work, but the BIOS didn't expose.

Bjorn
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/