Re: Can't install R5.4

2005-07-25 Thread Vladimir Botka

Hello,
I had the same problem. Just create the slice and exit sysinstall. Start 
sysinstall again and create partitions. It works for me but cannot explain 
why. Or use fdisk/disklabel.


Cheers,
Vladimir.

On Tue, 26 Jul 2005, Nobuhiko Yoshimoto wrote:



I tried to install Rel5.4 on ASUS T2-R with WD1600BB-00GUA0. When I
entered Partiton, received warning as below.

"A geometry of 310101/6/63 for ad0 is incorrect. Using a more likely
geometry. "

However, fdisk showed Disk Geometry as below. It seems reasonable
values.

Disk name: ad0
DISK Geometry: 19457 cyls/255 heads/63 sectors = 312576705 sectors (152625MB)

After having created a slice (as0s2), I enterd Disklabel and the
partitions required. But, entering Commit, installers said "Unable to
make new root filesystem on /dev/ad0s2a! Command returned status 36",
and "Couldn't make filesystems properly. Aborting."

After abortion of installation, I examined the disk and found disk
slice has been created normally, and MBR also installed. Why couldn't
the installer create file system on it?

The "status 36", what does it mean? I need your help.


Nobuhiko Yoshimoto
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Can't install R5.4

2005-07-25 Thread Nobuhiko Yoshimoto

I tried to install Rel5.4 on ASUS T2-R with WD1600BB-00GUA0. When I
entered Partiton, received warning as below.

"A geometry of 310101/6/63 for ad0 is incorrect. Using a more likely
geometry. "

However, fdisk showed Disk Geometry as below. It seems reasonable
values.

Disk name: ad0
DISK Geometry: 19457 cyls/255 heads/63 sectors = 312576705 sectors (152625MB)

After having created a slice (as0s2), I enterd Disklabel and the
partitions required. But, entering Commit, installers said "Unable to
make new root filesystem on /dev/ad0s2a! Command returned status 36",
and "Couldn't make filesystems properly. Aborting."

After abortion of installation, I examined the disk and found disk
slice has been created normally, and MBR also installed. Why couldn't
the installer create file system on it?

The "status 36", what does it mean? I need your help.


Nobuhiko Yoshimoto
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Quality of FreeBSD

2005-07-25 Thread J. Porter Clark
>On 7/25/05, J. Porter Clark <[EMAIL PROTECTED]> wrote:
>>
>> The ATA (definitely not SATA) controller on my Dell Latitude
>> C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times
>> a day unless I turn off DMA.  It hangs for 3-4 seconds, logs
>> errors, then proceeds.  It isn't heavily loaded.  I tried using
>> Soren's ATA mkIII patches, and now it likes to panic about that
>> same frequency instead of hanging, so I'm going back to the
>> stock RELENG_5 config next chance I get.
>>
>> It's one of these:
>>
>>   atapci0:  port 
>> 0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0

>Your going back to stock RELENG_5 from what?

RELENG_5 with Soren's patches.

>I have that very same laptop running FreeBSD from 5.0 up to 5.4 with
>absolutely no DMA problems using it.
>Note: I did exchange the HDD from 20 to 60GB, different brands.

Might be a clue.  My laptop has this:

  ad0: 19077MB  at ata0-master UDMA100

Typical errors:
  Jul 23 15:00:33 auricle kernel: ad0: TIMEOUT - WRITE_DMA retrying (2 retries 
left) LBA=20586350
  Jul 25 09:01:52 auricle kernel: ad0: TIMEOUT - READ_MUL retrying (2 retries 
left) LBA=1731115

I had been running 4.X on this box with no DMA problems until I
put 5.3 on it many months ago.  It also boots Windows XP, and I
don't have any obvious disk problems with that.

Do you have trouble with the touchpad occasionally going nuts?
I had mine replaced, and it still does it.  With any OS I care
to boot.

I have some Firewire-related problems, too, but I won't go into
them right now.

