Send freebsd-i386 mailing list submissions to
freebsd-i386@freebsd.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.freebsd.org/mailman/listinfo/freebsd-i386
or, via email, send a message with subject or body 'help' to
freebsd-i386-request@freebsd.org
You can reach the person managing the list at
freebsd-i386-owner@freebsd.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of freebsd-i386 digest..."
Today's Topics:
1. Re: i386/95993: Cyrix 5530 unable to map interrupt
(Kirill Yelizarov)
2. Re: kern/123731: [patch][fix][sysvsem] System V semaphores
cause unexpected hanging (gavin@FreeBSD.org)
3. i386/123734: Chipset VIA CX700 requires extra initialization
(Sergey Korsak)
4. Re: i386/94141: [iwi] iwi doesn't work on Acer Laptop
(matteo@FreeBSD.org)
5. Re: i386/98964: [iwi] iwi totally freezes system
(matteo@FreeBSD.org)
6. Re: i386/101135: [iwi] iwi goes up and down (matteo@FreeBSD.org)
----------------------------------------------------------------------
Message: 1
Date: Fri, 16 May 2008 12:50:03 GMT
From: Kirill Yelizarov <ykirill@yahoo.com>
Subject: Re: i386/95993: Cyrix 5530 unable to map interrupt
To: freebsd-i386@FreeBSD.org
Message-ID: <200805161250.m4GCo3OD022017@freefall.freebsd.org>
The following reply was made to PR i386/95993; it has been noted by GNATS.
From: Kirill Yelizarov <ykirill@yahoo.com>
To: bug-followup@FreeBSD.org
Cc: John Baldwin <jhb@freebsd.org>
Subject: Re: i386/95993: Cyrix 5530 unable to map interrupt
Date: Fri, 16 May 2008 05:15:17 -0700 (PDT)
I upgraded to 7.0 Stable and problem went away. Thanks for all the help!
>
> > --- John Baldwin <jhb@FreeBSD.org> wrote:
> > > Does this still happen on 6.3? It appears that
> > > ata(4) is still working ok.
> > >
> > > --
> > > John Baldwin
> >
> >
> >
>
------------------------------
Message: 2
Date: Fri, 16 May 2008 14:17:46 GMT
From: gavin@FreeBSD.org
Subject: Re: kern/123731: [patch][fix][sysvsem] System V semaphores
cause unexpected hanging
To: gavin@FreeBSD.org, freebsd-i386@FreeBSD.org,
freebsd-bugs@FreeBSD.org
Message-ID: <200805161417.m4GEHkfk030086@freefall.freebsd.org>
Synopsis: [patch][fix][sysvsem] System V semaphores cause unexpected hanging
Responsible-Changed-From-To: freebsd-i386->freebsd-bugs
Responsible-Changed-By: gavin
Responsible-Changed-When: Fri May 16 14:17:14 UTC 2008
Responsible-Changed-Why:
Not i386 specific
http://www.freebsd.org/cgi/query-pr.cgi?pr=123731
------------------------------
Message: 3
Date: Fri, 16 May 2008 16:45:45 GMT
From: Sergey Korsak <skif@1plus1.net>
Subject: i386/123734: Chipset VIA CX700 requires extra initialization
To: freebsd-gnats-submit@FreeBSD.org
Message-ID: <200805161645.m4GGjjdL056847@www.freebsd.org>
>Number: 123734
>Category: i386
>Synopsis: Chipset VIA CX700 requires extra initialization
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-i386
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri May 16 16:50:00 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Sergey Korsak
>Release: 7.0-RELEASE
>Organization:
TV channel "Studio 1+1"
>Environment:
FreeBSD tiny.homenet 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
>Description:
I had got mini PC eBox-4854 made by DMP Electronics Inc. ( http://www.compactpc.com.tw/ebox-4854.htm ) and found onboard NIC (Realtek 8100B) and mini-PCI Wi-Fi module didn't work with errors:
rl0: watchdog timeout
and
ath0: ath_chan_set: unable to reset channel ...
Booting FreeBSD on another eBox-4854, playing with BIOS and sysctl settings, switching ACPI/APIC and compiling custom kernels didn't help.
OpenBSD 4.3 experienced the same problems.
But in Linux (fc7) both devices worked OK.
This box uses VIA CX700M chipset, so I grep-ped linux kernel sources and found interesting piece of code:
/*
* Disable PCI Bus Parking and PCI Master read caching on CX700
* which causes unspecified timing errors with a VT6212L on the PCI
* bus leading to USB2.0 packet loss. The defaults are that these
* features are turned off but some BIOSes turn them on.
*/
uint8_t b;
if (pci_read_config_byte(dev, 0x76, &b) == 0) {
if (b & 0x40) {
/* Turn off PCI Bus Parking */
pci_write_config_byte(dev, 0x76, b ^ 0x40);
dev_info(&dev->dev,
"Disabling VIA CX700 PCI parking\n");
}
}
if (pci_read_config_byte(dev, 0x72, &b) == 0) {
if (b != 0) {
/* Turn off PCI Master read caching */
pci_write_config_byte(dev, 0x72, 0x0);
/* Set PCI Master Bus time-out to "1x16 PCLK" */
pci_write_config_byte(dev, 0x75, 0x1);
/* Disable "Read FIFO Timer" */
pci_write_config_byte(dev, 0x77, 0x0);
dev_info(&dev->dev,
"Disabling VIA CX700 PCI caching\n");
}
}
Here dev is
vendor = 0x1106 'VIA Technologies Inc'
device = 0x324e 'CX700 Internal Module Bus'
class = 0x060000 'HOST-PCI bridge'
Being done on FreeBSD, these steps fix the problem till the next system boot.
>How-To-Repeat:
Boot FreeBSD on PC, based on VIA CX700* chipset. If BIOS doesn't initialize chipset correctly, like in my case, problem with some PCI devices using DMA transfer should appear.
>Fix:
I think BIOS developers but not OS developers must fix this problem. But as long as not all of them do it, it will be good to include this quirk in FreeBSD's kernel code. Anyway, there is my script /usr/local/etc/rc.d/cx700fix in the attach.
Patch attached with submission follows:
#!/bin/sh
# PROVIDE: cx700fix
# REQUIRE: FILESYSTEMS
# BEFORE: netif
. /etc/rc.subr
name="cx700fix"
start_cmd="reg_fix"
stop_cmd=":"
reg_fix()
{
if selector=`pciconf -l | sed -n '/chip=0x324e1106/{s/[[:blank:]].*//;p;}'` && [ -n "$selector" ]; then
b=`read_config_byte 0x76`
if [ $((b & 64)) -eq 64 ]; then
echo "Disabling VIA CX700 PCI parking"
write_config_byte 0x76 $((b ^ 64))
fi
if [ `read_config_byte 0x72` -ne 0 ]; then
echo "Disabling VIA CX700 PCI caching"
write_config_byte 0x72 0
write_config_byte 0x75 1
write_config_byte 0x77 0
fi
fi
return 0
}
read_config_byte() {
echo $(( 0x$(pciconf -rb $selector $1) ))
}
write_config_byte() {
pciconf -wb $selector $1 $2
}
run_rc_command "$1"
>Release-Note:
>Audit-Trail:
>Unformatted:
------------------------------
Message: 4
Date: Sat, 17 May 2008 10:05:34 GMT
From: matteo@FreeBSD.org
Subject: Re: i386/94141: [iwi] iwi doesn't work on Acer Laptop
To: lexa@wincmd.ru, matteo@FreeBSD.org, freebsd-i386@FreeBSD.org
Message-ID: <200805171005.m4HA5Ytc084290@freefall.freebsd.org>
Synopsis: [iwi] iwi doesn't work on Acer Laptop
State-Changed-From-To: open->feedback
State-Changed-By: matteo
State-Changed-When: Sab 17 Mag 2008 10:04:51 UTC
State-Changed-Why:
Can you experience this problem on newer FreeBSD version too?
http://www.freebsd.org/cgi/query-pr.cgi?pr=94141
------------------------------
Message: 5
Date: Sat, 17 May 2008 10:06:20 GMT
From: matteo@FreeBSD.org
Subject: Re: i386/98964: [iwi] iwi totally freezes system
To: jakub.laszczynski@gmail.com, matteo@FreeBSD.org,
freebsd-i386@FreeBSD.org
Message-ID: <200805171006.m4HA6KGw084341@freefall.freebsd.org>
Synopsis: [iwi] iwi totally freezes system
State-Changed-From-To: open->feedback
State-Changed-By: matteo
State-Changed-When: Sab 17 Mag 2008 10:05:45 UTC
State-Changed-Why:
Can you experience this problem on newer FreeBSD versions too?
http://www.freebsd.org/cgi/query-pr.cgi?pr=98964
------------------------------
Message: 6
Date: Sat, 17 May 2008 10:06:45 GMT
From: matteo@FreeBSD.org
Subject: Re: i386/101135: [iwi] iwi goes up and down
To: id4you@gmail.com, matteo@FreeBSD.org, freebsd-i386@FreeBSD.org
Message-ID: <200805171006.m4HA6jJl084391@freefall.freebsd.org>
Synopsis: [iwi] iwi goes up and down
State-Changed-From-To: open->feedback
State-Changed-By: matteo
State-Changed-When: Sab 17 Mag 2008 10:06:32 UTC
State-Changed-Why:
Can you experience this problem on newer FreeBSD versions too?
http://www.freebsd.org/cgi/query-pr.cgi?pr=101135
------------------------------
_______________________________________________
freebsd-i386@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-i386
To unsubscribe, send any mail to "freebsd-i386-unsubscribe@freebsd.org"
End of freebsd-i386 Digest, Vol 264, Issue 5
********************************************
