Re: ncplogin panic

2006-08-10 Thread m . ehinger
Antony Mawer <[EMAIL PROTECTED]> schrieb am 09.08.2006 02:08:20:


> Okay. What version of Netware are you using? What are the step-by-step
> procedures you are following in order to reproduce this (from step 1 as
> logging in to Netware or mounting the volume)?


We're using Netware Verion 6.5 over TCP/IP only.

Step 1. load ncp.ko, mount volume (mount_nwfs -A ... )
Step 2. cp /netwarefile /localfolder

Here is what strace gives me:

Script started on Thu Aug 10 10:02:46 2006
execve(0xbfbfe828, [0xbfbfed0c], [/* 0 vars */]) = 0
mmap(0, 3904, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x28074000
munmap(0x28074000, 3904)= 0
__sysctl([...], 0x28070b98, 0xbfbfeab4, NULL, 0) = 0
mmap(0, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0x28074000
issetugid(0)= 0
open("/etc/libmap.conf", O_RDONLY)  = -1 ENOENT (No such file or directory)
open("/var/run/ld-elf.so.hints", O_RDONLY) = 3
read(3, "_ALL\0%s:\n\0\t%o => %p (%x)\n\0\t%o (%"..., 128) = 128
lseek(3, 128, SEEK_SET) = 128
read(3, "/lib:/usr/lib:/usr/lib/compat:/u"..., 188) = 188
close(3)= 0
access("/lib/libc.so.6", F_OK)  = 0
open("/lib/libc.so.6", O_RDONLY)= 3
fstat(3, {st_mode=0, st_size=0, ...})   = 0
read(3, "\177ELF\1\1\1\t\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200\352"..., 4096) = 
4096
mmap(0, 937984, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_NOCORE, 3, 0) = 0x2807c000
mprotect(0x28144000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC) = 0
mprotect(0x28144000, 4096, PROT_READ|PROT_EXEC) = 0
mmap(0x28145000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 
0xc9000) = 0x28145000
mmap(0x2814b000, 90112, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANON, 
-1, 0) = 0x2814b000
close(3)= 0
sysarch(0xa, 0xbfbfeb30)= 0
mmap(0, 584, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x28161000
munmap(0x28161000, 584) = 0
mmap(0, 22792, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0) = 0x28161000
munmap(0x28161000, 22792)   = 0
sigprocmask(SIG_BLOCK, ~[ILL TRAP ABRT EMT FPE BUS SEGV SYS], []) = 0
sigprocmask(SIG_SETMASK, [], NULL)  = 0
syscall_416(0x1d, 0xbfbfeaf0, 0xbfbfead0) = 0
stat("/root", {st_mode=0, st_size=4294967297, ...}) = 0
umask(0777) = 022
umask(022)  = 0777
readlink("/etc/malloc.conf", "°Ë", 63)  = 2
issetugid(0x2806f598)   = 0
mmap(0, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANON, -1, 0) = 0x28161000
break(0x805d000)= 0
break(0x805e000)= 0
break(0x805f000)= 0
break(0x806)= 0
stat("file", {st_mode=S_IFREG|0755, st_size=12, ...}) = 0
stat("/root/file", {st_mode=0, st_size=4294967297, ...}) = 0
open("file", O_RDONLY)  = 3
open("/root/file", O_WRONLY|O_TRUNC)= 4
mmap(0, 12, PROT_READ, MAP_SHARED, 3, 0) = -1 EINVAL (Invalid argument)
write(2, "\0\0\0\0", 4cp: ) = 4
write(2, "\0\0\0\0", 4file) = 4
write(2, ": ", 2: )   = 2
write(2, "\0: path too long\n", 17Invalid argument
) = 17
close(3)= 0
close(4)= 0
exit(1) = ?

Script done on Thu Aug 10 10:02:46 2006

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


amd64 cannot boot on ASUS M2N-E

2006-08-10 Thread Angelo Turetta
The motherboard (BIOS rev.0203) is based on the nVidia MCP55 chipset, 
AMD64 3500+ (2200 MHz), 1 GB DDR553, two SATA2 Maxtor 80GB, DVD-R Samsung.


Trying to boot the latest snapshot 6.1-STABLE-200608-amd64, the kernel 
probes most peripherals (the Marvel gigabit-ethernet is not detected, 
but that's a known item), but just after reporting acd0 it hangs solid 
with the IDE led on. No panic, nor errors.
It seems related to the detection of the disks (they are not reported). 
I even left it in that state the whole night (just in case it was some 
lng timeout), but nothing.
The -i386 image exhibits the same exact behaviour. Booting without ACPI 
does not solve.


7.0-CURRENT-200608-amd64 boots fine (no Marvel gbit, of course).

What should I try next?

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


6-stable locking problem

2006-08-10 Thread Pavel Merdin
Hello.

There's  a problem with a very busy server (ad server, CPU is close to
0% idle most of the time).
Configuration: Dual AMD Opteron 252 2.6GHz
Chipset: AMD 8131
Integrated LAN Controller: Broadcom BCM5704 dual-channel GbE Gigabit
Adaptec AIC-7902W Ultra 320 SCSI controller
amr0: 

We tried both 6.1-RELEASE and 6-STABLE amd64 kernels. (bge driver is
always from recent stable with full Broadcom support).

The  server hangs one or more times a day. It even hangs for some time
right  after  boot  sequence  finishes  (when "login:" prompt occurs).
During  a hang everything stops, even keyboard (interrupts).

We already removed PREEMPTION and linux support.
Sometimes the server can panic with:
  Sleeping thread (tid 16, pid 4) owns a non-sleepable lock
  panic: sleeping thread
  cpuid=0
  KDB: enter: panic
and hangs there without even starting a debugger.
pid 4 seems to be [g_down]

Today I compiled a kernel with INVARIANTS and WITTNESS.
Right after booting sequence I got the following:

Aug 10 04:37:09 ad1 kernel: lock order reversal: (Giant after non-sleepable)
Aug 10 04:37:09 ad1 kernel: 1st 0xff026c4ebe70 AMR List Lock (AMR List 
Lock) @ dev/amr/amr.c:403
Aug 10 04:37:09 ad1 kernel: 2nd 0x8073adc0 Giant (Giant) @ 
vm/vm_contig.c:579
Aug 10 04:37:09 ad1 kernel: KDB: stack backtrace:
Aug 10 04:37:09 ad1 kernel: kdb_backtrace() at kdb_backtrace+0x37
Aug 10 04:37:09 ad1 kernel: witness_checkorder() at witness_checkorder+0x6fb
Aug 10 04:37:09 ad1 kernel: _mtx_lock_flags() at _mtx_lock_flags+0x9a
Aug 10 04:37:09 ad1 kernel: contigmalloc() at contigmalloc+0x57
Aug 10 04:37:09 ad1 kernel: alloc_bounce_pages() at alloc_bounce_pages+0x75
Aug 10 04:37:09 ad1 kernel: bus_dmamap_create() at bus_dmamap_create+0x149
Aug 10 04:37:09 ad1 kernel: amr_alloccmd_cluster() at amr_alloccmd_cluster+0x102
Aug 10 04:37:09 ad1 kernel: amr_alloccmd() at amr_alloccmd+0x55
Aug 10 04:37:09 ad1 kernel: amr_bio_command() at amr_bio_command+0x27
Aug 10 04:37:09 ad1 kernel: amr_startio() at amr_startio+0x6a
Aug 10 04:37:09 ad1 kernel: amr_submit_bio() at amr_submit_bio+0x51
Aug 10 04:37:09 ad1 kernel: amrd_strategy() at amrd_strategy+0x23
Aug 10 04:37:09 ad1 kernel: g_disk_start() at g_disk_start+0x17d
Aug 10 04:37:09 ad1 kernel: g_io_schedule_down() at g_io_schedule_down+0x189
Aug 10 04:37:09 ad1 kernel: g_down_procbody() at g_down_procbody+0x80
Aug 10 04:37:09 ad1 kernel: fork_exit() at fork_exit+0xdf
Aug 10 04:37:09 ad1 kernel: fork_trampoline() at fork_trampoline+0xe
Aug 10 04:37:09 ad1 kernel: --- trap 0, rip = 0, rsp = 0xb8e8bd00, rbp 
= 0 ---

Any advice (except suggestion of switching to Linux) ?

-- 
/ Pavel Merdin
Fotki Inc.

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


Re: error: syntax error before "_X_SENTINEL"

2006-08-10 Thread Norberto Meijome
On Thu, 10 Aug 2006 03:25:47 -0700
"Chris H." <[EMAIL PROTECTED]> wrote:

> Then I built the entire Xorg-6.9 server and libraries from source.
> Everything worked/ performed as expected. I have not made anything
> that required XFree86 (and friends) - it's purely Xorg.
> But recently, I am recieving the error(s) mentioned /every/ time
> I build anything that depends on GTK - /anything/. That's why I
> was sure there is an issue in the GTK/GD source as provided in the
> ports tree. I have no difficulties with anything unless GTK is involved.

fair enough. please keep in mind that I would have installed those packages for
a reason (other than because I felt like it...) ... from memory, it was some
dependency that didnt work out well and I installed it (obviously wrongly).

what packages have you got installed, btw? 

pkg_info | grep -i x

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


Re: error: syntax error before "_X_SENTINEL"

2006-08-10 Thread Chris H.

Hello, and thank you for your reply.

Quoting Norberto Meijome <[EMAIL PROTECTED]>:


On Wed, 09 Aug 2006 21:24:36 -0700
"Chris H." <[EMAIL PROTECTED]> wrote:


Hello Mark, and thank you for your prompt reply.

Quoting Mark Kirkwood <[EMAIL PROTECTED]>:

> Chris H. wrote:
>> Hello,
>> I just recenlly found that I am almost always unable to
>> build X (Xorg) related applications on a 5.5 box that has
>> pretty recent source. The applications all die during the
>> make process with the following error:
>> error: syntax error before "_X_SENTINEL"
>> Any to fix this? Googling indicates that this is a common
>> problem without a solution.
>>
>> System runs Xorg 6.9.
>>
>> Thank you for all your time and consideration.
>>
>
> I saw this:
>
> 
http://support.zenwalk.org/index.php?PHPSESSID=84b9cfbdfe961f45c90c7c47960b2268&topic=2134.msg11956

>
> Might be worth a try.

Yes, I caught the thread on that board. But didn't find the solution you
provided. Thanks! That was the /magic/ required to stop the whining offender
(gdkx.h). After some more research and investigation, this anomoly
appears to be a GTK/GD issue, and not X. I'm trying to figure out how to
get this #ifdef hack sucked in globally for the gtk/gd environment. I'm
/pretty/ sure gdkx.h will probably cover it. But would rather have it
sucked in from a seperate file. So as to not contaminate the actual header
file. I've cc'd the ports list, in hopes there is a better solution and
(even better) a newer version that resolves this problem.



Hi all,
interesting this is appearing ... I had this problem around 23rd of 
march on my
laptop running 6-STABLE at the time. I am not sure if this is the 
*same* issue,

BUT I think it went like this...

xproto's makefile says it conflicts with xorg-libraries-*
CONFLICTS=  XFree86-libraries-* xorg-libraries-*

i think that I had installed by hand one of the X lib-packages and that had
made the whole problem. conflicting libraries and include files. I 
removed all

the extra Xfree86 libs and Xorg, reinstalled Xorg and that was it.

I am not saying this is your problem... but it may be worth a try.

Xfree86 lib-packages that were installed in my system at the time:
libX11
libXau
libXcursor
libXdmcp
libXfixes
libXrender
xextensions
xproto

They definitely install files (under include and lib/ ) that xorg provides.


Thank you for your suggestion. But if I understand you correctly, I don't
think that I fall into this catagory. I installed with the Source Developer
option from the CD (no X, no Games). Then performed:

cvsup -g -L 2 /root/stable-src-supfile && \
cvsup -g -L 2 /root/ports-supfile && portsdb -uU && pkgdb -F

Then edited: /usr/sys/i386/conf/generic and saved to my custom config.
Performed a make buildworld,
make buildkernel
make installkernel
etc, etc...

Then I built the entire Xorg-6.9 server and libraries from source.
Everything worked/ performed as expected. I have not made anything
that required XFree86 (and friends) - it's purely Xorg.
But recently, I am recieving the error(s) mentioned /every/ time
I build anything that depends on GTK - /anything/. That's why I
was sure there is an issue in the GTK/GD source as provided in the
ports tree. I have no difficulties with anything unless GTK is involved.

Thanks again for your response.

--Chris




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





--
panic: kernel trap (ignored)



-
FreeBSD 5.4-RELEASE-p12 (SMP - 900x2) Tue Mar 7 19:37:23 PST 2006
/

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


Re: Network often not responding

2006-08-10 Thread Dominic Marks

Stanislaw Halik wrote:

On Wed, Aug 09, 2006, Dominic Marks wrote:

Aug  9 15:09:16 cache kernel: xl0: transmission error: 90
Aug  9 15:09:16 cache kernel: xl0: tx underrun, increasing tx start 
threshold to 120 bytes



dc%d: TX underrun -- increasing TX threshold  The device generated a
transmit underrun error while attempting to DMA and transmit a packet.
This happens if the host is not able to DMA the packet data into the

  

NIC's FIFO fast enough.  The driver will dynamically increase the

  ~~

trans- mit start threshold so that more data must be DMAed into the
FIFO before the NIC will start transmitting it onto the wire."



So it would seem like the card cannot keep pace with the system. What NICs

~

have you tried?


Basing on the quoted text, isn't it the opposite?



Yep! I should read more than the first line on things, especially when 
quoting

them to others :)

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


Re: Network often not responding

2006-08-10 Thread Akhmad Sakirun
I little bit frustated
after getting no luck with Pyun YongHyeon patch, i run cvsup today and
going to see what happen tomorrow.
It's happen only on bussy hour/work hour but not on afternoon until
morning. it's mean only happen when on maximum/heavy traffic load.
I suspected it's error on motherboard or the system.

now i'm using 2 ethernet using 2 different catalyst switch and 2 different 
network.
1st ethernet:

em0:  port 0xa800-0xa83f 
mem 0xfeaa-0xfeab,0xfea8-0xfea9 irq 18 at device 3.0 on pci2
em0: Ethernet address: 00:e0:81:31:af:ca
em0: [FAST]

2nd ethernet:
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xa880-0xa8ff mem 
0xfeafec00-0xfeafec7f irq 19 at device 7.0 on pci2
miibus0:  on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
xl0: Ethernet address: 00:10:5a:0d:c1:45

Best regards,

Thursday, August 10, 2006, 8:08:45 PM, Dominic wrote:
> Stanislaw Halik wrote:
>> On Wed, Aug 09, 2006, Dominic Marks wrote:
 Aug  9 15:09:16 cache kernel: xl0: transmission error: 90
 Aug  9 15:09:16 cache kernel: xl0: tx underrun, increasing tx start
 threshold to 120 bytes
>> 
>>> dc%d: TX underrun -- increasing TX threshold  The device generated a
>>> transmit underrun error while attempting to DMA and transmit a packet.
>>> This happens if the host is not able to DMA the packet data into the
>>  
>> 
>>> NIC's FIFO fast enough.  The driver will dynamically increase the
>>   ~~
>>> trans- mit start threshold so that more data must be DMAed into the
>>> FIFO before the NIC will start transmitting it onto the wire."
>> 
>>> So it would seem like the card cannot keep pace with the system. What NICs
>> ~
>>> have you tried?
>> 
>> Basing on the quoted text, isn't it the opposite?
>> 

> Yep! I should read more than the first line on things, especially when
> quoting
> them to others :)

> Dom
> ___
> 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]"


