headers
Matt Dainty | 6 Sep 2004 15:09
Gravatar

Re: Can't boot releng-current snapshot

Hi,

I'm also getting this warm boot/tlb miss behaviour booting a
cross-built kernel (GENERIC with one small change[1]) on my 680 using
sources from yesterday. I'm using the latest (release 12?) of hpcboot.

If I boot using the serial console instead of the LCD, then the kernel
boots fine, up to the point of asking me for the root device, etc.

Matt

[1] port-hpcsh/26863
--

-- 
"Accept anything. Then explain it your way."
Permalink | Reply | 501 comments |
headers
Valeriy E. Ushakov | 6 Sep 2004 15:23
Picon

Re: Can't boot releng-current snapshot

On Mon, Sep 06, 2004 at 14:09:07 +0100, Matt Dainty wrote:

> I'm also getting this warm boot/tlb miss behaviour booting a
> cross-built kernel (GENERIC with one small change[1]) on my 680 using
> sources from yesterday. I'm using the latest (release 12?) of hpcboot.
> 
> If I boot using the serial console instead of the LCD, then the kernel
> boots fine, up to the point of asking me for the root device, etc.

Also with a gzipped kernel?  If yes - does the uncompressed one works?
A recentish kernel works ok for me.

> [1] port-hpcsh/26863

I'll handle this one.

SY, Uwe
--

-- 
uwe <at> ptc.spbu.ru                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen
Permalink | Reply | 501 comments |
headers
Matt Dainty | 6 Sep 2004 20:24
Gravatar

Re: Can't boot releng-current snapshot

On Mon, 2004-09-06 at 14:23, Valeriy E. Ushakov wrote:
> On Mon, Sep 06, 2004 at 14:09:07 +0100, Matt Dainty wrote:
> 
> > I'm also getting this warm boot/tlb miss behaviour booting a
> > cross-built kernel (GENERIC with one small change[1]) on my 680 using
> > sources from yesterday. I'm using the latest (release 12?) of hpcboot.
> > 
> > If I boot using the serial console instead of the LCD, then the kernel
> > boots fine, up to the point of asking me for the root device, etc.
> 
> Also with a gzipped kernel?  If yes - does the uncompressed one works?
> A recentish kernel works ok for me.

Yup, just tested with an uncompressed version of my kernel and it boots
no problem.

Matt
Permalink | Reply | 0 comments |
headers
Matt Dainty | 12 Sep 2004 23:32
Gravatar

screenblank doesn't unblank

Is screenblank known to work okay? It seems to blank and power off the
LCD correctly on my Jornada 680, but I can't get it to unblank again
without stopping screenblank manually. I've tried running with no
additional flags, and also specifying the various /dev/wskbd* devices
with '-i', but the screen stays powered off.

Am I using the right keyboard device? Or is the wakeup code missing
somehow?

Cheers

Matt
Permalink | Reply | 5 comments |
headers
Valeriy E. Ushakov | 13 Sep 2004 00:26
Picon

Re: screenblank doesn't unblank

On Sun, Sep 12, 2004 at 22:32:43 +0100, Matt Dainty wrote:

> Is screenblank known to work okay? It seems to blank and power off the
> LCD correctly on my Jornada 680, but I can't get it to unblank again
> without stopping screenblank manually. I've tried running with no
> additional flags, and also specifying the various /dev/wskbd* devices
> with '-i', but the screen stays powered off.
> 
> Am I using the right keyboard device? Or is the wakeup code missing
> somehow?

If doesn't work if you mount your fs with nodevmtime, which I suppose
you do to avoid extra CF wear.

SY, Uwe
--

-- 
uwe <at> ptc.spbu.ru                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen
Permalink | Reply | 4 comments |
headers
Matt Dainty | 13 Sep 2004 00:35
Gravatar

Re: screenblank doesn't unblank

On Sun, 2004-09-12 at 23:26, Valeriy E. Ushakov wrote:
> On Sun, Sep 12, 2004 at 22:32:43 +0100, Matt Dainty wrote:
> 
> > Is screenblank known to work okay? It seems to blank and power off the
> > LCD correctly on my Jornada 680, but I can't get it to unblank again
> > without stopping screenblank manually. I've tried running with no
> > additional flags, and also specifying the various /dev/wskbd* devices
> > with '-i', but the screen stays powered off.
> > 
> > Am I using the right keyboard device? Or is the wakeup code missing
> > somehow?
> 
> If doesn't work if you mount your fs with nodevmtime, which I suppose
> you do to avoid extra CF wear.

