mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Carlo E. Prelz" <fluido@fluido.as>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
Date: Sun, 22 Jan 2006 09:30:03 +0100	[thread overview]
Message-ID: <20060122083003.GB1315@epio.fluido.as> (raw)
In-Reply-To: <20060121235546.68f50bd5.akpm@osdl.org>

	Subject: Re: ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15 rc1
	Date: sab 21 gen 06 11:55:46 -0800

Quoting Andrew Morton (akpm@osdl.org):

> > and 1002:4373 is the USB2 (EHCI) controller. I attach the output of
> > lspci -vx. Even with 2.6.14.6, I have problems with USB. It did not
> > work at all, then I downloaded the latest bios, and now, right after
> > boot, usb works OK.
> 
> OK, so it sounds like quirk_usb_disable_ehci() caused your machine to hang
> with the old BIOS.  That's fairly bad behaviour from the kernel, even
> though the BIOS presumably had some problems.

It did not hang. When inserting USB disks, I got messages like:

ehci_hcd 0000:00:13.2: Unlink after no-IRQ?  Controller is probably using the wrong IRQ.
usb 1-1: device not accepting address 2, error -110

and the usb-storage module was not loaded. But the kernel went on
working. After upgrading the BIOS, with the same kernel, the USB disk
was recognized. But I now notice that the log file, with both old and
new BIOS, contains these lines:

ehci_hcd 0000:00:13.2: BIOS handoff failed (160, 01010001)
ehci_hcd 0000:00:13.2: continuing after BIOS bug...
ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:13.2: irq 18, io mem 0xfe02b000
ehci_hcd 0000:00:13.2: USB 2.0 initialized, EHCI 1.00, driver 10 Dec 2004

(only, the IRQ number changed from 10 to 18 after changing BIOS)

> Can you please gather some more details on this and prepare a new report? 
> The full demsg output, machine description, etc.  It might be best to do
> this via a new bugzilla.kernel.org record so we know where to find
> it.

I will try that. I saw on apic.c that APIC error 40 should mean
'received illegal vector,' but I have no clue about how to interpret
this. 

I will now play a bit with BIOS USB parameters.

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-01-22  8:30 UTC|newest]

Thread overview: 22+ 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 [this message]
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
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

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=20060122083003.GB1315@epio.fluido.as \
    --to=fluido@fluido.as \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®