linux-kernel - Re: Initializing iwl3945 error

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]

Message-ID: <CAErSpo6XVgzeQiWjXJs6vxdQ5_O7LFG-j4p=4S7rQSyBdq7-SA@mail.gmail.com>
Date:	Mon, 28 May 2012 12:21:34 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Stanislaw Gruszka <sgruszka@...hat.com>
Cc:	Kamil Grzebien <ciptok@...il.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: Initializing iwl3945 error

Sorry this got dropped on the floor for so long.  I don't see anything
wrong with the PCI memory routing information in either the failing or
the working logs.

Kamil, you mentioned: "Driver can't initialize card as all
ioread32/iowrite32 seems to not do their job. All reads finalize with
0xffffffff."

Normally this means we got no response, either because the transaction
didn't reach the device, or the device didn't respond.  Here's the
routing information I see, which looks fine:

  ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
  pci_root PNP0A03:00: host bridge window [mem 0xe0000000-0xf7ffffff]
  pci 0000:00:1c.1: PCI bridge to [bus 0b-0b]
  pci 0000:00:1c.1:   bridge window [mem 0xf1e00000-0xf1efffff]
  pci 0000:0b:00.0: [8086:4222] type 0 class 0x000280
  pci 0000:0b:00.0: reg 10: [mem 0xf1eff000-0xf1efffff]

And we enabled memory space decoding for the device:

  iwl3945 0000:0b:00.0: enabling device (0000 -> 0002)

so it *should* respond.  It's interesting that we didn't have to
enable the device in the working ("noapic") case -- there's no
"enabling device" line in that dmesg log, which means memory decoding
was already enabled when we found it.

You also said "If I access the memory directly, not by mapping, I can
write and read pci memory but driver load fails anyway."  What exactly
does that mean?  I assume you mean that even in the failing case, you
can somehow access that region ([mem 0xf1eff000-0xf1efffff]).  What
mechanism are you using?  ioremap() in the driver?  User-space mmap of
a /sys file?

You said "This issue is reproducible in 100% on my system when I turn
on the machine. It doesn't occur after some work on it."  I wonder if
there's some timing issue with that device coming out of reset or
something.  Does the same problem happen if the driver is statically
linked in vs. loaded as a module after boot?  What if you add a long
delay in the driver probe routine?
--
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/