-- 
J. Porter Clark <[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: em(4) stops passing data

2005-07-25 Thread UEMURA (fka. MAENAKA) Tetsuya
I had had apparently same problem in April. For my time, em0 seemed dead,
though no link down message was generated, and could go up again by
`ifconfig em0 down; ifconfig em0 up'.

My problem was caused by defected power supply which generated around
4.5V instead of 5V, and corrected completely by replacing of power
supply.

FYI, use physical mean when measuring voltage. Reported in BIOS or
monitor software may vary from actual.

-- 
UEMURA (fka. MAENAKA) Tetsuya <[EMAIL PROTECTED]>

Posted on Tue, 26 Jul 2005 02:36:40 +0100 (BST)
by author Chris Howells <[EMAIL PROTECTED]>
> I have a server with an Asus A7V8X-X motherboard and a Intel 1000 Pro MT
> Gigabit ethernet card. I have only had the Gigabit card for a few days,
> and all seemed to be well to start with -- but today the card has started
> to stop passing data after fairly high network load (for instance it
> always stops some way through transferring 4 x 500MB files from a Windows
> machine to a drive in the machine using samba).
> 
> After it stops passing data it's impossible to ping the machine, or to
> ping other machines from the machine.
> 
> However, the strange bit is that a simple 'ifconfig em0 down && ifconfig
> em0 up' "fixes" the problem.

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


em(4) stops passing data

2005-07-25 Thread Chris Howells
Hi,

I have a server with an Asus A7V8X-X motherboard and a Intel 1000 Pro MT
Gigabit ethernet card. I have only had the Gigabit card for a few days,
and all seemed to be well to start with -- but today the card has started
to stop passing data after fairly high network load (for instance it
always stops some way through transferring 4 x 500MB files from a Windows
machine to a drive in the machine using samba).

After it stops passing data it's impossible to ping the machine, or to
ping other machines from the machine.

However, the strange bit is that a simple 'ifconfig em0 down && ifconfig
em0 up' "fixes" the problem.

I've just spent quite a few hours messing about -- first of all upgrading
the machine from 5.3-STABLE to 5.4 to 5.4-STABLE, but with no improvement.
I've also tried Intel's official driver with no improvement. I've disabled
'apic' in the kernel config, disabled ACPI from the loader, changed the
interrupt mode in the BIOS from 'apic' to 'pic', disabled the USB
controllers and various other things, all to no avail.

The machine is connected to a SMC EZ 5 port Gigabit switch.

Any input greatfully received, I am completely stumped, particularly as it
seemed to work for a few days.

(see below sigature for dmesg)

-- 
Cheers, Chris Howells -- [EMAIL PROTECTED]
Web: http://www.kde.org.uk, PGP ID: 0x33795A2C
KDE/Qt Developer: http://www.kde.org

Copyright (c) 1992-2005 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.4-STABLE #12: Tue Jul 26 01:55:51 BST 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SAURON
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Duron(TM) (1791.22-MHz 686-class CPU)
  Origin = "AuthenticAMD"  Id = 0x681  Stepping = 1
  
Features=0x383fbff
  AMD Features=0xc040
real memory  = 402636800 (383 MB)
avail memory = 384323584 (366 MB)
npx0:  on motherboard
npx0: INT 16 interface
acpi0:  on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <32-bit timer at 3.579545MHz> port 0xe408-0xe40b on acpi0
cpu0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
agp0:  mem
0xf800-0xfbff at device 0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
atapci0:  port
0xa400-0xa40f,0xa800-0xa803,0xb000-0xb007,0xb400-0xb403,0xb800-0xb807 mem
0xf280-0xf2803fff irq 3 at device 12.0 on pci0
ata2: channel #0 on atapci0
ata3: channel #1 on atapci0
atapci1:  port
0x8800-0x880f,0x9000-0x9003,0x9400-0x9407,0x9800-0x9803,0xa000-0xa007 mem
0xf200-0xf2003fff irq 11 at device 13.0 on pci0
ata4: channel #0 on atapci1
ata5: channel #1 on atapci1
ahc0:  port 0x8400-0x84ff mem
0xf180-0xf1800fff irq 10 at device 14.0 on pci0
aic7880: Ultra Wide Channel A, SCSI Id=15, 16/253 SCBs
uhci0:  port 0x8000-0x801f at device 16.0 on pci0
usb0:  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
uhci1:  port 0x7800-0x781f at device 16.1 on pci0
usb1:  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
uhci2:  port 0x7400-0x741f at device 16.2 on pci0
usb2:  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
pci0:  at device 16.3 (no driver attached)
isab0:  at device 17.0 on pci0
isa0:  on isab0
atapci2:  port
0x7000-0x700f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 17.1 on pci0
ata0: channel #0 on atapci2
ata1: channel #1 on atapci2
pci0:  at device 17.5 (no driver attached)
pci0:  at device 18.0 (no driver attached)
em0:  port
0x6400-0x643f mem 0xf000-0xf001 irq 12 at device 19.0 on pci0
em0: Ethernet address: 00:0e:0c:74:0d:4c
em0:  Speed:N/A  Duplex:N/A
sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
sio0: type 16550A
atkbdc0:  port 0x64,0x60 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
orm0:  at iomem
0xd-0xd07ff,0xcc000-0xce7ff,0xc-0xc7fff on isa0
pmtimer0 on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
Timecounter "TSC" frequency 1791219571 Hz quality 800
Timecounters tick every 10.000 msec
ad0: 39205MB  [79656/16/63] at ata0-master UDMA133
ad2: 152627MB  [310101/16/63] at ata1-master
UDMA100
ad4: 152627MB  [310101/16/63] at ata2-master
UDMA100
ad6: 194481MB  [395136/16/63] at ata3-master UDMA100
ad8: 152627MB  [310101/16/63] at ata4-master
UDMA100
ad10: 152627MB  [310101/16/63] at
ata5-master UDMA100
Waiting 15 seconds for SCSI devices to settle
sa0 at ahc0 bus 0 target 6 lun 0
sa0:  Removable Sequential Access SCSI-3 device
sa0: 

6.0 Beta 1 partitioning as /dev/X?

2005-07-25 Thread Jayton Garnett

Hello,

I downloaded the FreeBSD 6.0 Beta 1 ISO's and burnt them as per usual 
and thought great let me try install it
I got to the sysinstall partitioning screen and allocated 20GB of my 
250GB ATA100 Western Digital hard drive.
This is where the problem starts, normally it will create the partition 
on something like  /dev/ad1s3 but in this case
it created it as /dev/X. I thought nothing of it at first thinking it 
was a new way that 6.x will be allocating the partitions.


I went on to select the normal stuff I want too install ( user + X, 
src/ALL ) and went on to try commit, I tried to commit
off the CD's, that did not work and had an error about the /dev/X, so I 
thought I would try install via FTP, the same error

popped up.

My hardware is as follows:

Jetway V266B motherboard ( 
http://www.jetway.com.tw/evisn/product/amd/v266b/v266b.htm )

Western Digital 80GB (IDE Channel 0, XP Pro only)
Western Digital 250GB (IDE Channel 1, FreeBSD 5.4, 3xNTFS, 1xFAT32)
768MB 266MHZ DDR

I use the GAG boot manager, this is not a Compaq/HP/Dell it is a custom 
built system.
I found a bug report about /dev/X being created as a hidden partition 
for XP, but since mine is not a OEM XP Pro
it should not create a so called hidden partition that would produce 
this failure (as far as I know) and if it was down to that

surely FreeBSD 5.4 would have had a similar problem.

Other links for reference:
http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/39604
http://www.freebsd.org/cgi/query-pr.cgi?pr=i386/84008

I have submitted this problem to the FreeBSD guys via the bug report on 
the FreeBSD website aswell.


--
Kind regards,
Jayton Garnett

email: [EMAIL PROTECTED]
Main : www.uberhacker.co.uk
Test server: jayton.plus.com


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Quality of FreeBSD

2005-07-25 Thread Joao Barros
On 7/25/05, J. Porter Clark <[EMAIL PROTECTED]> wrote:
> >The VIA SATA onboard controller on my server works (and has worked)
> >flawlessly.  I have two identical 80G Maxtor SATA drives connected to it
> >and have had absolutely no problems and excellent performance.  Even my
> >Dell Inspirion 5100--with a few hiccups--has made great progress and is
> >mostly functional.
> 
> The ATA (definitely not SATA) controller on my Dell Latitude
> C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times
> a day unless I turn off DMA.  It hangs for 3-4 seconds, logs
> errors, then proceeds.  It isn't heavily loaded.  I tried using
> Soren's ATA mkIII patches, and now it likes to panic about that
> same frequency instead of hanging, so I'm going back to the
> stock RELENG_5 config next chance I get.
> 
> It's one of these:
> 
>   atapci0:  port 
> 0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0
> 

Your going back to stock RELENG_5 from what?
I have that very same laptop running FreeBSD from 5.0 up to 5.4 with
absolutely no DMA problems using it.
Note: I did exchange the HDD from 20 to 60GB, different brands.

--
Joao Barros
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Panic on 5.4, 1 second uptime

2005-07-25 Thread Gavin Atkinson

On Mon, 25 Jul 2005, Norberto Meijome wrote:


( This is an exact copy of my post to -questions)
Hi all,
I am trying to install 5.4 on a box that's been running Linux. It's a 2 year 
old 'Snap Appliance 4500' ( 
http://www.snapappliance.com/page.cfm?name=4500Main&nav=4500 ), with 4 x 120 
GB EIDE, P4, 512 Mb.


As soon as I try to load the kernel I get :
--- (copied by hand )
Fatal trap 10: trace trap while in vm86 mode
instruction pointer = 0xf000:0xf842
stack pointer= 0x0:0xff8
frame pointer   = 0x0:0x0
code segment  = base 0x330026, limit 0x1, type 0x9
= DPL 3, pres 1 def32 0, fram 0
processor eflags  = interrupt enabled, vm86, IOPL=0
current process   = 0 ()
trap number= 10
panic : trace trap
uptime : 1 s
-

Every time, the same pointers / segments. This happens right after the kernel 
memory addresses (data? segment? pls excuse my ignorance) show after pressing 
an option in the boot menu.


Can you boot in verbose mode and try and get a few of the lines before the 
lines you quoted?  Knowing roughly where in the boot process this happens 
will probably greatly help.


Gavin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Quality of FreeBSD

2005-07-25 Thread J. T. Farmer

J. Porter Clark wrote:


The ATA (definitely not SATA) controller on my Dell Latitude
C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times
a day unless I turn off DMA.  It hangs for 3-4 seconds, logs
errors, then proceeds.  It isn't heavily loaded.  I tried using
Soren's ATA mkIII patches, and now it likes to panic about that
same frequency instead of hanging, so I'm going back to the
stock RELENG_5 config next chance I get.

It's one of these:

 atapci0:  port 
0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0



I have the same problem, only worse :^<  I could not get through the install
without booting in same mode.  WRITE_DMA errors all over the place when
writing out the superblocks.  I haven't tried the ATA mkIII patches yet, RL
has been very busy & I've not gotten back to this workstation.

It happens all the time for disk activity.  There appears to be no relation
to load or activity.

It's a plain vanilla KT266A system with an 80G WDC PATA drive

Here is the dmesg info:

FreeBSD 5.4-STABLE-20050708-JPSNAP #0: Fri Jul  8 01:47:15 UTC 2005
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) XP 2200+ (1794.90-MHz 686-class CPU)
 Origin = "AuthenticAMD"  Id = 0x681  Stepping = 1
 
Features=0x383f9ff
T,PSE36,MMX,FXSR,SSE>
 AMD Features=0xc040
real memory  = 1073741824 (1024 MB)
avail memory = 1041190912 (992 MB)
npx0:  on motherboard
npx0: INT 16 interface
cpu0 on motherboard
pcib0:  pcibus 0 on motherboard
pir0:  on motherboard
pci0:  on pcib0
agp0:  mem 
0xe000-0xe7

ff at device 0.0 on pci0
pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
uhci0:  port 0xd000-0xd01f irq 11 at device 
16.0 on pci0

usb0:  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
uhci1:  port 0xd400-0xd41f irq 3 at device 
16.1 on pci0

usb1:  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
uhci2:  port 0xd800-0xd81f irq 10 at device 
16.2 on pci0

usb2:  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
pci0:  at device 16.3 (no driver attached)
isab0:  at device 17.0 on pci0
isa0:  on isab0
atapci0:  port 
0xdc00-0xdc0f,0x376,0x170-0x177,0x3f

6,0x1f0-0x1f7 at device 17.1 on pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
pci0:  at device 17.5 (no driver attached)
vr0:  port 0xe800-0xe8ff mem 
0xea001000-0xea00

10ff irq 11 at device 18.0 on pci0
miibus0:  on vr0
ukphy0:  on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
vr0: Ethernet address: 00:0a:e6:d4:0e:9d
orm0:  at iomem 0xc-0xc on isa0
pmtimer0 on isa0
atkbdc0:  at port 0x64,0x60 on isa0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
fdc0:  at port 0x3f0-0x3f5 irq 6 drq 2 on isa0
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ppc0:  at port 0x378-0x37f irq 7 on isa0
ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppc0: FIFO with 16/16/16 bytes threshold
ppbus0:  on ppc0
plip0:  on ppbus0
lpt0:  on ppbus0
lpt0: Interrupt-driven port
ppi0:  on ppbus0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown:  can't assign resources (port)
unknown:  can't assign resources (irq)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
unknown:  can't assign resources (port)
Timecounter "TSC" frequency 1794898271 Hz quality 800
Timecounters tick every 10.000 msec
ad0: 76319MB  [155061/16/63] at ata0-master 
PIO4

acd0: CDRW  at ata1-master PIO4


John

--
John T. FarmerOwner & CTOGoldSword Systems
[EMAIL PROTECTED] 865-691-6498   Knoxville TN
   Consulting, Design, & Development of Networks & Software

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Quality of FreeBSD

2005-07-25 Thread J. Porter Clark
>The VIA SATA onboard controller on my server works (and has worked)
>flawlessly.  I have two identical 80G Maxtor SATA drives connected to it
>and have had absolutely no problems and excellent performance.  Even my
>Dell Inspirion 5100--with a few hiccups--has made great progress and is
>mostly functional.

The ATA (definitely not SATA) controller on my Dell Latitude
C840 laptop has READ_DMA, WRITE_DMA problems, maybe 2-3 times
a day unless I turn off DMA.  It hangs for 3-4 seconds, logs
errors, then proceeds.  It isn't heavily loaded.  I tried using
Soren's ATA mkIII patches, and now it likes to panic about that
same frequency instead of hanging, so I'm going back to the
stock RELENG_5 config next chance I get.

It's one of these:

  atapci0:  port 
0xbfa0-0xbfaf,0x376,0x170-0x177,0x 3f6,0x1f0-0x1f7 at device 31.1 on pci0

-- 
J. Porter Clark <[EMAIL PROTECTED]>
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: "Save as page..." freezes firefox for 15 minutes

2005-07-25 Thread manfred
On Sun, 24 Jul 2005 19:43:23 +
Ben Kaduk <[EMAIL PROTECTED]> wrote:

> 
> Thanks, marcel -- the 'firefox-bin' process (which does most of the
> work for firefox) is sleeping while waiting on kserel -- the
> kse_release state from the threading library.  A little work on
> google shows that other people have had problems with firefox being
> stuck in this state; for example, see this thread:
> http://www.freebsd.org/cgi/getmsg.cgi?fetch=911761+0+/usr/local/www/db/text/2005/freebsd-current/20050424.freebsd-current
> The problem for this person involved loading pages with lots of flash
> -- are you using a flash plugin, and are the pages that you're trying
> to save using flash?  Also, are you using the native firefox, or
> linux-firefox?
> It might also be useful to know which version of the threading library
> you're using; can you send the output of "ldd `locate firefox-bin`"?
> 
> Ben Kaduk


Well, I'm using flash. However, firefox hangs an any website when I try
"Save Page As..." the very first time after starting it. I even
deinstalled flash and deleted the ~/.mozilla directory. The same
freeze on www.google.com or whatever site I choose.


/usr/X11R6/lib/firefox/firefox-bin:
libmozjs.so => not found (0x0)
libxpcom.so => not found (0x0)
libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x28093000)
libplds4.so => /usr/local/lib/libplds4.so (0x2818)
libplc4.so => /usr/local/lib/libplc4.so (0x281a5000)
libnspr4.so => /usr/local/lib/libnspr4.so (0x281cb000)
libgtk-x11-2.0.so.600 => /usr/X11R6/lib/libgtk-x11-2.0.so.600 
(0x281fa000)
libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x284a2000)
libstdc++.so.4 => /usr/lib/libstdc++.so.4 (0x28561000)
libm.so.3 => /lib/libm.so.3 (0x28633000)
libpthread.so.1 => /usr/lib/libpthread.so.1 (0x2864e000)
libc.so.5 => /lib/libc.so.5 (0x28672000)
libgdk-x11-2.0.so.600 => /usr/X11R6/lib/libgdk-x11-2.0.so.600 
(0x2874c000)
libgdk_pixbuf-2.0.so.600 => /usr/X11R6/lib/libgdk_pixbuf-2.0.so.600 
(0x287c5000)
libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x287d9000)
libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x287dd000)
libXinerama.so.1 => /usr/X11R6/lib/libXinerama.so.1 (0x287e5000)
libXfixes.so.3 => /usr/X11R6/lib/libXfixes.so.3 (0x287e8000)
libXcursor.so.1 => /usr/X11R6/lib/libXcursor.so.1 (0x287ed000)
libgmodule-2.0.so.600 => /usr/local/lib/libgmodule-2.0.so.600 
(0x287f6000)
libgobject-2.0.so.600 => /usr/local/lib/libgobject-2.0.so.600 
(0x287fa000)
libpangoxft-1.0.so.800 => /usr/X11R6/lib/libpangoxft-1.0.so.800 
(0x2883)
libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x28837000)
libfreetype.so.9 => /usr/local/lib/libfreetype.so.9 (0x28848000)
libz.so.2 => /lib/libz.so.2 (0x288ac000)
libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x288bc000)
libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x288c4000)
libfontconfig.so.1 => /usr/X11R6/lib/libfontconfig.so.1 (0x288d1000)
libpangox-1.0.so.800 => /usr/X11R6/lib/libpangox-1.0.so.800 (0x288f7000)
libatk-1.0.so.901 => /usr/local/lib/libatk-1.0.so.901 (0x28901000)
libintl.so.6 => /usr/local/lib/libintl.so.6 (0x28919000)
libglib-2.0.so.600 => /usr/local/lib/libglib-2.0.so.600 (0x28922000)
libpangoft2-1.0.so.800 => /usr/X11R6/lib/libpangoft2-1.0.so.800 
(0x289a1000)
libpango-1.0.so.800 => /usr/X11R6/lib/libpango-1.0.so.800 (0x289c4000)
libexpat.so.5 => /usr/local/lib/libexpat.so.5 (0x289fb000)


-- 
Manfred


-- 
Manfred




___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


FreeBSD Stable on Sony Vaio PCG K33

2005-07-25 Thread Maicon Stihler
Hi,

I recently bought a notebook (sony vaio pcg k33) and Im planning to
install FreeBSD stable on it. Does someone knows of some special trick
that must be performed to make it run at least almost fully working? I
searched google but failed to spot any report on this specific model.
I hope that theres is not any special incompatibilities with FreeBSD.
Any thoughts welcome.

Thank you
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: "Save as page..." freezes firefox for 15 minutes

2005-07-25 Thread Jacob Frelinger
On Sun, Jul 24, 2005 at 07:45:39AM +0200, manfred wrote:
> When the first time after loading firefox I choose File/Save Page as...
> firefox freezes for 15 minutes. Then the "Save as" window opens and all
> works fine.
> 
> After newly choosing File/Save Page as... the "Save as" windows opens up
> instantaneously.
> 
> The problem doesn't disappear even after deleting ~/.mozilla before
> starting firefox.
> 
> 
> I'm running firefox 1.0.6 under FreeBSD 5.4. The problem occured also with
> firefox 1.04. There is no CPU usage. It is simply a waiting situation.
> However, I have not the faintest idea what firefox is waiting for.
> 
> 
> Any ideas, how to track it down?

I'm having the same problem.  I've been unable to track down the
cause of the problem.  It looks to me to be something outside of
firefox, as a package built on an other machine that doesn't
exhibit the problem, still persists on my affected machine.

I'd also be grateful for help or advice in tracking this down.

-- 
Jacob "I'm Brainy For Zombie Pops" Frelinger 
Jolly at TheCoffinClub dot Com 
http://www.thecoffinclub.com 
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FreeBSD IO Performance (was Re: Quality of FreeBSD)

2005-07-25 Thread Bohdan Horst
On Mon, Jul 25, 2005 at 10:15:41PM +1200, Mark Kirkwood wrote:
> Hmm - looks like I missed that thread, never mind - repeatability of 
> findings is sound scientific principle :-)
> 
> With respect to changing the default for vfs.read_max - makes sense to 
> me, but it would be interesting to know if anyone has a system that 
> performs *worse* with it set to 16.
> 
> regards
> 
> Mark
> 
> Chris wrote:
> >Its been mentioned before and most experience the same as you by
> >setting it to 16 a dramatic improvement in the sequential read, I
> >currently run all my 5.x servers like this with no issues as a result.
> > I am curious if the default will ever be changed.

on my notebook:
IBM TP 600x
5.4-RELEASE-p4
ad0: 38154MB  [77520/16/63] at ata0-master UDMA33
APM enable (but same effect with disable APM)
AAC unfortunatelly not supported :(


anything above vfs.read_max=1 produce very annoying little sound (i can
hear disk heads) when playing movies..

my 2 cents

-- 
Bohdan 'Nexus' Horst
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Quality of FreeBSD

2005-07-25 Thread John Merryweather Cooper
Igor Robul wrote:

> Karl Denninger wrote:
>
>> Ok, Robert, but then here's the question
>>
>> How come the ATA code which was very stable in 4.x was screwed with in a
>> production release, breaking it, with no path backwards to the working
>> code?
>>  
>>
> I had not ANY problems with ATA on several mothersboards, both SMP and
> uniproc.
> ___
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
The VIA SATA onboard controller on my server works (and has worked)
flawlessly.  I have two identical 80G Maxtor SATA drives connected to it
and have had absolutely no problems and excellent performance.  Even my
Dell Inspirion 5100--with a few hiccups--has made great progress and is
mostly functional.

jmc

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: FYI - RELENG_6 branch has been created.

2005-07-25 Thread Claus Guttesen
>  Wow thats a big jump from what I got in a test I did a couple of months
> ago, here is a copy and paste of an older email
>  Are you using AMD64 mode or i386?

Sorry for the late reply, was on vacation (and off-line too :-). I'm
using the amd64-port, -O2 in kernel and ubench.

>  Dell 1850 Dual CPU with 4 Gigs of ram, thats in idle 
>  CPU: Intel(R) Xeon(TM) CPU 3.20GHz (3192.23-MHz 686-class CPU) 
>  
>  Ubench CPU:   170748 
>  Ubench MEM:   172775 
>   
>  Ubench AVG:   171761 
> 
> Not very scientific but here is my ubench on a dual nocona @ 2.8 GHz
> and 4 GB RAM on a Dell 2850:
> 
> 
> SCHED_4BSD and 6.0 stable pr. July 12'th 2005:
> 
> Ubench CPU: 260315
> Ubench MEM: 189686
> 
> Ubench AVG: 225000

regards
Claus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


panic with nfsd on 5.4-RELEASE-p1

2005-07-25 Thread Philippe PEGON

Hi,

last friday we had a panic on a FreeBSD 5.4-RELEASE-p1 visibly related to nfsd. 
This
box exports home directory for approxymately 20 users with nfs.

$ uname -a
FreeBSD crc.u-strasbg.fr 5.4-RELEASE-p1 FreeBSD 5.4-RELEASE-p1 #2: Thu Jun
 9 12:59:40 CEST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CRC
 i386

The kernel config file and dmesg are attached. The kernel is launched with ACPI 
enabled.

Fatal trap 12: page fault in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code  = supervisor write, page not present
instruction pointer = 0x8:0xc0739000
stack pointer   = 0x10:0xe925ea08
frame pointer   = 0x10:0xe925ea24
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 499 (nfsd)
[thread pid 499 tid 100154 ]
Stopped at  nfs_rephead+0x144:  movl%eax,0(%edx)
db> trace
Tracing pid 499 tid 100154 td 0xc3954600
nfs_rephead(78,c9266c00,0,e925ea60,e925ea64) at nfs_rephead+0x144
nfsrv_remove(c9266c00,c3ff4b80,c3954600,e925eca8,e925eca4) at nfsrv_remove+0x5d9
nfssvc_nfsd(c3954600,0,c3954600,e925ece8,c3957388) at nfssvc_nfsd+0x406
nfssvc(c3954600,e925edl14,2,0,296) at nfssvc+0x1bc
syscall(2f,2f,2f,bfbfeec4,8) at syscall+0x2b3
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (155, FreeBSD ELF32, nfssvc), eip = 0x280c3b9b, esp = 0xbfbfeb1c, 
ebp = 0xbfbfeb38 ---

--
Philippe PEGON

#
# CRC
#

machine i386
cpu I686_CPU
ident   CRC

# To statically compile in device wiring instead of /boot/device.hints
#hints  "GENERIC.hints" # Default places to look for devices.

options SCHED_4BSD  # 4BSD scheduler
options INET# InterNETworking
options INET6   # IPv6 communications protocols
options FFS # Berkeley Fast Filesystem
options SOFTUPDATES # Enable FFS soft updates support
options UFS_ACL # Support for access control lists
options UFS_DIRHASH # Improve performance on big directories
options MD_ROOT # MD is a potential root device
options NFSCLIENT   # Network Filesystem Client
options NFSSERVER   # Network Filesystem Server
options NFS_ROOT# NFS usable as /, requires NFSCLIENT
options MSDOSFS # MSDOS Filesystem
options CD9660  # ISO 9660 Filesystem
options PROCFS  # Process filesystem (requires PSEUDOFS)
options PSEUDOFS# Pseudo-filesystem framework
options GEOM_GPT# GUID Partition Tables.
options COMPAT_43   # Compatible with BSD 4.3 [KEEP THIS!]
options COMPAT_FREEBSD4 # Compatible with FreeBSD4
options SCSI_DELAY=15000# Delay (in ms) before probing SCSI
options KTRACE  # ktrace(1) support
options SYSVSHM # SYSV-style shared memory
options SYSVMSG # SYSV-style message queues
options SYSVSEM # SYSV-style semaphores
options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time 
extensions
options KBD_INSTALL_CDEV# install a CDEV entry in /dev
options AHC_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~128k to driver.
options AHD_REG_PRETTY_PRINT# Print register bitfields in debug
# output.  Adds ~215k to driver.
options ADAPTIVE_GIANT  # Giant mutex is adaptive.

device  apic# I/O APIC

# Bus support.  Do not remove isa, even if you have no isa slots
device  isa
device  eisa
device  pci

# Floppy drives
device  fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  ataraid # ATA RAID drives
device  atapicd # ATAPI CDROM drives
device  atapifd # ATAPI floppy drives
device  atapist # ATAPI tape drives
options ATA_STATIC_ID   # Static device numbering

# SCSI Controllers
device  ahb # EISA AHA1742 family
device  ahc # AHA2940 and onboard AIC7xxx devices
device  ahd # AHA39320/29320 and onboard AIC79xx devices
device  amd # AMD 53C974 (Tekram DC-390(T))
device  isp # Qlogic family
device  mpt # LSI-Logic MPT-Fusion
#device ncr # NCR/Symbios Logic
device  sym # NCR/Symbios Logic (newer chipsets + those of 
`ncr')
device  trm # Tekr

Re: FreeBSD IO Performance (was Re: Quality of FreeBSD)

2005-07-25 Thread Mark Kirkwood
Hmm - looks like I missed that thread, never mind - repeatability of 
findings is sound scientific principle :-)