I'm currently still running entirely from NFS, would that be causing it
somehow? Although I'm not explicitly using any extra mount options...

Matt
Permalink | Reply | 3 comments |
headers
Valeriy E. Ushakov | 13 Sep 2004 00:41
Picon

Re: screenblank doesn't unblank

On Sun, Sep 12, 2004 at 23:35:43 +0100, Matt Dainty wrote:

> > If doesn't work if you mount your fs with nodevmtime, which I suppose
> > you do to avoid extra CF wear.
> 
> I'm currently still running entirely from NFS, would that be causing it
> somehow? Although I'm not explicitly using any extra mount options...

Hmm.  Strange.  It used to work for me last time I ran off of NFS.

SY, Uwe
--

-- 
uwe <at> ptc.spbu.ru                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen
Permalink | Reply | 2 comments |
headers
Valeriy E. Ushakov | 13 Sep 2004 21:55
Picon

Re: screenblank doesn't unblank

On Mon, Sep 13, 2004 at 02:41:03 +0400, Valeriy E. Ushakov wrote:

> On Sun, Sep 12, 2004 at 23:35:43 +0100, Matt Dainty wrote:
> 
> > > If doesn't work if you mount your fs with nodevmtime, which I suppose
> > > you do to avoid extra CF wear.
> > 
> > I'm currently still running entirely from NFS, would that be causing it
> > somehow? Although I'm not explicitly using any extra mount options...
> 
> Hmm.  Strange.  It used to work for me last time I ran off of NFS.

Ok, now I have doubts in my sanity.  C.f. PRs 11905, 23182.

SY, Uwe
--

-- 
uwe <at> ptc.spbu.ru                         |       Zu Grunde kommen
http://www.ptc.spbu.ru/~uwe/            |       Ist zu Grunde gehen
Permalink | Reply | 1 comment |
headers
Matt Dainty | 14 Sep 2004 02:36
Gravatar

Re: screenblank doesn't unblank

On Mon, 2004-09-13 at 20:55, Valeriy E. Ushakov wrote:
> On Mon, Sep 13, 2004 at 02:41:03 +0400, Valeriy E. Ushakov wrote:
> 
> > On Sun, Sep 12, 2004 at 23:35:43 +0100, Matt Dainty wrote:
> > 
> > > > If doesn't work if you mount your fs with nodevmtime, which I suppose
> > > > you do to avoid extra CF wear.
> > > 
> > > I'm currently still running entirely from NFS, would that be causing it
> > > somehow? Although I'm not explicitly using any extra mount options...
> > 
> > Hmm.  Strange.  It used to work for me last time I ran off of NFS.
> 
> Ok, now I have doubts in my sanity.  C.f. PRs 11905, 23182.

Hmm, PR 11905 looks like it fits the bill as far as I'm concerned.

Matt
Permalink | Reply | 0 comments |
headers
Matt Dainty | 14 Sep 2004 12:13
Gravatar

Segfault in libfontconfig

(cc'd to port-dreamcast as well)

I'm getting a repeatable sigsegv in libfontconfig when I launch either
xclock or gtk-demo:

Backtrace from xclock:

(gdb) bt
#0  0x2046f888 in FcValueSave () from /usr/X11R6/lib/libfontconfig.so.1
#1  0x2047060a in FcPatternAddWithBinding ()
   from /usr/X11R6/lib/libfontconfig.so.1
#2  0x20470710 in FcPatternAdd () from /usr/X11R6/lib/libfontconfig.so.1
#3  0x20470880 in FcPatternAddString () from
/usr/X11R6/lib/libfontconfig.so.1
#4  0x204713b4 in FcNameParse () from /usr/X11R6/lib/libfontconfig.so.1
#5  0x20475678 in FcDirSave () from /usr/X11R6/lib/libfontconfig.so.1

gtk-demo backtrace is more lengthy, but FcValueSave() is the culprit in
both cases.

I've found these two pages:

http://www2.starcat.ne.jp/~yaoshi/diary/?200407b&to=200407200
http://www2.starcat.ne.jp/~yaoshi/diary/?0217

Which contain the same backtrace, but with the NetBSD/Dreamcast port. I
can't read anything else on the page, but it suggests to me that
this is perhaps a SuperH issue rather than anything hpcsh-specific.

I can sort of make out that the Dreamcast X11 was cross-compiled. My X11
(Continue reading)

Permalink | Reply | 0 comments |

Gmane