Re: gzip is faster with -O3

2006-08-10 Thread Simon L. Nielsen
On 2006.08.09 17:53:01 -0500, Brooks Davis wrote:
> [...] Poul-Henning Kamp has a nice (if probably
> somewhat overkill for this case) writeup on doing benchmarking here:
> 
> http://lists.freebsd.org/pipermail/freebsd-current/2004-January/019595.html

It should be mentioned that this is in the Developers Handbook along
with some more tips/comments from Robert Watson:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/testing.html

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


Re: boot problem with ACPI disabled

2006-08-10 Thread John Baldwin
On Wednesday 09 August 2006 23:59, Ganbold wrote:
> Hi,
> 
> I've got fatal trap on Dell D620 laptop when I tried to boot with ACPI 
> disabled.

Yes, somehow the kernel goes off in the weeds while doing the PNPBIOS
scan.  Don't disable ACPI.

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


Re: Device conflict 3ware twe and CMedia sound card

2006-08-10 Thread Dominic Marks

John Baldwin wrote:

On Wednesday 09 August 2006 06:15, Dominic Marks wrote:

Hello,

I seem to have a device conflict on my desktop. When attempting to fsck 
a gstripe
volume attached via the twe card the system becomes 'choppy' and from 
looking
at systat (when it isn't frozen) the system is receiving about 300k 
interrupts per
second from the pcm device. If I leave the system in this state for a 
few minutes it

will do an instant-reset, presumably because it can't cope.

Verbose dmesg: http://goodforbusiness.co.uk/~dom/dmesg.boot

Specific parts:

twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 
0xdcb0-0xdcbf mem 0xdf00-0xdf7f irq 49 at device 13.0 on pci3

twe0: Reserved 0x10 bytes for rid 0x10 type 4 at 0xdcb0
ioapic2: routing intpin 1 (PCI IRQ 49) to vector 49
twe0: [GIANT-LOCKED]
twe0: AEN: 
twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048
twe0: Monitor ME7X 1.01.00.040, PCB Rev5, Achip 3.20, Pchip 1.30-66
twe0: port 0: WDC WD3200KS-00PFB0  305245MB
twe0: port 1: WDC WD3200KS-00PFB0  305245MB

pcm0:  port 0xcc00-0xccff irq 17 at device 13.0 on pci7
pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xcc00
ioapic0: routing intpin 17 (PCI IRQ 17) to vector 55
pcm0: [MPSAFE]
pcm0: sndbuf_setmap 3e8ee000, 4000; 0xe5408000 -> 3e8ee000
pcm0: sndbuf_setmap 3e8ea000, 4000; 0xe540c000 -> 3e8ea000

I believe I can use device.hints(5) to work around this, but I am unsure 
variable I can
set in order to resolve this. Does the device 13.0 from dmesg refer to 
the 'drq' ?


Does this system have an Intel PCI-X host bridge in it?  If so, it's
probably due to brain damage in that chip.  You might be able to work
around it by making twe0 use the same IRQ as pcm0 by adding the
following hint:


I've had a look, I don't exactly know what to look for, but I have 
several PCI Express to

PCI bridges:

[EMAIL PROTECTED]:0:0: class=0x060400 card=0x0044 chip=0x03298086 rev=0x00 
hdr=0x01

vendor   = 'Intel Corporation'
device   = '6700PXH PCI Express-to-PCI Express Bridge A'
class= bridge
subclass = PCI-PCI
[EMAIL PROTECTED]:0:2: class=0x060400 card=0x0044 chip=0x032a8086 rev=0x00 
hdr=0x01

vendor   = 'Intel Corporation'
device   = '6700PXH PCI Express-to-PCI Express Bridge B'
class= bridge
subclass = PCI-PCI

While looking through the pciconf -vl output I also noticed this error:

[EMAIL PROTECTED]:13:0: class=0x010400 card=0x100113c1 chip=0x100113c1 rev=0x01 
hdr=0x00

vendor   = '3ware Inc.'
device   = '7000/8000 series ATA-133 Storage Controller' **
class= mass storage
subclass = RAID

** This actually a SATA 150 Controller. Not a big deal, but still incorrect.


hint.pci3.13.INTA.irq=17

That should make twe0 use IRQ 17.



I doesn't seem to have had the desired effect:

> kenv | grep pci3
hint.pci3.13.INTA.irq="17"

> grep twe0 /var/run/dmesg.boot
twe0: <3ware Storage Controller. [...]> port 0xdcb0-0xdcbf mem 
0xdf00-0xdf7f irq 49 at device 13.0 on pci3


Thank you very much John. I'll keep on looking for a solution.

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


Re: Device conflict 3ware twe and CMedia sound card

2006-08-10 Thread John Baldwin
On Thursday 10 August 2006 11:27, Dominic Marks wrote:
> I've had a look, I don't exactly know what to look for, but I have 
> several PCI Express to
> PCI bridges:
> 
> [EMAIL PROTECTED]:0:2: class=0x060400 card=0x0044 chip=0x032a8086 
> rev=0x00 
> hdr=0x01
>  vendor   = 'Intel Corporation'
>  device   = '6700PXH PCI Express-to-PCI Express Bridge B'
>  class= bridge
>  subclass = PCI-PCI

You probably are hitting the condition I'm thinking of then.
 
> While looking through the pciconf -vl output I also noticed this error:
> 
> [EMAIL PROTECTED]:13:0: class=0x010400 card=0x100113c1 chip=0x100113c1 
> rev=0x01 
> hdr=0x00
>  vendor   = '3ware Inc.'
>  device   = '7000/8000 series ATA-133 Storage Controller' **
>  class= mass storage
>  subclass = RAID
> 
> ** This actually a SATA 150 Controller. Not a big deal, but still incorrect.

It's just a string in /usr/share/misc/pci_vendors, it has no effect on 
operation or anything in the kernel. :)