With respect to changing the default for vfs.read_max - makes sense to 
me, but it would be interesting to know if anyone has a system that 
performs *worse* with it set to 16.


regards

Mark

Chris wrote:

Its been mentioned before and most experience the same as you by
setting it to 16 a dramatic improvement in the sequential read, I
currently run all my 5.x servers like this with no issues as a result.
 I am curious if the default will ever be changed.



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Machine Replication

2005-07-25 Thread Marc Olzheim
On Sat, Jul 23, 2005 at 08:43:00AM +0100, Dick Davies wrote:
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/pxe/article.html

Heheh...
This needs updating; only 2 of the vnconfig references have been updated
to mdconfig.

Marc


pgpYywe8nwJob.pgp
Description: PGP signature


Re: Nero problem [was: (no subject)]

2005-07-25 Thread Warren
On Mon, 25 Jul 2005 5:59 pm, Martin Moeller wrote:
> * Daniel Evans <[EMAIL PROTECTED]> [25-07-2005 00:46:14 -0700]:
> > The unit does not seem to work with NERO with this format.
> > I copied the CDA files to my hard drive, and then tried to load them in
> > to Nero to make an audio CD. Nero states the drive does not work with CDA
> > files.
>
> Hello Daniel,
>
> you're probably asking this question on the wrong mailing list, since
> this list discusses FreeBSD, and NERO is a Windows program.

