linux-kernel - Transparent bridges, assign_busses and poweroff/tsc problems

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>] [day] [month] [year] [list]

Message-Id: <200702230624.l1N6OI9a017864@turbo.physics.adelaide.edu.au>
Date:	Fri, 23 Feb 2007 16:54:18 +1030 (CST)
From:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>
To:	linux-kernel@...r.kernel.org
Cc:	jwoithe@...sics.adelaide.edu.au (Jonathan Woithe)
Subject: Transparent bridges, assign_busses and poweroff/tsc problems

Hi all

I have previously posted regarding a message about a transparent
bridge message I get when booting my laptop.

  PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
  PCI quirk: region 1180-11bf claimed by ICH6 GPIO
  PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
  PCI: Transparent bridge - 0000:00:1e.0
  PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#07) (try
  'pci=assign-busses')
  Please report the result to linux-kernel to fix this permanently

There doesn't appear to be any ill-effects from this, but a permanent
fix is probably a good thing and so I'm reporting it.

I have however tried "pci=assign-busses" as suggested.  While this does
make the above complaint go away, it introduces two other things, one
a lot more serious.

The first thing I've noticed is that when "pci=assign-busses" has been
specified, I get the following in the dmesg:

  Clocksource tsc unstable (delta = -434140355 ns)

I don't seem to get this if assignbusses hasn't been given.

The second effect of "pci=assign-busses" is that it prevents Linux powering
the laptop off; pressing the power button triggers an ACPI event as it
should and Linux proceeds to close everything down.  However, when it comes
time to actually kill the power the screen goes blank and the backlight
gets turned off, but power remains on until I force it off by holding the
power button down for 4 seconds.

I have verified this with 2.6.18, 2.6.19 and 2.6.20.  Furthermore, the RT
patchset does not change the behaviour.

Something mighty odd seems to be going on here.  Does anyone have any ideas
or suggestions of things to try?

Regards
  jonathan
-
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/