On 04/28/2012 06:23 PM, Benjamin Herrenschmidt wrote:
On Sat, 2012-04-28 at 18:17 -0500, Larry Finger wrote:
Yes, good catch by Andreas. That change does fix the problem.
Ben - Do you want to fix the typos for open/not open with the same
patch?
Sure, if you're going to do a proper patch, by a
On Sat, 2012-04-28 at 18:17 -0500, Larry Finger wrote:
> Yes, good catch by Andreas. That change does fix the problem.
>
> Ben - Do you want to fix the typos for open/not open with the same
> patch?
>
Sure, if you're going to do a proper patch, by all means please fix
those too :-)
Does it fix a
On 04/28/2012 05:48 PM, Benjamin Herrenschmidt wrote:
On Sat, 2012-04-28 at 20:23 +0200, Andreas Schwab wrote:
Larry Finger writes:
I have done a little more debugging. The problem is definitely coming from
drivers/tty/serial/pmac_zilog.c. I am getting ChanB interrupts while open,
which cause
On Sun, 2012-04-29 at 08:41 +1000, Benjamin Herrenschmidt wrote:
> On Sat, 2012-04-28 at 13:09 -0500, Larry Finger wrote:
> > I have done a little more debugging. The problem is definitely coming
> > from
> > drivers/tty/serial/pmac_zilog.c. I am getting ChanB interrupts while
> > open, which
> >
On Sat, 2012-04-28 at 20:23 +0200, Andreas Schwab wrote:
> Larry Finger writes:
>
> > I have done a little more debugging. The problem is definitely coming from
> > drivers/tty/serial/pmac_zilog.c. I am getting ChanB interrupts while open,
> > which causes the following code segment to return IRQ
On Sat, 2012-04-28 at 13:09 -0500, Larry Finger wrote:
> I have done a little more debugging. The problem is definitely coming
> from
> drivers/tty/serial/pmac_zilog.c. I am getting ChanB interrupts while
> open, which
> causes the following code segment to return IRQ_NONE:
>
> if (r3 &
Larry Finger writes:
> I have done a little more debugging. The problem is definitely coming from
> drivers/tty/serial/pmac_zilog.c. I am getting ChanB interrupts while open,
> which causes the following code segment to return IRQ_NONE:
>
>if (r3 & (CHBEXT | CHBTxIP | CHBRxIP)) {
>
On 04/27/2012 07:42 PM, Benjamin Herrenschmidt wrote:
Ok, so you do have a serial port, probably two even :-) One of them is
connected to the infra red transceiver and the other one is probably
connected to the internal modem.
(The modem itself might not use it, some of these machines use an
i2
On Fri, 2012-04-27 at 19:02 -0500, Larry Finger wrote:
> It is a 15" Powerbook G4. I think they call it a Titanium. The console is not
> on
> a serial port. In fact, the reason that I did not think this patch was a
> problem
> is because the serial port does not appear to be connected to an ex
On 04/27/2012 05:26 PM, Benjamin Herrenschmidt wrote:
On Fri, 2012-04-27 at 10:38 -0500, Larry Finger wrote:
Sorry, I was unable to find anything in debugfs to help me learn about interrupt
mapping. The value of CONFIG_NR_IRQS is already 512. I have not tried reducing
it to 128. The setting for
On Fri, 2012-04-27 at 10:38 -0500, Larry Finger wrote:
> Sorry, I was unable to find anything in debugfs to help me learn about
> interrupt
> mapping. The value of CONFIG_NR_IRQS is already 512. I have not tried
> reducing
> it to 128. The setting for CONFIG_SPARSE_IRQ was on, and changing it
On 04/25/2012 04:44 PM, Benjamin Herrenschmidt wrote:
Do we know what the bad interrupt maps to ? Also what is the value of
NR_IRQ and do you have SPARSE_IRQ enabled ? Can you try with the latter
disabled and NR_IRQ set to something large, such as 128 ?
(You may be able to check the interrupt m
On Wed, 2012-04-25 at 10:00 -0500, Larry Finger wrote:
>
> After a few tries, I managed to change over to pata_macio.
> Fortunately, most of
> the system used dev-by-id or UUID, thus most of the process was
> getting all the
> kernel pieces built in.
>
> Unfortunately, the original problem rema
On 04/24/2012 11:11 PM, Benjamin Herrenschmidt wrote:
On Tue, 2012-04-24 at 21:37 -0500, Larry Finger wrote:
Somewhere between v3.2 and v3.3, the kernel in my Powerbook G4
started issuing
the following traceback on bootup:
Does it continue working afterward or not at all ?
Are you using the
On Tue, 2012-04-24 at 21:37 -0500, Larry Finger wrote:
> >> Somewhere between v3.2 and v3.3, the kernel in my Powerbook G4
> started issuing
> >> the following traceback on bootup:
> >
> > Does it continue working afterward or not at all ?
> >
> > Are you using the old IDE driver or the newer libat
On 04/24/2012 06:53 PM, Benjamin Herrenschmidt wrote:
On Tue, 2012-04-24 at 17:58 -0500, Larry Finger wrote:
Hi,
Somewhere between v3.2 and v3.3, the kernel in my Powerbook G4 started issuing
the following traceback on bootup:
Does it continue working afterward or not at all ?
Are you using
On Tue, 2012-04-24 at 17:58 -0500, Larry Finger wrote:
> Hi,
>
> Somewhere between v3.2 and v3.3, the kernel in my Powerbook G4 started
> issuing
> the following traceback on bootup:
Does it continue working afterward or not at all ?
Are you using the old IDE driver or the newer libata based p
Hi,
Somewhere between v3.2 and v3.3, the kernel in my Powerbook G4 started issuing
the following traceback on bootup:
[ 40.264006] irq 23: nobody cared (try booting with the "irqpoll" option)
[ 40.264031] Call Trace:
[ 40.264070] [dfff3f00] [c000984c] show_stack+0x7c/0x194 (unreliable)
[
18 matches
Mail list logo