There is a version of Nero that works for Linux called 
NeroLinux(http://www.nero.com/en/NeroLINUX.html) either way though it is the 
wrong list.
-- 
Yours Sincerely
Shinjii
http://www.shinji.nq.nu
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Quality of FreeBSD

2005-07-25 Thread Claus Guttesen
> >How come the ATA code which was very stable in 4.x was screwed with in a
> >production release, breaking it, with no path backwards to the working
> >code?
> >
> I had not ANY problems with ATA on several mothersboards, both SMP and
> uniproc.

I must say that I have had few problems using FreeBSD as my main OS.
I've been using it as a nfs-server since the 5.2-alpha-days using a
compaq smartarray (ciss) and a qlogic 2300 hba (isp) serving some TB
of data. It was *rock-solid*. Longest uptime was 171 days when I tool
it down for maintenance. I phased it out recently after almost two
years of very reliable service. I had problems using the qlogic-hba on
the amd64-port with 4 GB RAM on 5.4, and switched to the i386-port
where it was very stable.

Then I have 5.2 and 5.4 as a firewall (5.2 with ipfw/dummynet/ipf and
5.4 with pf) on ATA.

The webserver started out as 5.1 on ATA and SCSI (amr). The webservers
needed some tweaking to /boot/loader.conf, otherwise it would (re)boot
without any notice or message. Other than that it's been very stable,
only recently did I get some resettings on my em-onboard gb-nic on two
particular servers. The others run fine.

Then I use it as a samba- and imap-server and some troubleticketing.

I had very few problems, I don't consider myself *that* lucky but knew
that running alpha- and beta-versions of FreeBSD as a nfs-server was
not without risk. But testing over and over made me confident that it
was stable for my purpose.

I haven't had the need to enter the SATA-area except for one webserver
using a 3ware-card which was recommended by the vendor. This SATA-card
haven't given me any problems.

regards
Claus
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: Nero problem [was: (no subject)]

2005-07-25 Thread Martin Moeller
* Daniel Evans <[EMAIL PROTECTED]> [25-07-2005 00:46:14 -0700]:

> The unit does not seem to work with NERO with this format.
> I copied the CDA files to my hard drive, and then tried to load them in to 
> Nero to make an audio CD. Nero states the drive does not work with CDA files.

Hello Daniel,

you're probably asking this question on the wrong mailing list, since
this list discusses FreeBSD, and NERO is a Windows program.

-- 
Martin Moeller 

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: RELENG_6 scroll wheel

2005-07-25 Thread Marian Hettwer

Hi,

Jonguk Kim wrote:

Marian Hettwer wrote:


I think 'Option "Buttons" "5"' can help you.


nope, didn't do the trick. But thanks for the suggestion anyway :)

Strange thing though, same config worked under RELENG_5 without problems.



My mouse works under RELENG_6.

my ps:
imonu@/usr/my# ps ax | grep moused
  245  ??  Is 0:15.02 /usr/sbin/moused -p /dev/ums0 -t auto -I 
/var/run/moused.ums0.pid


Why don't you remove -z option?


Strange thing - it's working without -z in moused ...
I recall that -z was needed to enable the scroll wheel. Anyway, now it's 
working :)


