Linux PARISC architecture development
 help / color / mirror / Atom feed
* [parisc-linux] check_ivt panic / binutils
@ 2006-10-03  1:09 Jeff Bailey
  2006-10-03  2:11 ` John David Anglin
  0 siblings, 1 reply; 5+ messages in thread
From: Jeff Bailey @ 2006-10-03  1:09 UTC (permalink / raw)
  To: parisc-linux

I bisected the binutils CVS until I found the failure point.  It seems
that with 2006-04-30 I don't get the check_ivt failure (although the
kernel does die immediately after e100 is initialised), but at
2006-05-01, I get the check_ivt failure.

What's *really* annoying is that the only changes between the two appear
to be MIPS stuff.  http://people.ubuntu.com/~jbailey/binutils.patch or
"cvs diff -D 2006-04-30 -D 2006-05-01" to see what I mean.

My kernel config is at http://people.ubuntu.com/~jbailey/a500_config if
it's of any use.  I'm not sure what to look at next.

Tks,
Jeff Bailey

-- 
Although when you're in the situation that RMS is telling you that
you're being too ideological about freedom, maybe, just maybe, it's
true.
- Matthew Wilcox

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] check_ivt panic / binutils
  2006-10-03  1:09 [parisc-linux] check_ivt panic / binutils Jeff Bailey
@ 2006-10-03  2:11 ` John David Anglin
  2006-10-03  2:17   ` Jeff Bailey
  0 siblings, 1 reply; 5+ messages in thread
From: John David Anglin @ 2006-10-03  2:11 UTC (permalink / raw)
  To: Jeff Bailey; +Cc: parisc-linux

> I bisected the binutils CVS until I found the failure point.  It seems
> that with 2006-04-30 I don't get the check_ivt failure (although the
> kernel does die immediately after e100 is initialised), but at
> 2006-05-01, I get the check_ivt failure.

It's not at all obvious why you think this is a binutils bug.

>  IIR: 0e60109c    ISR: 0000000000000000  IOR: 0000000100000000

$ disasm 0x0e60109c
   0:   0e 60 10 9c     ldw 0(r19),ret0

> r16-19  00000000f00003b0 00000000f000024c 00000000f0002b4c 0000000100000000

The r19 value is the problem.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] check_ivt panic / binutils
  2006-10-03  2:11 ` John David Anglin
@ 2006-10-03  2:17   ` Jeff Bailey
  2006-10-03  2:50     ` Matthew Wilcox
  2006-10-03  2:52     ` John David Anglin
  0 siblings, 2 replies; 5+ messages in thread
From: Jeff Bailey @ 2006-10-03  2:17 UTC (permalink / raw)
  To: John David Anglin; +Cc: parisc-linux


[-- Attachment #1.1: Type: text/plain, Size: 1438 bytes --]

Le lundi 02 octobre 2006 à 22:11 -0400, John David Anglin a écrit :
> > I bisected the binutils CVS until I found the failure point.  It seems
> > that with 2006-04-30 I don't get the check_ivt failure (although the
> > kernel does die immediately after e100 is initialised), but at
> > 2006-05-01, I get the check_ivt failure.
> 
> It's not at all obvious why you think this is a binutils bug.

Sorry, the first part of the conversation happened on IRC, my bad.

I was trying to figure out why I was seeing a problem that Joel had
reported before and no-one else was.  Kyle got me to try a sid chroot,
and it didn't happen there.  Eventually I narrowed down the difference
between a working kernel and a non-working one was whether I was using a
bleeding edge CVS snapshot, or whether I was using the released
binutils-2.17 package.

I'm not claiming I know where the bug is, but I wanted to know what the
change was that happened between a bootable kernel and a non-bootable
kernel.

> >  IIR: 0e60109c    ISR: 0000000000000000  IOR: 0000000100000000
> 
> $ disasm 0x0e60109c
>    0:   0e 60 10 9c     ldw 0(r19),ret0
> 
> > r16-19  00000000f00003b0 00000000f000024c 00000000f0002b4c 0000000100000000
> 
> The r19 value is the problem.

-- 
Although when you're in the situation that RMS is telling you that
you're being too ideological about freedom, maybe, just maybe, it's
true.
- Matthew Wilcox

[-- Attachment #1.2: Ceci est une partie de message numériquement signée --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 169 bytes --]

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] check_ivt panic / binutils
  2006-10-03  2:17   ` Jeff Bailey
@ 2006-10-03  2:50     ` Matthew Wilcox
  2006-10-03  2:52     ` John David Anglin
  1 sibling, 0 replies; 5+ messages in thread
From: Matthew Wilcox @ 2006-10-03  2:50 UTC (permalink / raw)
  To: Jeff Bailey; +Cc: John David Anglin, parisc-linux

On Mon, Oct 02, 2006 at 10:17:19PM -0400, Jeff Bailey wrote:
> I'm not claiming I know where the bug is, but I wanted to know what the
> change was that happened between a bootable kernel and a non-bootable
> kernel.

I suppose the obvious thing to do is to objdump -dr each kernel and then
diff the two.  That'll tell you if it's a heisenbug or if there's
actually any difference.

_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [parisc-linux] check_ivt panic / binutils
  2006-10-03  2:17   ` Jeff Bailey
  2006-10-03  2:50     ` Matthew Wilcox
@ 2006-10-03  2:52     ` John David Anglin
  1 sibling, 0 replies; 5+ messages in thread
From: John David Anglin @ 2006-10-03  2:52 UTC (permalink / raw)
  To: Jeff Bailey; +Cc: parisc-linux

> > > I bisected the binutils CVS until I found the failure point.  It seems
> > > that with 2006-04-30 I don't get the check_ivt failure (although the
> > > kernel does die immediately after e100 is initialised), but at
> > > 2006-05-01, I get the check_ivt failure.
> >=20
> > It's not at all obvious why you think this is a binutils bug.
> 
> Sorry, the first part of the conversation happened on IRC, my bad.
> 
> I was trying to figure out why I was seeing a problem that Joel had
> reported before and no-one else was.  Kyle got me to try a sid chroot,
> and it didn't happen there.  Eventually I narrowed down the difference
> between a working kernel and a non-working one was whether I was using a
> bleeding edge CVS snapshot, or whether I was using the released
> binutils-2.17 package.

If you think it's a binutils issue, then cmp the two kernels
or modules and see if they differ.  Generate an assembler printout
for the code that caused the panic.  This would show if there's a
relocation issue with the instruction that causes the panic.

There haven't been many changes to the hppa binutils port in recent
months.  The TLS stuff went in after you say the failure started.

Dave
-- 
J. David Anglin                                  dave.anglin@nrc-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2006-10-03  2:52 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-10-03  1:09 [parisc-linux] check_ivt panic / binutils Jeff Bailey
2006-10-03  2:11 ` John David Anglin
2006-10-03  2:17   ` Jeff Bailey
2006-10-03  2:50     ` Matthew Wilcox
2006-10-03  2:52     ` John David Anglin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox