Am Donnerstag, 15. November 2012, 17:58:35 schrieb Grant Likely:
> Anyway, here is a real patch.
Thanks a lot, Grant!
Your patch improves the situation significantly. However, it is still not
entirely fixed:
irq: irq-93==>hwirq-0x5d mapping failed: -22
There are a lot less error messages than be
On Thu, 25 Oct 2012 21:33:41 +0200, Dennis Schridde wrote:
> Hello everyone!
>
> Am Freitag, 19. Oktober 2012, 09:04:08 schrieb Dennis Schridde:
> > Am Freitag, 19. Oktober 2012, 00:17:55 schrieb Grant Likely:
> > > What does the boot log look like with the attached patch? (compiled
> > > only, I
Hello again!
Am Donnerstag, 25. Oktober 2012, 21:33:41 schrieb Dennis Schridde:
> Am Freitag, 19. Oktober 2012, 09:04:08 schrieb Dennis Schridde:
> > Am Freitag, 19. Oktober 2012, 00:17:55 schrieb Grant Likely:
> > > What does the boot log look like with the attached patch? (compiled
> > > only, I
Hello everyone!
Am Freitag, 19. Oktober 2012, 09:04:08 schrieb Dennis Schridde:
> Am Freitag, 19. Oktober 2012, 00:17:55 schrieb Grant Likely:
> > What does the boot log look like with the attached patch? (compiled
> > only, I haven't booted with it)
>
> Please find the log attached.
Have you fou
Am Freitag, 19. Oktober 2012, 00:17:55 schrieb Grant Likely:
> What does the boot log look like with the attached patch? (compiled
> only, I haven't booted with it)
Please find the log attached.
--Dennis
blade03-tmux.log.xz
Description: application/xz
signature.asc
Description: This is a digita
On Thu, 2012-10-18 at 23:44 +0100, Grant Likely wrote:
> Also, it should be noted that the irq does actually get set up by
> irqdomain.c, but because everything above 0x1ff is larger than the
> lookup table, it complains. The new code complains loudly (as you
> discovered) if someone tries to use a
On Thu, Oct 18, 2012 at 11:59 PM, Grant Likely
wrote:
> On Thu, Oct 18, 2012 at 11:44 PM, Grant Likely
> wrote:
>> On Thu, Oct 18, 2012 at 10:59 PM, Dennis Schridde wrote:
>>> Am Donnerstag, 18. Oktober 2012, 22:32:55 schrieb Grant Likely:
Unfortunately the debug messages don't show up in t
On Thu, Oct 18, 2012 at 11:44 PM, Grant Likely
wrote:
> On Thu, Oct 18, 2012 at 10:59 PM, Dennis Schridde wrote:
>> Am Donnerstag, 18. Oktober 2012, 22:32:55 schrieb Grant Likely:
>>> Unfortunately the debug messages don't show up in the console log by
>>> default. Can you either send the output
On Thu, Oct 18, 2012 at 10:59 PM, Dennis Schridde wrote:
> Am Donnerstag, 18. Oktober 2012, 22:32:55 schrieb Grant Likely:
>> Unfortunately the debug messages don't show up in the console log by
>> default. Can you either send the output of 'dmesg' after booting, or
>> add "loglevel=8" to the kern