thanks!

best regards,
Marian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


(no subject)

2005-07-25 Thread Daniel Evans
I noticed your post on this CD player/burner.
I am also having a problem with it.
I am just trying to copy audio files to make a CD however much of the
music I have tried to copy are in CDA format.
The unit does not seem to work with NERO with this format.
I copied the CDA files to my hard drive, and then tried to load them in to Nero 
to make an audio CD. Nero states the drive does not work with CDA files.
What is wrong with this
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: RELENG_6 scroll wheel

2005-07-25 Thread Jonguk Kim

Marian Hettwer wrote:

Hej jonguk,

Jonguk Kim wrote:


Marian Hettwer wrote:


from /etc/X11/xorg.conf
Section "InputDevice"
Identifier  "Mouse0"
Driver  "mouse"
Option  "Protocol" "auto"
Option  "Device" "/dev/sysmouse"




I think 'Option "Buttons" "5"' can help you.


nope, didn't do the trick. But thanks for the suggestion anyway :)

Strange thing though, same config worked under RELENG_5 without problems.


My mouse works under RELENG_6.

my ps:
imonu@/usr/my# ps ax | grep moused
  245  ??  Is 0:15.02 /usr/sbin/moused -p /dev/ums0 -t auto -I 
/var/run/moused.ums0.pid


Why don't you remove -z option?



best regards,
Marian
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"



___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"