> > hint.pci3.13.INTA.irq=17
> > 
> > That should make twe0 use IRQ 17.
> > 
> 
> I doesn't seem to have had the desired effect:
> 
>  > kenv | grep pci3
> hint.pci3.13.INTA.irq="17"
> 
>  > grep twe0 /var/run/dmesg.boot
> twe0: <3ware Storage Controller. [...]> port 0xdcb0-0xdcbf mem 
> 0xdf00-0xdf7f irq 49 at device 13.0 on pci3

Erm, that should have worked.  Did you just do 'kenv' to set it or did you 
reboot and set it in the loader?  Also, what version are you running, and 
what revision of /sys/dev/pci/pci.c do you have?

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


RE: Re: Re: bce0: Error mapping mbuf into TX chain!

2006-08-10 Thread David Christensen
Scott,

> 
> What are you doing when this problem occurs?  Is it something 
> I can easily duplicate here?  When I tested the fix on 
> -CURRENT I used the following command suggested by Doug to 
> bring out the failure quickly:
> 
> ssh  "dd if=/dev/zero bs=1" > /dev/null
> 
> Does this same command fail for you too?
> 

I updated my RELENG_6 system to the tip and tried the same ssh 
command which you mentioned also failed on your system.  I couldn't
duplicate the problem at all.  Are you sure you are actually using 
the new code?  My system is reporting a different driver version
than yours (mine = 0.9.6, yours = 0.9.5):

