c.cheetham | 1 Jul 2009 01:15
Picon
Favicon

xsrc/41656: Followup: 41644 - Favourable workaround discovered, this is a non-issue really.

>Number:         41656
>Category:       xsrc
>Synopsis:       Followup: 41644 - Favourable workaround discovered, this is a non-issue really.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    xsrc-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 30 23:15:01 +0000 2009
>Originator:     Craig Cheetham
>Release:        V5.0
>Organization:
>Environment:
>Description:
Originally I posted problem report #41644.

I have now discovered a workaround which will mean that this issue is no more. 

Basically I ventured on a quest to enable DRI on my system, and then test this issue again using the xorg.conf
details here http://www.netbsd.org/~jmcneill/index.html. To my surprise the problem was no more.
>How-To-Repeat:

>Fix:
Enable DRI.

http://www.netbsd.org/~jmcneill/index.html

(Continue reading)

David Laight | 1 Jul 2009 01:15
Picon

Re: bin/41652: newfs ignores block and frag sizes in disklabel

The following reply was made to PR bin/41652; it has been noted by GNATS.

From: David Laight <david <at> l8s.co.uk>
To: gnats-bugs <at> NetBSD.org
Cc: 
Subject: Re: bin/41652: newfs ignores block and frag sizes in disklabel
Date: Wed, 1 Jul 2009 00:13:45 +0100

 On Tue, Jun 30, 2009 at 09:40:00PM +0000, bad <at> bsd.de wrote:
 > >Number:         41652
 > >Category:       bin
 > >Synopsis:       newfs neither respects nor updates the block and frag sizes in disklabel
 ...
 > newfs(8) specifies that the defaults are taken from the disklabel.
 > I have chosen 8K/1k block/frag sizes in the disklabel for partitions.
 > newfs ignores this for filesystems >1G and uses 16k/2k block/frag sizes.
 > newfs also fails to update the block/frag sizes in the kernel as the man
 > page specifes.

 IMHO the block/frag sizes don't belong in the disklabel ....

 So maybe just the documentation should be changed.

 	David

 -- 
 David Laight: david <at> l8s.co.uk

Valeriy E. Ushakov | 1 Jul 2009 04:45
Picon

PR/41652 CVS commit: src/sbin/newfs

The following reply was made to PR bin/41652; it has been noted by GNATS.

From: "Valeriy E. Ushakov" <uwe <at> netbsd.org>
To: gnats-bugs <at> gnats.NetBSD.org
Cc: 
Subject: PR/41652 CVS commit: src/sbin/newfs
Date: Wed, 1 Jul 2009 02:43:35 +0000

 Module Name:	src
 Committed By:	uwe
 Date:		Wed Jul  1 02:43:35 UTC 2009

 Modified Files:
 	src/sbin/newfs: newfs.8

 Log Message:
 G/c sentence fragment left over from vinum reference (forgotten in 1.69).
 Noticed by bad <at>  in PR bin/41652

 
 To generate a diff of this commit:
 cvs rdiff -u -r1.73 -r1.74 src/sbin/newfs/newfs.8

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

David Holland | 1 Jul 2009 07:10
Picon

Re: xsrc/41644 - Favourable workaround discovered, this is a non-issue really.]

The following reply was made to PR xsrc/41644; it has been noted by GNATS.

From: David Holland <dholland-bugs <at> netbsd.org>
To: gnats-bugs <at> netbsd.org
Cc: 
Subject: Re: xsrc/41644 - Favourable workaround discovered, this is a
	non-issue really.]
Date: Wed, 1 Jul 2009 05:08:51 +0000

 This was meant to be a comment on 41644, not its own PR.

    ------

 From: c.cheetham <at> yahoo.co.uk
 To: xsrc-manager <at> netbsd.org, gnats-admin <at> netbsd.org, netbsd-bugs <at> netbsd.org
 Cc: 
 Subject: xsrc/41656: Followup: 41644 - Favourable workaround discovered, this
 	is a non-issue really.
 Date: Tue, 30 Jun 2009 23:15:01 +0000 (UTC)

 Originally I posted problem report #41644.

 I have now discovered a workaround which will mean that this issue is no more. 

 Basically I ventured on a quest to enable DRI on my system, and then test this issue again using the xorg.conf
details here http://www.netbsd.org/~jmcneill/index.html. To my surprise the problem was no more.

 
  >Fix:
 Enable DRI.
(Continue reading)

David Holland | 1 Jul 2009 07:15
Picon

Re: bin/41652: newfs ignores block and frag sizes in disklabel

The following reply was made to PR bin/41652; it has been noted by GNATS.

From: David Holland <dholland-bugs <at> netbsd.org>
To: gnats-bugs <at> NetBSD.org
Cc: 
Subject: Re: bin/41652: newfs ignores block and frag sizes in disklabel
Date: Wed, 1 Jul 2009 05:13:05 +0000

 On Tue, Jun 30, 2009 at 11:15:06PM +0000, David Laight wrote:
  >  > newfs(8) specifies that the defaults are taken from the disklabel.
  >  > I have chosen 8K/1k block/frag sizes in the disklabel for partitions.
  >  > newfs ignores this for filesystems >1G and uses 16k/2k block/frag sizes.
  >  > newfs also fails to update the block/frag sizes in the kernel as the man
  >  > page specifes.
  >  
  >  IMHO the block/frag sizes don't belong in the disklabel ....
  >  
  >  So maybe just the documentation should be changed.

 I agree, but traditionally they're kept there, and since the fields
 exist we need to either honor them or be explicit about ignoring them.
 So it isn't quite that simple.

 -- 
 David A. Holland
 dholland <at> netbsd.org

David Holland | 1 Jul 2009 07:18
Picon

Re: xsrc/41644 - Favourable workaround discovered, this is a non-issue really.]

 > I have now discovered a workaround which will mean that this issue
 > is no more.

That's good, but it isn't really a fix, so let's leave the PR open.

--

-- 
David A. Holland
dholland <at> netbsd.org

dholland | 1 Jul 2009 07:19
Picon

Re: xsrc/41656 (Followup: 41644 - Favourable workaround discovered, this is a non-issue really.)

Synopsis: Followup: 41644 - Favourable workaround discovered, this is a non-issue really.

State-Changed-From-To: open->closed
State-Changed-By: dholland <at> NetBSD.org
State-Changed-When: Wed, 01 Jul 2009 05:19:04 +0000
State-Changed-Why:
Meant to be a comment on xsrc/41644.

David Holland | 1 Jul 2009 07:25
Picon

Re: port-evbmips/41650: NetBSD/evbmips -current on MERAKI/Atheros 2315 WiSoC crashes

On Tue, Jun 30, 2009 at 08:40:03PM +0000, Fredrik Pettai wrote:
 >  > "trace" output, please?
 >  
 >  db> trace
 >  PC 0x1bb958f6: not in kernel space
 >  0+1bb958f6 (a87f0000,b0000000,c003020,4) ra 0 sz 0
 >  User-level: pid 0.1

oh joy.

'show registers'?

--

-- 
David A. Holland
dholland <at> netbsd.org

David Holland | 1 Jul 2009 07:30
Picon

Re: port-evbmips/41650: NetBSD/evbmips -current on MERAKI/Atheros 2315 WiSoC crashes

The following reply was made to PR port-evbmips/41650; it has been noted by GNATS.

From: David Holland <dholland-bugs <at> netbsd.org>
To: gnats-bugs <at> NetBSD.org
Cc: port-evbmips-maintainer <at> netbsd.org, gnats-admin <at> netbsd.org,
	netbsd-bugs <at> netbsd.org, pettai <at> nordu.net
Subject: Re: port-evbmips/41650: NetBSD/evbmips -current on MERAKI/Atheros
	2315 WiSoC crashes
Date: Wed, 1 Jul 2009 05:25:09 +0000

 On Tue, Jun 30, 2009 at 08:40:03PM +0000, Fredrik Pettai wrote:
  >  > "trace" output, please?
  >  
  >  db> trace
  >  PC 0x1bb958f6: not in kernel space
  >  0+1bb958f6 (a87f0000,b0000000,c003020,4) ra 0 sz 0
  >  User-level: pid 0.1

 oh joy.

 'show registers'?

 -- 
 David A. Holland
 dholland <at> netbsd.org

David Holland | 1 Jul 2009 07:53
Picon

Re: port-evbmips/41650: NetBSD/evbmips -current on MERAKI/Atheros 2315 WiSoC crashes

On Tue, Jun 30, 2009 at 07:15:00AM +0000, pettai <at> nordu.net wrote:
 > status=0x2, cause=0x50008010

These values make no sense - are you sure you transcribed them
correctly?

--

-- 
David A. Holland
dholland <at> netbsd.org


Gmane