mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jon Nelson" <jnelson-linux-raid@jamponi.net>
To: "Robert Hancock" <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)
Date: Sat, 5 Jul 2008 18:50:58 -0500	[thread overview]
Message-ID: <cccedfc60807051650o32e72887gc732587d0911e962@mail.gmail.com> (raw)
In-Reply-To: <487001A4.1060406@shaw.ca>

On Sat, Jul 5, 2008 at 6:20 PM, Robert Hancock <hancockr@shaw.ca> wrote:
> Jon Nelson wrote:
>>
>> On Sat, Jul 5, 2008 at 2:04 PM, Robert Hancock <hancockr@shaw.ca> wrote:
>>>
>>> Jon Nelson wrote:
>>>>
>>>> Where should APIC errors be posted?
>>>> My EPoX MF570-SLI *will not boot* without noapic or nolapic.
>>>
>>> Post on linux-kernel about that one, with the dmesg from noapic mode and
>>> whatever info you can gather from when it won't boot. You might want to
>>> also
>>> test with 2.6.26-rc8 to see if the problem has already been fixed there.
>>
>> Here is the boot log from booting my EPoX MF570SLI in nolapic mode.
>> When I boot without nolapic or noapic I get as far as
>>
>> io scheduler cfq registered (default)
>>
>> I can't boot to serial right now.
>
> You are getting this as the next line after that:
>
> 0000:00:02.1 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
>
> You might want to try upgrading your BIOS, it seems like the BIOS is not
> letting go of the USB controller when Linux tries to take over. I don't know
> if that's related to the problem though.
>
> If that doesn't work, I'd try a newer kernel version.


I completely disabled USB in the BIOS. I get a bit further, but still,
a hang. See my other msgs.


-- 
Jon

  reply	other threads:[~2008-07-05 23:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.u8J+BqAcxU1mg8ob9pMBJaAHBPo@ifi.uio.no>
2008-07-05 18:38 ` Robert Hancock
2008-07-05 19:28   ` Justin Piszcz
2008-07-05 23:22     ` Robert Hancock
2008-07-05 23:24       ` Justin Piszcz
2008-07-06 10:31         ` Justin Piszcz
2008-07-06 12:13           ` Justin Piszcz
2008-07-06 12:42             ` Justin Piszcz
2008-07-06 19:51               ` Justin Piszcz
2008-07-07  9:45         ` Mattias Wadenstein
2008-07-07  9:57           ` Justin Piszcz
     [not found]   ` <cccedfc60807051154m7d0a8b44h3294ec29fe07d35a@mail.gmail.com>
     [not found]     ` <486FC5D2.80600@shaw.ca>
2008-07-05 22:53       ` Jon Nelson
2008-07-05 23:20         ` Robert Hancock
2008-07-05 23:50           ` Jon Nelson [this message]
2008-07-05 23:49         ` Jon Nelson
2008-07-05 16:57 Justin Piszcz
2008-07-05 17:35 ` Jon Nelson
2008-07-05 17:35 ` Jon Nelson
2008-07-07 15:04 ` Gerhard Wiesinger
2008-07-07 15:08   ` Gerhard Wiesinger
2008-07-07 16:04     ` Justin Piszcz
2008-07-08  6:24       ` Gerhard Wiesinger
2008-07-08  6:59         ` Gerhard Wiesinger
2008-07-08  8:35           ` Justin Piszcz
2008-07-08 10:31             ` Gerhard Wiesinger
2008-07-08  8:34         ` Justin Piszcz
2008-07-08 10:33           ` Gerhard Wiesinger
2008-07-08 13:15             ` Justin Piszcz
2008-07-09  5:37               ` Gerhard Wiesinger
2008-07-10  1:27                 ` Henrique de Moraes Holschuh
2008-07-12  8:29                 ` Gerhard Wiesinger

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=cccedfc60807051650o32e72887gc732587d0911e962@mail.gmail.com \
    --to=jnelson-linux-raid@jamponi.net \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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®