mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carlo E. Prelz" <fluido@fluido.as>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
	Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
Date: Mon, 6 Feb 2006 09:02:51 +0100	[thread overview]
Message-ID: <20060206080251.GA23014@epio.fluido.as> (raw)
In-Reply-To: <200602051145.22933.david-b@pacbell.net>

	Subject: Re: [linux-usb-devel] Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
	Date: dom 05 feb 06 11:45:22 -0800

Quoting David Brownell (david-b@pacbell.net):

> Interesting ... feels like a BIOS problem.  If you want to experiment,
> there's a right bracket -- "}" -- immediately before that.  Try moving
> it right after that write, so that write_config_byte is covered by the
> preceding "if LEGSUP_BIOS" test; or copying the much later "disable SMI"
> clause into an "else" for that "if".

The first one would be useless - I inserted lots of printouts to find
out where the freeze took place, and I know that the 
EHCI_USBLEGSUP_BIOS flag is on (cap is 0x10001). The value remains the
same after the 'spin till it hands it over' loop - so that this
printout appears:

0000:00:13.2 EHCI: BIOS handoff failed (BIOS bug ?)

About the second thing you suggest: do you refer to this call?

			/* just in case, always disable EHCI SMIs */
			pci_write_config_dword(pdev,
					offset + EHCI_USBLEGCTLSTS,
					0);

In my machine, the write takes place without apparent ill effects. If
I add it as an else clause to the "if LEGSUP_BIOS" test, it won't
execute, because the EHCI_USBLEGSUP_BIOS flag is on.

In case you need it: hcc_params is 0xa012. 

Carlo

-- 
  *         Se la Strada e la sua Virtu' non fossero state messe da parte,
* K * Carlo E. Prelz - fluido@fluido.as             che bisogno ci sarebbe
  *               di parlare tanto di amore e di rettitudine? (Chuang-Tzu)

  reply	other threads:[~2006-02-06  8:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-20 12:32 Carlo E. Prelz
2006-01-21  9:09 ` Andrew Morton
2006-01-21 12:57   ` Carlo E. Prelz
2006-01-21 20:58     ` Andrew Morton
2006-01-21 21:28       ` Erwin Rol
2006-01-21 22:04         ` Dave Jones
2006-01-22  4:14           ` Kurt Wall
2006-01-22  7:40       ` Carlo E. Prelz
2006-01-22  7:55         ` Andrew Morton
2006-01-22  8:30           ` Carlo E. Prelz
2006-01-22 11:11           ` Carlo E. Prelz
2006-02-05 10:33             ` Carlo E. Prelz
2006-02-05 19:45               ` [linux-usb-devel] " David Brownell
2006-02-06  8:02                 ` Carlo E. Prelz [this message]
2006-02-06 16:24                   ` David Brownell
2006-02-06 16:50                     ` Carlo E. Prelz
2006-02-06 17:31                       ` David Brownell
2006-02-06 17:45                         ` Carlo E. Prelz
2006-01-23 19:01           ` David Brownell
2006-01-23 21:47             ` Carlo E. Prelz
2006-01-24  4:42             ` Greg KH
2006-01-24 15:15               ` David Brownell
2006-02-07  2:03 Aleksey Gorelov
2006-02-07 22:05 ` David Brownell
2006-02-08  1:04   ` Aleksey V Gorelov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060206080251.GA23014@epio.fluido.as \
    --to=fluido@fluido.as \
    --cc=akpm@osdl.org \
    --cc=david-b@pacbell.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome