Current issues

2002-12-11 Thread Marcus Reid
Hi:

I made the jump to CURRENT this morning (via a fresh -RC1 install) and
made the following observations.

1. Thought I toggled newfs off on the partition where /home was mounted.
   It went ahead and zapped it anyway. Good thing for backups..

2. USB doesn't work with my chipset. I have an Asus A7V with VIA chipset.
   Kernel messages follow. Please contact me if I can assist in debugging.

Otherwise, smooth sailing. I'm sure I'll break something else soon :)

Marcus

uhci0: VIA 83C572 USB controller port 0xd400-0xd41f irq 9 at device 4.2 on pci0
usb0: VIA 83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub0: port error, restarting port 1
uhub0: port error, giving up port 1
uhub0: port error, restarting port 2
uhub0: port error, giving up port 2
uhci1: VIA 83C572 USB controller port 0xd000-0xd01f irq 9 at device 4.3 on pci0
usb1: VIA 83C572 USB controller on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub1: port error, restarting port 1
uhub1: port error, giving up port 1
uhub1: port error, restarting port 2
uhub1: port error, giving up port 2
uhub2: ALCOR Generic USB Hub, class 9/0, rev 1.10/1.00, addr 2
uhub2: 4 ports with 4 removable, self powered

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Current issues

2002-12-11 Thread Chris Faulhaber
On Wed, Dec 11, 2002 at 08:59:04AM -0800, Marcus Reid wrote:
 Hi:
 
 I made the jump to CURRENT this morning (via a fresh -RC1 install) and
 made the following observations.
 
 1. Thought I toggled newfs off on the partition where /home was mounted.
It went ahead and zapped it anyway. Good thing for backups..
 
 2. USB doesn't work with my chipset. I have an Asus A7V with VIA chipset.
Kernel messages follow. Please contact me if I can assist in debugging.
 

I get the same errors on my Asus A7V333 yet my usb mouse works:

jedgar@darkstar:~$ dmesg | grep ^u
uhci0: VIA 83C572 USB controller port 0xb400-0xb41f irq 5 at device 9.0 on pci0
usb0: VIA 83C572 USB controller on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhub0: port error, restarting port 1
uhub0: port error, giving up port 1
uhub0: port error, restarting port 2
uhub0: port error, giving up port 2
uhci1: VIA 83C572 USB controller port 0xb000-0xb01f irq 11 at device 9.1 on pci0
usb1: VIA 83C572 USB controller on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub1: port error, restarting port 1
uhub1: port error, giving up port 1
uhub1: port error, restarting port 2
uhub1: port error, giving up port 2
uhci2: VIA 83C572 USB controller port 0xa000-0xa01f irq 9 at device 17.2 on pci0
usb2: VIA 83C572 USB controller on uhci2
usb2: USB revision 1.0
uhub2: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhub2: port error, restarting port 1
uhub2: port error, giving up port 1
uhub2: port error, restarting port 2
uhub2: port error, giving up port 2
ums0: Logitech USB-PS/2 Optical Mouse, rev 2.00/11.10, addr 2, iclass 3/1
ums0: 3 buttons and Z dir.
uhci3: VIA 83C572 USB controller port 0x9800-0x981f irq 9 at device 17.3 on pci0
usb3: VIA 83C572 USB controller on uhci3
usb3: USB revision 1.0
uhub3: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
uhub3: port error, restarting port 1
uhub3: port error, giving up port 1
uhub3: port error, restarting port 2
uhub3: port error, giving up port 2
jedgar@darkstar:~$ sudo usbdevs -v  
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 
1.00
 port 1 powered
 port 2 powered
Controller /dev/usb1:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 
1.00
 port 1 powered
 port 2 powered
Controller /dev/usb2:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 
1.00
 port 1 powered
 port 2 addr 2: low speed, power 98 mA, config 1, USB-PS/2 Optical Mouse(0xc00e), 
Logitech(0x046d), rev 11.10
Controller /dev/usb3:
addr 1: full speed, self powered, config 1, UHCI root hub(0x), VIA(0x), rev 
1.00
 port 1 powered
 port 2 powered
jedgar@darkstar:~$ 

-- 
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

FreeBSD: The Power To Serve   -   http://www.FreeBSD.org



msg48534/pgp0.pgp
Description: PGP signature


Re: Current issues

2002-12-11 Thread Marcus Reid
On Wed, Dec 11, 2002 at 08:59:04AM -0800, Marcus Reid wrote:
 Hi:
 
 2. USB doesn't work with my chipset. I have an Asus A7V with VIA chipset.
Kernel messages follow. Please contact me if I can assist in debugging.

Looks like I spoke too soon. It doesn't work with the RC1 GENERIC kernel,
but after a cvsup and a build it's fine. I'll try to break something real
next time.

Marcus

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Current issues

2002-12-11 Thread Christian Brueffer
On Wed, Dec 11, 2002 at 01:25:22PM -0500, Chris Faulhaber wrote:
 On Wed, Dec 11, 2002 at 08:59:04AM -0800, Marcus Reid wrote:
  Hi:
  
  I made the jump to CURRENT this morning (via a fresh -RC1 install) and
  made the following observations.
  
  1. Thought I toggled newfs off on the partition where /home was mounted.
 It went ahead and zapped it anyway. Good thing for backups..
  
  2. USB doesn't work with my chipset. I have an Asus A7V with VIA chipset.
 Kernel messages follow. Please contact me if I can assist in debugging.
  
 
 I get the same errors on my Asus A7V333 yet my usb mouse works:
 

The same here (Asus A7M266).

- Christian

-- 
http://www.unixpages.org[EMAIL PROTECTED]
GPG Pub-Key: www.unixpages.org/cbrueffer.asc
GPG Fingerprint: A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D
GPG Key ID : 0xA0ED982D



msg48541/pgp0.pgp
Description: PGP signature


Current issues

2002-12-10 Thread Paul Richards
I'm trying to thrash 5.0 a bit but I've run into some rather more
basic issues right off.

1) I think I'm suffering from the 1GB memory hang problem. I'm
definitely getting the hangs :-) I'll leave this for now since I'll
do some more testing tonight and it's already been raised by someone
else anyway, so this is just a me too.

2) The IPFW2 syntax is not compatible with IPFW. The latter accepts
rules in the form of

1 add ... 

whereas IPFW2 doesn't understand that format and requires

add 1 ..

3) The compiler won't build some C++ packages, evolution being the
particular one bothering me at the moment. Is this a known issues
that the 5.0 compiler won't build all packages?

I will report other problems as I find them :-)

Paul.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Current issues

2002-12-10 Thread Patrick Hartling
Mark Murray wrote:

I'm trying to thrash 5.0 a bit but I've run into some rather more
basic issues right off.

1) I think I'm suffering from the 1GB memory hang problem. I'm
definitely getting the hangs :-) I'll leave this for now since I'll
do some more testing tonight and it's already been raised by someone
else anyway, so this is just a me too.



I had a nasty console hang (all the VTYs hung about 2 minutes after
boot, but the box was otherwise stable enough to make world). I make
damn sure I was clean and did a proper make everything (no NOCLEAN) and
all was well.


I think that I am seeing this as well since I updated to -current from 
Dec 4.  It doesn't bother me too much since I really only use the machine 
remotely right now.  As a result, I haven't been keeping close track to 
see if there have been similar reports or a fix yet.  The first time it 
hung for me was during 'make installworld' from a single-user boot.  I 
was following the nine-step procedure in /usr/src/Makefile exactly.  It 
sounds like doing another update would clear things up, no?

 -Patrick


--
Patrick L. Hartling			| Research Assistant, VRAC
[EMAIL PROTECTED]| 2274 Howe Hall Room 2624
PGP: http://www.137.org/patrick/pgp.txt	| T: +1.515.294.4916
http://www.137.org/patrick/		| http://www.vrac.iastate.edu/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: Current issues

2002-12-10 Thread Scott Long
On Tue, Dec 10, 2002 at 09:37:20AM -0600, Patrick Hartling wrote:
 Mark Murray wrote:
 I'm trying to thrash 5.0 a bit but I've run into some rather more
 basic issues right off.
 
 1) I think I'm suffering from the 1GB memory hang problem. I'm
 definitely getting the hangs :-) I'll leave this for now since I'll
 do some more testing tonight and it's already been raised by someone
 else anyway, so this is just a me too.
 
 
 I had a nasty console hang (all the VTYs hung about 2 minutes after
 boot, but the box was otherwise stable enough to make world). I make
 damn sure I was clean and did a proper make everything (no NOCLEAN) and
 all was well.
 
 I think that I am seeing this as well since I updated to -current from 
 Dec 4.  It doesn't bother me too much since I really only use the machine 
 remotely right now.  As a result, I haven't been keeping close track to 
 see if there have been similar reports or a fix yet.  The first time it 
 hung for me was during 'make installworld' from a single-user boot.  I 
 was following the nine-step procedure in /usr/src/Makefile exactly.  It 
 sounds like doing another update would clear things up, no?
 

There were console problems for people using the ahc and ahd drivers that
were fixed late in the day on Dec 4.  Maybe this is what you're seeing?

Scott

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Current issues

2002-12-10 Thread Patrick Hartling
Scott Long wrote:

On Tue, Dec 10, 2002 at 09:37:20AM -0600, Patrick Hartling wrote:


Mark Murray wrote:


I'm trying to thrash 5.0 a bit but I've run into some rather more
basic issues right off.

1) I think I'm suffering from the 1GB memory hang problem. I'm
definitely getting the hangs :-) I'll leave this for now since I'll
do some more testing tonight and it's already been raised by someone
else anyway, so this is just a me too.



I had a nasty console hang (all the VTYs hung about 2 minutes after
boot, but the box was otherwise stable enough to make world). I make
damn sure I was clean and did a proper make everything (no NOCLEAN) and
all was well.


I think that I am seeing this as well since I updated to -current from 
Dec 4.  It doesn't bother me too much since I really only use the machine 
remotely right now.  As a result, I haven't been keeping close track to 
see if there have been similar reports or a fix yet.  The first time it 
hung for me was during 'make installworld' from a single-user boot.  I 
was following the nine-step procedure in /usr/src/Makefile exactly.  It 
sounds like doing another update would clear things up, no?



There were console problems for people using the ahc and ahd drivers that
were fixed late in the day on Dec 4.  Maybe this is what you're seeing?


Probably so!  I am indeed using the ahc driver on the machine in 
question.  Thanks for the suggestion.  :)

 -Patrick


--
Patrick L. Hartling			| Research Assistant, VRAC
[EMAIL PROTECTED]| 2274 Howe Hall Room 2624
PGP: http://www.137.org/patrick/pgp.txt	| T: +1.515.294.4916
http://www.137.org/patrick/		| http://www.vrac.iastate.edu/


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


Re: Current issues

2002-12-10 Thread Kris Kennaway
On Tue, Dec 10, 2002 at 02:01:08PM +, Paul Richards wrote:

 3) The compiler won't build some C++ packages, evolution being the
 particular one bothering me at the moment. Is this a known issues
 that the 5.0 compiler won't build all packages?

Yes.

Kris



msg48472/pgp0.pgp
Description: PGP signature


Re: Current issues

2002-12-10 Thread Joe Marcus Clarke
On Tue, 2002-12-10 at 15:48, Kris Kennaway wrote:
 On Tue, Dec 10, 2002 at 02:01:08PM +, Paul Richards wrote:
 
  3) The compiler won't build some C++ packages, evolution being the
  particular one bothering me at the moment. Is this a known issues
  that the 5.0 compiler won't build all packages?
 
 Yes.

