All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: blackluck@ktk.bme.hu
Cc: linuxppc-dev@ozlabs.org, debian-powerpc@lists.debian.org,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: sym scsi driver problem with 2.6.26 or newer debian kernel on p610 (fwd)
Date: Tue, 23 Jun 2009 11:18:10 +1000	[thread overview]
Message-ID: <1245719890.4017.26.camel@pasglop> (raw)
In-Reply-To: <4A3F4A77.6070704@ktk.bme.hu>

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.

Cheers,
Ben.

> 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 attempt to forward this to scsi was wrong, as pointed out 
> >> by Matthew Wilcox this does indeed look like an interrupt problem - 
> >> no interrupts drom SCSI, IDE, keyboar. Might be a known problem, I 
> >> guess. In any case, I think, the OP would be grateful for any hints.
> >>
> >> Thanks
> >> Guennadi
> >> ---
> >> Guennadi Liakhovetski, Ph.D.
> >> Freelance Open-Source Software Developer
> >> http://www.open-technology.de/
> >>
> >> ---------- Forwarded message ----------
> >> Date: Sat, 13 Jun 2009 16:22:07 +0200
> >> From: Laszlo Fekete <blackluck@ktk.bme.hu>
> >> To: debian-powerpc@lists.debian.org
> >> Subject: sym scsi driver problem with 2.6.26 or newer debian kernel 
> >> on p610
> >> Resent-Date: Sat, 13 Jun 2009 14:29:55 +0000 (UTC)
> >> Resent-From: debian-powerpc@lists.debian.org
> >>
> >> This is a multi-part message in MIME format.
> >> ------------------------------------------------------------------------
> >>
> >> Hello!
> >>
> >>
> >>
> >>
> >>
> >> Pls help me with sym scsi driver problem.
> >>
> >>
> >>
> >> I have Ibm P610 (and tested it on P630 and P640 too), installed debian
> >>
> >> etch and upgraded to lenny.
> >>
> >>
> >>
> >> But with 2.6.26 or newer kernel it's not booting, it's hang on sym scsi
> >>
> >> bus scan.
> >>
> >>
> >>
> >>
> >>
> >> Whats the problem with it, or how can I fix this?
> >>
> >>
> >>
> >>
> >>
> >> I attach the output from minicom with 2.6.29, 2.6.26, and the working
> >>
> >> 2.6.24 kernel booting.
> >>
> >>
> >>
> >>
> >>
> >> Thank you very much!
> >>
> >>
> >>   
> >
> >
> 
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev

  reply	other threads:[~2009-06-23  1:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14  9:10 sym scsi driver problem with 2.6.26 or newer debian kernel on p610 (fwd) Guennadi Liakhovetski
2009-06-17  9:33 ` Laszlo Fekete
2009-06-22  9:10   ` Laszlo Fekete
2009-06-23  1:18     ` Benjamin Herrenschmidt [this message]
2009-06-23  2:30       ` Benjamin Herrenschmidt
2009-06-23 21:57         ` Benjamin Herrenschmidt
2009-06-23 23:29           ` Benjamin Herrenschmidt
2009-06-24  5:53             ` Michael Ellerman
2009-06-24  5:56               ` Benjamin Herrenschmidt
2009-06-24  6:19                 ` Michael Ellerman
2009-06-24  9:31                   ` Benjamin Herrenschmidt
2009-06-27 17:46                   ` Laszlo Fekete
2009-06-27 22:54                     ` Benjamin Herrenschmidt
2009-07-06  9:05                       ` Michael Ellerman
2009-06-23  2:31 ` Benjamin Herrenschmidt
  -- strict thread matches above, loose matches on Subject: below --
2009-06-13 19:49 Guennadi Liakhovetski
2009-06-14  1:50 ` Matthew Wilcox

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=1245719890.4017.26.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=blackluck@ktk.bme.hu \
    --cc=debian-powerpc@lists.debian.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.