bce0:  mem
0xdc00-0xddff irq 16 at device 0.0 on pci2
bce0: ASIC ID 0x57081020; Revision (B2); PCI-X 64-bit 133MHz
bce0: Ethernet address: 00:10:18:15:f6:96

Are you still having a problem?  Can you change the version number in
if_bce.c (bce_driver_version) and make sure the right driver is loading?

Dave

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


Re: amd64 cannot boot on ASUS M2N-E

2006-08-10 Thread Ruslan Ermilov
On Thu, Aug 10, 2006 at 12:55:15PM +0200, Angelo Turetta wrote:
> The motherboard (BIOS rev.0203) is based on the nVidia MCP55 chipset, 
> AMD64 3500+ (2200 MHz), 1 GB DDR553, two SATA2 Maxtor 80GB, DVD-R Samsung.
> 
> Trying to boot the latest snapshot 6.1-STABLE-200608-amd64, the kernel 
> probes most peripherals (the Marvel gigabit-ethernet is not detected, 
> but that's a known item), but just after reporting acd0 it hangs solid 
> with the IDE led on. No panic, nor errors.
> It seems related to the detection of the disks (they are not reported). 
> I even left it in that state the whole night (just in case it was some 
> lng timeout), but nothing.
> The -i386 image exhibits the same exact behaviour. Booting without ACPI 
> does not solve.
> 
> 7.0-CURRENT-200608-amd64 boots fine (no Marvel gbit, of course).
> 
> What should I try next?
> 
You need ata-chipset.c from -CURRENT, or wait for fix to be merged.

: revision 1.166
: date: 2006/07/24 10:44:50;  author: sos;  state: Exp;  lines: +47 -34
: Finally fix support for the newer MCP51/MCP55 nVidia chipsets.
: The register layout has changed since the original NV4 - sigh.
: Hotplug support has been fixed for all nVidia chipsets that supports it
: (including the MCP51/55).
: 
: HW donated by: Kingsley College


Cheers,
-- 
Ruslan Ermilov
[EMAIL PROTECTED]
FreeBSD committer


pgpp881CeZWBP.pgp
Description: PGP signature


Re: error: syntax error before "_X_SENTINEL"

2006-08-10 Thread Chris H.

Hello, and thank you for your reply.

Quoting Norberto Meijome <[EMAIL PROTECTED]>:


On Thu, 10 Aug 2006 03:25:47 -0700
"Chris H." <[EMAIL PROTECTED]> wrote:


Then I built the entire Xorg-6.9 server and libraries from source.
Everything worked/ performed as expected. I have not made anything
that required XFree86 (and friends) - it's purely Xorg.
But recently, I am recieving the error(s) mentioned /every/ time
I build anything that depends on GTK - /anything/. That's why I
was sure there is an issue in the GTK/GD source as provided in the
ports tree. I have no difficulties with anything unless GTK is involved.


fair enough. please keep in mind that I would have installed those 
packages for

a reason (other than because I felt like it...) ... from memory, it was some
dependency that didnt work out well and I installed it (obviously wrongly).


Sure. Understood.



what packages have you got installed, btw?

pkg_info | grep -i x


Script started on Thu Aug 10 15:24:22 2006
3ddesktop-0.2.9_1   3D Virtual Desktop Switcher

Gdtclft-2.2.5_4 A TCL interface to the Thomas Boutell's Gd library

GeoIP-1.3.17Find the country that any IP address or hostname 
originates


GraphicsMagick-1.1.6_1 Fast image processing tools based on ImageMagick

ImageMagick-6.2.8.5 Image processing tools

ORBit2-2.14.0_1 High-performance CORBA ORB with support for the C language

Sablot-1.0.2_1  XML toolkit implementing XSLT 1.0, XPath 1.0 and 
DOM Level2


WhistlerK-200010142358_2 A GTK theme engine inspired by the Windows Whistler

a2ps-a4-4.13b_3 Formats an ascii file for printing on a postscript printer

apache+ssl-1.3.34.1.57_1 Apache secure webserver integrating OpenSSL

arc-5.21o   Create & extract files from DOS .ARC files

arj-3.10.22 Open-source ARJ

artwiz-fonts-1.0_1  A set of free fonts for X11 desktops

aspell-0.60.4_4 Spelling checker with better suggestion logic than ispell

aterm-1.0.0_1   A color vt102 terminal emulator with transparency support

atk-1.11.4_1A GNOME accessibility toolkit (ATK)

autoconf-2.13.000227_5 Automatically configure source code on many Un*x 
platforms


autoconf-2.53_3 Automatically configure source code on many Un*x platforms

autoconf-2.59_2 Automatically configure source code on many Un*x platforms

automake-1.4.6_2GNU Standards-compliant Makefile generator (1.4)

automake-1.9.6  GNU Standards-compliant Makefile generator (1.9)

bash-3.1.17 The GNU Project's Bourne Again SHell

bdc-7.0.1_2 BitDefender Console Antivirus for FreeBSD

bison-1.75_2,1  A parser generator from FSF, (mostly) compatible with Yacc

bitstream-vera-1.10_2 Bitstream Vera TrueType font collection

boxtools-0.70.1 Style tools for the blackbox family of window managers

buffy-0.2_2 A GTK theme engine looking like SGI enhanced Motif 
(aka Rox


bzip2-1.0.3_1   A block-sorting file compressor

cabextract-1.1  A program to extract Microsoft cabinet (.CAB) files

cairo-1.0.4_1   Vector graphics library with cross-device output support

cclient-2004g,1 Mark Crispin's C-client mail access routines

clean-theme-gtk-1.2.x_2 The Clean GTK theme engine

colorstep-0.6_2 A theme engine based on GtkStep and Step-pastel

compositeext-2.0_1  X Composite extension headers and specification

conky-1.4.2_1   An advanced, highly configurable system monitor for X

cracklib-2.7_2  Password-checking library

curl-7.15.4 Non-interactive tool to get files from FTP, GOPHER, 
HTTP(S)


cvsup-without-gui-16.1h_2 General network file distribution system 
optimized for CVS


dbh-1.0.24_1Disk Based Hashtables

deb2targz-20021217  A command-line utility for converting a Debian .deb 
file to


dovecot-1.0.r2  Secure and compact IMAP and POP3 servers

dynamite-0.1Decompress data compressed with PKWARE Data 
Compression Lib


edb-1.0.5.007   Enlightenment Database Library

eet-0.9.10.032  Enlightenment Data Handling Library

engradient-0.5_2A GTK+ engine-gradient theme based off of the 
IceGradient t


eterm-0.9.3_5   X11 terminal emulator based on rxvt/xterm

expat-2.0.0_1   XML 1.0 parser written in C

fastest_cvsup-0.2.9_4 Finds fastest CVSup server

fbpanel-4.3_3   A desktop panel that includes a taskbar, pager, 
launchbar a


filerunner-2.5.1_1  Filemanager with FTP capabilities. Uses Tcl/Tk

fixesext-2.0.1_1X Fixes extension headers and specification

fluxbox-0.1.14_2A small and fast window manager based on BlackBox

fluxspace-0.0.3_2   A window manager and workspace enhancer and integrator

fontconfig-2.3.2_5,1 An XML-based font configuration API for X Windows

freefont-ttf-20060126 Free UCS Outline Fonts

freefonts-0.10_2A collection of ATM fonts (not all free) from the 
CICA arch


freetype2-2.1.10_3  A free and portable TrueType font rendering engine

fvwm-2.5.16 Popular virtual window manager for X

gamin-0.1.7_2   A file and directory m

CFT: ipw driver update

2006-08-10 Thread Sam Leffler
If you use ipw please try a new version at:

http://www.freebsd.org/~sam/ipw-20060710.tgz

This code should work with wpa_supplicant, recognize beacon miss (i.e.
roam), implement the rfkill radio switch, etc.  It should work on both
HEAD and RELENG_6.

There are still some rough edges as the ipw firmware has some quirks but
I believe it's an improvement over what's in the tree.  Beware of bugs;
it's only been lightly tested.

Note that you'll need the ipw firmware packaged as modules.  This is the
way things are in HEAD but not RELENG_6.  The ipw-firmware-kmod port
currently won't allow installation on a RELENG_6 system; you'll need to
defeat the check in the Makefile to install the necessary firmware.

If you hit issues please try to collect a debug log by setting

sysctl debug.ipw=1

(or higher if needed); msgs go to the console.

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


Odd problem with Intel em driver

2006-08-10 Thread lnelson

Hi Everyone,

  I'm having an odd problem with the Intel em driver.  It's
built into the kernel by default, but it won't recognize
the part.

  However, if I grab the driver source from the Intel website,
compile it as a KLD, and put it in loader.conf, it works.
The odd thing is that it complains that it is already loaded,
and acts as if it is refusing to load the module.

  When it works, the message I get is:

module_register: module pci/em already exists!
Module pci/em failed to register: 17
...  ...
em0:  port 0x3000-0x301f 
mem 
0xc830-0xc831 i
rq 18 at device 0.0 on pci5
em0: Ethernet address: 00:30:48:78:5a:2a
em0:  Speed:N/A  Duplex:N/A
em1:  port 0x3020-0x303f 
mem 
0xc832-0xc833 i
rq 19 at device 0.1 on pci5
em1: Ethernet address: 00:30:48:78:5a:2b
em1:  Speed:N/A  Duplex:N/A

  When it doesn't work, I get no messages regarding
em at all.  

  It seems like the KLD is actually getting loaded, even
though it says it isn't.

  I should mention that I am running the amd64 port of
6.1 RELEASE.

  Any thoughts?  Can I run a production server like this?

  Thanks,

  Lee


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