Evo isn't a C++ application.  I haven't seen any build logs for it,
either.  I'm doing a build on my i386 machine now just to be sure.

Joe

 
 Kris
-- 
PGP Key : http://www.marcuscom.com/pgp.asc




To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Current issues

2002-12-10 Thread Miguel Mendez
On 10 Dec 2002 16:02:14 -0500
Joe Marcus Clarke [EMAIL PROTECTED] wrote:

Hi,

 Evo isn't a C++ application.  I haven't seen any build logs for it,
 either.  I'm doing a build on my i386 machine now just to be sure.

I built it a couple of days ago on my 5.0-RC system, works okay.

flynn@christine# pkg_info|grep evo
evolution-1.2.0_2   An integrated mail, calendar and address book distributed s
gal-0.21A collection of widgets taken from GNOME gnumeric and evolu
flynn@christine# uname -a
FreeBSD christine.energyhq.tk 5.0-RC FreeBSD 5.0-RC #0: Sat Dec  7 22:56:40 CET 2002   
  [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CHRISTINE  i386

Cheers,
-- 
Miguel Mendez - [EMAIL PROTECTED]
GPG Public Key :: http://energyhq.homeip.net/files/pubkey.txt
EnergyHQ :: http://www.energyhq.tk
Of course it runs NetBSD!

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: Current issues

2002-12-10 Thread Paul Richards
On Tue, Dec 10, 2002 at 04:02:14PM -0500, Joe Marcus Clarke wrote:
 On Tue, 2002-12-10 at 15:48, Kris Kennaway wrote:
  On Tue, Dec 10, 2002 at 02:01:08PM +, Paul Richards wrote:
  
   3) The compiler won't build some C++ packages, evolution being the
   particular one bothering me at the moment. Is this a known issues
   that the 5.0 compiler won't build all packages?
  
  Yes.
 
 Evo isn't a C++ application.  I haven't seen any build logs for it,
 either.  I'm doing a build on my i386 machine now just to be sure.

You're right, it was one of the dependencies, maybe aspell. Anyway, I've
got it built now, it was old include files that was the problem since
this had originally been a 4.x machine.

Paul.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Re: 4.0-CURRENT issues...

2000-02-15 Thread Kazutaka YOKOTA


I have 2 issues with 4.0-CURRENT.  The first is the plethora of
"microuptime() went backwards..." errors that scroll on my console.

The second is that I have DDB compiled into my kernel (and a USB keyboard)
either on vga or serial console, if I trip DDB (control-shift-esc), I will
either get the ddb prompt or the system will hard lock. Below is my 
dmesg and kernel config.  Help is appreciated.

Is there a reliable way to reproduce this?  Do you have any error
messages when this happens?

Kazu

[...]
usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ums0: Microsoft Microsoft IntelliMouse\M-. Explorer, rev 1.10/1.03, addr 2, ic
lass 3/1
ums0: 5 buttons and Z dir.
ukbd0: Microsoft Natural Keyboard Elite, rev 1.00/1.04, addr 3, iclass 3/1
[...]
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0: System console at flags 0x100 on isa0
sc0: VGA 16 virtual consoles, flags=0x100
sio0 at port 0x3f8-0x3ff irq 4 flags 0x30 on isa0
sio0: type 16550A, console
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
[...]

device  vga0at isa?

# syscons is the default console driver, resembling an SCO console
device  sc0 at isa? flags 0x100
[...]

device  uhci# UHCI PCI-USB interface
device  ohci# OHCI PCI-USB interface
device  usb # USB Bus (required)
device  ugen# Generic
device  uhid# "Human Interface Devices"
device  ukbd# Keyboard
device  ulpt# Printer
device  umass   # Disks/Mass storage - Requires scbus and da
device  ums # Mouse


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message