On Sun, 2009-06-28 at 08:54 +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2009-06-27 at 19:46 +0200, Laszlo Fekete wrote:
> > Hello!
> >
> > Thank you very much, this patch works me too.
> >
> > Maybe this patch will be in the debian kernel someday?
>
> The patch isn't actually correct just yet
On Sat, 2009-06-27 at 19:46 +0200, Laszlo Fekete wrote:
> Hello!
>
> Thank you very much, this patch works me too.
>
> Maybe this patch will be in the debian kernel someday?
The patch isn't actually correct just yet :-) Michael will
be posting a proper one next week. It should be possible to
req
Hello!
Thank you very much, this patch works me too.
Maybe this patch will be in the debian kernel someday?
Thank you: blackluck
Michael Ellerman wrote:
> On Wed, 2009-06-24 at 15:56 +1000, Benjamin Herrenschmidt wrote:
>
>> On Wed, 2009-06-24 at 15:53 +1000, Michael Ellerman wrote:
>>
On Wed, 2009-06-24 at 16:19 +1000, Michael Ellerman wrote:
> sym53c8xx :00:0c.0: enabling device (0140 -> 0143)
> sym0: <896> rev 0x7 at pci :00:0c.0 irq 17
> sym0: No NVRAM, ID 7, Fast-40, SE, parity checking
> _mpic_irq_read: val 0x80480004 shadow 0x80080014
> _mpic_irq_read: val 0x48000
On Wed, 2009-06-24 at 15:56 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2009-06-24 at 15:53 +1000, Michael Ellerman wrote:
> > Doesn't fix my machine :/
> >
> That doesn't make sense ... What if you remove the bit inside the ifdef
> CONFIG_MPIC_BROKEN_REGREAD in _mpic_read() ?
>
> If that make
On Wed, 2009-06-24 at 09:29 +1000, Benjamin Herrenschmidt wrote:
> On Wed, 2009-06-24 at 07:57 +1000, Benjamin Herrenschmidt wrote:
> > > I tried on a POWER3 box I have here "IBM,7044-170" and things work fine
> > > here with current upstream. (I suspect a much smaller machine).
> > >
> > > I will
On Wed, 2009-06-24 at 15:53 +1000, Michael Ellerman wrote:
> Doesn't fix my machine :/
>
That doesn't make sense ... What if you remove the bit inside the ifdef
CONFIG_MPIC_BROKEN_REGREAD in _mpic_read() ?
If that makes a difference, then it would be interesting to add a printk
in there that prin
On Wed, 2009-06-24 at 07:57 +1000, Benjamin Herrenschmidt wrote:
> > I tried on a POWER3 box I have here "IBM,7044-170" and things work fine
> > here with current upstream. (I suspect a much smaller machine).
> >
> > I will really need an actual bisection here... In the meantime, I'll see
> > if I
> I tried on a POWER3 box I have here "IBM,7044-170" and things work fine
> here with current upstream. (I suspect a much smaller machine).
>
> I will really need an actual bisection here... In the meantime, I'll see
> if I can get my hand on one of these machines here.
Ok so I think we may have
On Sun, 2009-06-14 at 11:10 +0200, Guennadi Liakhovetski wrote:
> P610 (and tested it on P630 and P640 too)
Also, send me a tarball of /proc/device-tree please.
Cheers,
Ben.
--
To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact l
On Tue, 2009-06-23 at 11:18 +1000, Benjamin Herrenschmidt wrote:
> On Mon, 2009-06-22 at 11:10 +0200, Laszlo Fekete wrote:
> > Hello!
> >
> > Is there any idea for the solution?
>
> Hard to tell yet. Looks indeed like something is wrong with the
> interrupt controller.
>
> Any chance you can bis
On Mon, 2009-06-22 at 11:10 +0200, Laszlo Fekete wrote:
> Hello!
>
> Is there any idea for the solution?
Hard to tell yet. Looks indeed like something is wrong with the
interrupt controller.
Any chance you can bisect that ? I'll also have a look on my side,
it's definitely not something obvious.
Hello!
Is there any idea for the solution?
Thanks: blackluck
Laszlo Fekete wrote:
Hello!
I'm sorry about the annoyances, but I'd welcome all ideas, suggestions
to see what needs to be done or should be tested for the solution.
Thank you very much!
Guennadi Liakhovetski wrote:
Ok, first at
Hello!
I'm sorry about the annoyances, but I'd welcome all ideas, suggestions
to see what needs to be done or should be tested for the solution.
Thank you very much!
Guennadi Liakhovetski wrote:
Ok, first attempt to forward this to scsi was wrong, as pointed out by
Matthew Wilcox this does i
On Sat, Jun 13, 2009 at 09:49:31PM +0200, Guennadi Liakhovetski wrote:
> Forwarding to the scsi mailing list and driver maintainer.
It's an interrupt problem. Talk to the powerpc people, not me.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we under
15 matches
Mail list logo
