|To:||Manuel Lauss <firstname.lastname@example.org>|
|Subject:||Re: octeon: oops/panic with CONFIG_SERIO_I8042=y|
|From:||Sergei Shtylyov <email@example.com>|
|Date:||Thu, 18 Jul 2013 23:39:46 +0400|
|Cc:||Aaro Koskinen <firstname.lastname@example.org>, David Daney <email@example.com>, Faidon Liambotis <firstname.lastname@example.org>, Linux-MIPS <email@example.com>|
|List-software:||Ecartis version 1.0.0|
|References:||<20130718122556.GA19040@tty.gr> <51E817C6.firstname.lastname@example.org> <20130718180339.GH14385@blackmetal.musicnaut.iki.fi> <CAOLZvyE-KppwVkb4J8V5k3FHuHKUiQycQiXft5AijPxtSdcL-A@mail.gmail.com>|
|User-agent:||Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130620 Thunderbird/17.0.7|
Hello. On 07/18/2013 11:34 PM, Manuel Lauss wrote:
My goal is to run a standard Debian kernel and its octeon variant on the Ubiquity EdgeRouter Lite. The ERLite needs a couple of patches to boot and work (octeon-ethernet patch, octeon-usb driver) but these are already merged 3.11 and I'll file Debian bugs to enable those settings appropriately.
However, when trying to boot a standard Debian kernel in the ERLite I get a 7s delay followed by an oops for a Data bus error on i8042_flush() and ending up with a panic. It looks like the kernel is built with CONFIG_SERIO_I8042=y. The Octeon machine Debian owns prints "i8042: No controller found" but works nevertheless. This isn't the case with the ERLite; I tried 3.2 & 3.10 and got the same oops which went away as soon as I disabled CONFIG_SERIO_I8042.
Are there even any octeon machines with i8042 anyway? Should I request for the setting to be disabled irrespective of this bug?
Yes. There is a rare board called NAC38 that was produced by ASUS in a 1U chassis. I don't think it is important to support this, so the best thing seems to be not to enable SERIO_I8042
I think the real bug here is that IO space does not get properly initialized on Octeon when there is no PCI? So any drivers trying to probe IO space will produce some interesting results.
This is not specific to Octeon, I've seen it on Alchemy as well. A lot of drivers, coming from x86, simply assume that x86-Port-IO space is always available without having to map it first. I'd say it's a bug in the various drivers.
Drivers don't have to map I/O space in any way, it's a complete nonsense.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: octeon: oops/panic with CONFIG_SERIO_I8042=y, Manuel Lauss|
|Next by Date:||Re: [PATCH] mips/ftrace: Fix function tracing return address to match, Steven Rostedt|
|Previous by Thread:||Re: octeon: oops/panic with CONFIG_SERIO_I8042=y, Manuel Lauss|
|Next by Thread:||Re: octeon: oops/panic with CONFIG_SERIO_I8042=y, Manuel Lauss|
|Indexes:||[Date] [Thread] [Top] [All Lists]|