conf/147054: gpsemill

[gpsemill]

>Number: 147054
>Category:   conf
>Synopsis:   gpsemill
>Confidential:   no
>Severity:   critical
>Priority:   high
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  maintainer-update
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 26 10:00:07 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: gpsemill
>Release:gpsemill
>Organization:
gpsemill
>Environment:
gpsemill
>Description:
 [URL=http://ytknhgiz.com]tsiemnhz[/URL]  ezgtxyea http://eejdofzv.com ckzdfvof 
cpcttfzx  http://hlowlckl.com";>kzjwpalt 
>How-To-Repeat:
gpsemill
>Fix:
gpsemill

>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

kern/147063: zojerkth

[zojerkth]

>Number: 147063
>Category:   kern
>Synopsis:   zojerkth
>Confidential:   no
>Severity:   serious
>Priority:   medium
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  update
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 26 10:10:02 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: zojerkth
>Release:zojerkth
>Organization:
zojerkth
>Environment:
zojerkth
>Description:
rvjazfsn http://wyocpaat.com clivaife mkaebncv
>How-To-Repeat:
zojerkth
>Fix:
zojerkth

>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: junk/147054: gpsemill

[linimon]

Synopsis: gpsemill

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Wed May 26 14:17:15 UTC 2010
State-Changed-Why: 
spam run.

http://www.freebsd.org/cgi/query-pr.cgi?pr=147054
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: junk/147063: zojerkth

[linimon]

Synopsis: zojerkth

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Wed May 26 14:19:39 UTC 2010
State-Changed-Why: 
spam run.

http://www.freebsd.org/cgi/query-pr.cgi?pr=147063
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

misc/147082: Serial ports unusable

[Mayo Jordanov]

>Number: 147082
>Category:   misc
>Synopsis:   Serial ports unusable
>Confidential:   no
>Severity:   serious
>Priority:   medium
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 26 17:10:00 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Mayo Jordanov
>Release:RELENG_8_0, RELENG_8
>Organization:
>Environment:
FreeBSD test.local 8.1-PRERELEASE FreeBSD 8.1-PRERELEASE #0: Tue May 25 
16:16:39 PDT 2010 r...@test.local:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Trying to setup a terminal console on FreeBSD, I ran into problems where the 
console seems to be offline. I've hunted around and the problem may be related 
to getty and/or uart.

First, I've enabled serial console in /etc/ttys modifying the ttyu0 line to be:
ttyu0   "/usr/libexec/getty std.9600"   vt100   on secure

checking ps axl, it seems that ttyu0 remains in ttydtd.

Any attempt to talk on that serial line failed. Following that, the setup was 
changed to
ttyu0   "/usr/libexec/getty 3wire.9600" vt100   on secure

after the change to 3wire, the 3wire consoles are in ttyin wait state.

That did not get me very far, as almost nothing would make it through to/from 
the console. However, going through different configurations, I've noticed 
sometimes when I did `kill -HUP 1`, few characters would make is over to the 
machine running terminal application. Also, with the 3wire setup, plugging in 
and unplugging USB devices, the messages generated by kernel when a device gets 
plugged and uplugged would make it over to the listening machine.

Also, at some point I enabled all 4 ttyu consoles (the machine has 4 com 
ports), and changing all from std.9600 to 3wire.9600 followed by `kill -HUP 1` 
would only update ttyu0, having to kill ttyu{1,2,3} manually.

Next, I've changed loader.conf and boot.config to run over serial. In this 
case, there are no problems, and everything including the boot loader is 
visible over the serial up to the point where getty (presumably) is started. 
Following this, running shutdown/reboot, the serial terminal is re-activated at 
some point and I see the tail-end of the shutdown messages over serial terminal 
as well.

Next, I've tried simple experiment of connecting just two serial terminals 
together. Text written on the machine that works never made it to the FreeBSD, 
and vice versa. When the two machines were connected, checking status of the 
serial line in kermit on at the terminal application resulsts in:
 Device: /dev/cu.KeySerial1
Speed 9600
 Terminal echo: remote
 Terminal bytesize: 8
 Command bytesize: 8
 Parity: none
 Autodownload: on
 Session log: (none)
 Carrier Detect  (CD):  Off
 Dataset Ready   (DSR): On
 Clear To Send   (CTS): On
 Ring Indicator  (RI):  Off
 Data Terminal Ready (DTR): On
 Request To Send (RTS): On


and on the FreeBSD side resulsts in:
 Device: /dev/cuau3
Speed 9600
 Terminal echo: remote
 Terminal bytesize: 8
 Command bytesize: 8
 Parity: none
 Autodownload: on
 Session log: (none)
 Carrier Detect  (CD):  Off
 Dataset Ready   (DSR): Off
 Clear To Send   (CTS): Off
 Ring Indicator  (RI):  Off
 Data Terminal Ready (DTR): On
 Request To Send (RTS): On


Please note that the machine used to test against the FreeBSD machine is known 
to work with serial terminals on number of computers and devices. I've also 
tried using secondary machine with same results.

I've tried number of terminal appications, including cu, minicom, kermit, and 
screen. Kermit settings were:
set port /dev/cuauX
set speed 9600
set carrier-watch off
set flow-control none

As for hardware information on the machine, it is Advantech ARK-3360. The 
serial ports are detected as:
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: [FILTER]
uart0: console (9600,n,8,1)
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart1: [FILTER]
uart2: <16550 or compatible> port 0x3e8-0x3ef irq 11 on acpi0
uart2: [FILTER]
uart3: <16550 or compatible> port 0x2e8-0x2ef irq 10 on acpi0
uart3: [FILTER]


>How-To-Repeat:
1) Edit /etc/ttys, do the ttyu0 line reads:
ttyu0   "/usr/libexec/getty std.9600"   vt100   on secure
2) kill -HUP 1
3) Try connecting to it with terminal application

OR
Connect two machines with a serial cable, run terminal application on both. 
Typing in one should show up on the other.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

kern/147086: AHCI not being enabled on PC

[Ryan Holt]

>Number: 147086
>Category:   kern
>Synopsis:   AHCI not being enabled on PC
>Confidential:   no
>Severity:   serious
>Priority:   medium
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 26 17:30:13 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Ryan Holt
>Release:8.0-Stable-201004
>Organization:
>Environment:
FreeBSD fs.holthome.local 8.0-STABLE-201004 FreeBSD 8.0-STABLE-201004 #0: Mon 
Apr  5 15:59:06 UTC 2010 
r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64
>Description:
Hello,

I've got a fresh install of FreeBSD 8.0-Stable-201004 built on a Gigabyte 
GA-K8U-754 Motherboard 
(http://www.gigabyte.com.tw/Products/Motherboard/Products_Spec.aspx?ProductID=1876).
 The boot drives are plugged directly into the Motherboard's SATA ports, which 
I believe is powered by a ULi M1689 chipset. I also have a Supermicro 
AOC-SAT2-MV8 PCI-X HBA card 
(http://www.supermicro.com/products/accessories/addon/AOC-SAT2-MV8.cfm) which 
has a Hercules-2 Rev. C0 SATA host controller built in. I've added 
ahci_load="YES" in my /boot/loader.conf and I can see that ahci.ko was loaded 
using klstat, but I do not see any drives appearing that use the ahci module. 
All drives are labeled /dev/ad* instead of /dev/ada* and hotswap doesn't work 
properly. Running dmesg |grep -i ahci comes back empty.
>How-To-Repeat:
1. Boot computer
2. Run dmesg |grep -i ahci
3. Unplug drive, watch PC kernel panic
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147086: AHCI not being enabled on PC

[Alexander Motin]

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

From: Alexander Motin 
To: Ryan Holt 
Cc: Garrett Cooper , bug-follo...@freebsd.org
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 21:38:20 +0300

 Ryan Holt wrote:
 >> I've got a fresh install of FreeBSD 8.0-Stable-201004 built on a Gigabyte 
 >> GA-K8U-754 Motherboard. The boot drives are plugged directly into the 
 >> Motherboard's SATA ports, which I believe is powered by a ULi M1689 
 >> chipset. I also have a Supermicro AOC-SAT2-MV8 PCI-X HBA card which has a 
 >> Hercules-2 Rev. C0 SATA host controller built in. I've added 
 >> ahci_load="YES" in my /boot/loader.conf and I can see that ahci.ko was 
 >> loaded using klstat, but I do not see any drives appearing that use the 
 >> ahci module. All d rives are labeled /dev/ad* instead of /dev/ada* and 
 >> hotswap doesn't work properly. Running dmesg |grep -i ahci comes back empty.
 
 I can't say about ULi SATA - I haven't tried any of them. Make sure that
 you have AHCI mode enabled in BIOS. ahci(4) driver should attach to any
 hardware that reporting AHCI compatibility via PCI class/subclass.
 
 Supermicro AOC-SAT2-MV8 - is not AHCI compatible. New driver for it
 named mvs(4). It was merged to 8-STABLE just a few weeks ago. You may
 update your system and try it.
 
 -- 
 Alexander Motin
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147086: AHCI not being enabled on PC

[r...@ryanholt.net]

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

From: "r...@ryanholt.net" 
To: Garrett Cooper 
Cc: Alexander Motin , bug-follo...@freebsd.org
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 14:56:37 -0400 (EDT)

 --=_Part_46482_1005083949.1274900197056
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Hi Garrett,
 =C2=A0
 How can I get the device IDs? pciconf?
 =C2=A0
 
 [r...@fs /usr/src]# pciconf -lv
 hos...@pci0:0:0:0: =C2=A0 =C2=A0 =C2=A0class=3D0x06 card=3D0x50001458 c=
 hip=3D0x168910b9 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ULi M1689 K8 Northbridge with =
 AGP and hypertransport'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D HOST-PCI
 pc...@pci0:0:1:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x060400 card=3D0x c=
 hip=3D0x524610b9 rev=3D0x00
 hdr=3D0x01
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ULi AGP 3.0 Controller'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D PCI-PCI
 pc...@pci0:0:2:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x060401 card=3D0x c=
 hip=3D0x524910b9 rev=3D0x00
 hdr=3D0x01
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'HyperTransport to PCI Bridge (=
 M5249)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D PCI-PCI
 is...@pci0:0:3:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x060100 card=3D0x50011458 c=
 hip=3D0x156310b9 rev=3D0x70
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ALI M1563 South Bridge with Hy=
 pertransport Support'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D PCI-ISA
 no...@pci0:0:3:1: =C2=A0 =C2=A0 =C2=A0 class=3D0x068000 card=3D0x50031458 c=
 hip=3D0x710110b9 rev=3D0x00
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'ALI M7101 Power Management Con=
 troller'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D bridge
 no...@pci0:0:4:0: =C2=A0 =C2=A0 =C2=A0 class=3D0x040100 card=3D0xae011458 c=
 hip=3D0x545510b9 rev=3D0x20
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'AC'97 Audio Controller (M1563M=
  Southbridge)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D multimedia
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D audio
 atap...@pci0:0:14:0: =C2=A0 =C2=A0class=3D0x0101fa card=3D0x50021458 chip=
 =3D0x522910b9 rev=3D0xc7
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'EIDE Controller (M5229 Southbr=
 idge)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D mass storage
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D ATA
 atap...@pci0:0:14:1: =C2=A0 =C2=A0class=3D0x01018f card=3D0xb0031458 chip=
 =3D0x528910b9 rev=3D0x10
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'M5289 SATA/Raid controller (UL=
 I M1567/M1689 )'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D mass storage
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D ATA
 oh...@pci0:0:15:0: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0310 card=3D0x50041458 c=
 hip=3D0x523710b9 rev=3D0x03
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'OpenHCI 1.1 USB to =C2=A02.0 (=
 M5273 A1 for windows 98)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 oh...@pci0:0:15:1: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0310 card=3D0x50041458 c=
 hip=3D0x523710b9 rev=3D0x03
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'OpenHCI 1.1 USB to =C2=A02.0 (=
 M5273 A1 for windows 98)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 oh...@pci0:0:15:2: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0310 card=3D0x50041458 c=
 hip=3D0x523710b9 rev=3D0x03
 hdr=3D0x00
 =C2=A0=C2=A0 =C2=A0vendor =C2=A0 =C2=A0 =3D 'Acer Labs Incorporated (ALi/UL=
 i)'
 =C2=A0=C2=A0 =C2=A0device =C2=A0 =C2=A0 =3D 'OpenHCI 1.1 USB to =C2=A02.0 (=
 M5273 A1 for windows 98)'
 =C2=A0=C2=A0 =C2=A0class =C2=A0 =C2=A0 =C2=A0=3D serial bus
 =C2=A0=C2=A0 =C2=A0subclass =C2=A0 =3D USB
 eh...@pci0:0:15:3: =C2=A0 =C2=A0 =C2=A0class=3D0x0c0320 card=3D0x50041458 c=
 hip=3D0x523910b9 rev=3D0x01

Re: kern/147086: AHCI not being enabled on PC

[Alexander Motin]

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

From: Alexander Motin 
To: "r...@ryanholt.net" 
Cc: bug-follo...@freebsd.org, Garrett Cooper 
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 22:10:41 +0300

 r...@ryanholt.net wrote:
 > Will the MVS driver allow for any type of hot swap? It appears that when
 > I pull the drive out of any slot on the Supermicro card the kernel will
 > panic and system crash. Same thing with the on-board controller.
 
 mvs(4) provides almost the same set of features that ahci(4), just for
 different hardware. Hot swap should work fine.
 
 -- 
 Alexander Motin
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147086: AHCI not being enabled on PC

[r...@ryanholt.net]

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

From: "r...@ryanholt.net" 
To: Alexander Motin 
Cc: bug-follo...@freebsd.org, Garrett Cooper 
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 15:19:11 -0400 (EDT)

 --=_Part_47294_804650099.1274901551988
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 OK Great. Should I re-compile my kernel with mvs as a device option?
 =C2=A0
 Thanks,
 Ryan
 =C2=A0
 
 On May 26, 2010 at 7:10 PM Alexander Motin  wrote:
 
 > r...@ryanholt.net wrote:
 > > Will the MVS driver allow for any type of hot swap? It appears that whe=
 n
 > > I pull the drive out of any slot on the Supermicro card the kernel will
 > > panic and system crash. Same thing with the on-board controller.
 >
 > mvs(4) provides almost the same set of features that ahci(4), just for
 > different hardware. Hot swap should work fine.
 >
 > --
 > Alexander Motin
 --=_Part_47294_804650099.1274901551988
 MIME-Version: 1.0
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: 7bit
 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
 
 http://www.w3.org/1999/xhtml";>
   
 
 
   
 
   
 OK Great. Should I re-compile my kernel with mvs 
as a device option?
 
  
 
 Thanks,
 
 Ryan
 
  
 
 
   On May 26, 2010 at 7:10 PM Alexander Motin  
wrote:
   
   > r...@ryanholt.net wrote:
   > > Will the MVS driver allow for any type of hot swap? It appears 
that when
   > > I pull the drive out of any slot on the Supermicro card the 
kernel will
   > > panic and system crash. Same thing with the on-board 
controller.
   >
   > mvs(4) provides almost the same set of features that ahci(4), just 
for
   > different hardware. Hot swap should work fine.
   >
   > --
   > Alexander Motin
 
   
 
 
 --=_Part_47294_804650099.1274901551988--
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147086: AHCI not being enabled on PC

[r...@ryanholt.net]

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

From: "r...@ryanholt.net" 
To: Alexander Motin 
Cc: bug-follo...@freebsd.org, Garrett Cooper 
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 14:59:16 -0400 (EDT)

 --=_Part_46572_388073361.1274900356733
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 I'm assuming that the ULi doesn't have AHCI support as there's no option in=
  the
 BIOS for AHCI, only IDE and RAID.
 =C2=A0
 Will the MVS driver allow for any type of hot swap? It appears that when I =
 pull
 the drive out of any slot on the Supermicro card the kernel will panic and
 system crash. Same thing with the on-board controller.
 =C2=A0
 Thanks,
 Ryan
 =C2=A0
 
 On May 26, 2010 at 6:38 PM Alexander Motin  wrote:
 
 > Ryan Holt wrote:
 > >> I've got a fresh install of FreeBSD 8.0-Stable-201004 built on a Gigab=
 yte
 > >> GA-K8U-754 Motherboard. The boot drives are plugged directly into the
 > >> Motherboard's SATA ports, which I believe is powered by a ULi M1689
 > >> chipset. I also have a Supermicro AOC-SAT2-MV8 PCI-X HBA card which ha=
 s a
 > >> Hercules-2 Rev. C0 SATA host controller built in. I've added
 > >> ahci_load=3D"YES" in my /boot/loader.conf and I can see that ahci.ko w=
 as
 > >> loaded using klstat, but I do not see any drives appearing that use th=
 e
 > >> ahci module. All drives are labeled /dev/ad* instead of /dev/ada* and
 > >> hotswap doesn't work properly. Running dmesg |grep -i ahci comes back
 > >> empty.
 >
 > I can't say about ULi SATA - I haven't tried any of them. Make sure that
 > you have AHCI mode enabled in BIOS. ahci(4) driver should attach to any
 > hardware that reporting AHCI compatibility via PCI class/subclass.
 >
 > Supermicro AOC-SAT2-MV8 - is not AHCI compatible. New driver for it
 > named mvs(4). It was merged to 8-STABLE just a few weeks ago. You may
 > update your system and try it.
 >
 > --
 > Alexander Motin
 --=_Part_46572_388073361.1274900356733
 MIME-Version: 1.0
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: 7bit
 
 http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
 
 http://www.w3.org/1999/xhtml";>
   
 
 
   
 
   
 I'm assuming that the ULi doesn't have 
AHCI support as there's no option in the BIOS for AHCI, only IDE and 
RAID.
 
  
 
 Will the MVS driver allow for any type of hot 
swap? It appears that when I pull the drive out of any slot on the Supermicro 
card the kernel will panic and system crash. Same thing with the on-board 
controller.
 
  
 
 Thanks,
 
 Ryan
 
  
 
 
   On May 26, 2010 at 6:38 PM Alexander Motin  
wrote:
   
   > Ryan Holt wrote:
   > >> I've got a fresh install of FreeBSD 8.0-Stable-201004 
built on a Gigabyte GA-K8U-754 Motherboard. The boot drives are plugged 
directly into the Motherboard's SATA ports, which I believe is powered by a 
ULi M1689 chipset. I also have a Supermicro AOC-SAT2-MV8 PCI-X HBA card which 
has a Hercules-2 Rev. C0 SATA host controller built in. I've added 
ahci_load="YES" in my /boot/loader.conf and I can see that ahci.ko 
was loaded using klstat, but I do not see any drives ap pearing that use the 
ahci module. All drives are labeled /dev/ad* instead of /dev/ada* and hotswap 
doesn't work properly. Running dmesg |grep -i ahci comes back empty.
   >
   > I can't say about ULi SATA - I haven't tried any of them. 
Make sure that
   > you have AHCI mode enabled in BIOS. ahci(4) driver should attach to 
any
   > hardware that reporting AHCI compatibility via PCI 
class/subclass.
   >
   > Supermicro AOC-SAT2-MV8 - is not AHCI compatible. New driver for 
it
   > named mvs(4). It was merged to 8-STABLE just a few weeks ago. You 
may
   > update your system and try it.
   >
   > --
   > Alexander Motin
 
   
 
 
 --=_Part_46572_388073361.1274900356733--
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147086: AHCI not being enabled on PC

[Alexander Motin]

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

From: Alexander Motin 
To: "r...@ryanholt.net" 
Cc: bug-follo...@freebsd.org, Garrett Cooper 
Subject: Re: kern/147086: AHCI not being enabled on PC
Date: Wed, 26 May 2010 22:20:57 +0300

 r...@ryanholt.net wrote:
 > OK Great. Should I re-compile my kernel with mvs as a device option?
 
 As you wish. Module should also be fine.
 
 -- 
 Alexander Motin
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[remko]

Synopsis: [uart] Serial ports unusable

State-Changed-From-To: open->feedback
State-Changed-By: remko
State-Changed-When: Wed May 26 19:42:36 UTC 2010
State-Changed-Why: 
I send my working serial line to Mayo, set status to feedback

http://www.freebsd.org/cgi/query-pr.cgi?pr=147082
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/146647: Some PCIe seral/parallel boards with ID 9901 9710 don't work

[Garrett Cooper]

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

From: Garrett Cooper 
To: Tommy Johnson 
Cc: bug-follo...@freebsd.org
Subject: Re: kern/146647: Some PCIe seral/parallel boards with ID 9901 9710 
don't work
Date: Wed, 26 May 2010 13:51:05 -0700

 On Mon, May 17, 2010 at 10:37 PM, Garrett Cooper  wrote=
 :
 > On Sun, May 16, 2010 at 6:56 PM, Garrett Cooper  wrot=
 e:
 >> On Sun, May 16, 2010 at 6:47 PM, Garrett Cooper  wro=
 te:
 >>> On Sun, May 16, 2010 at 5:50 PM, Tommy Johnson  w=
 rote:
 
 >Number: =A0 =A0 =A0 =A0 146647
 >Category: =A0 =A0 =A0 kern
 >Synopsis: =A0 =A0 =A0 Some PCIe seral/parallel boards with ID 9901 971=
 0 don't work
 >Confidential: =A0 no
 >Severity: =A0 =A0 =A0 non-critical
 >Priority: =A0 =A0 =A0 low
 >Responsible: =A0 =A0freebsd-bugs
 >State: =A0 =A0 =A0 =A0 =A0open
 >Quarter:
 >Keywords:
 >Date-Required:
 >Class: =A0 =A0 =A0 =A0 =A0sw-bug
 >Submitter-Id: =A0 current-users
 >Arrival-Date: =A0 Mon May 17 01:00:10 UTC 2010
 >Closed-Date:
 >Last-Modified:
 >Originator: =A0 =A0 Tommy Johnson
 >Release: =A0 =A0 =A0 =A08.0
 >Organization:
 >Environment:
  FreeBSD teryx 8.0-STABLE FreeBSD 8.0-STABLE #8: Sat May 15 15:49:45 ED=
 T 2010 =A0 =A0 tjohn...@teryx:/usr/src/sys/amd64/compile/TERYX =A0amd64
 >Description:
  Support for cards with vendor 9901 device 9710 is in the uart and ppc =
 drivers. =A0Unfortunately several boards use the same PCI ID, and they don'=
 t all work.
 
  The code as it exists right now, will support boards which use the bui=
 lt in serial and parallel ports on the 9710 chip. =A0One or two serial, wit=
 h zero or one LPT will probably work.
 
  The board I have is four serial one LPT, which is implemented as two s=
 erial on the built in UARTS, and then an ISA bus interface with another two=
  UARTS and a LPT interface on that ISA bus. =A0Possibly implemented with a =
 16S552 chip. =A0(It has no documentation, of course...)
 
  The same chip will also do a USB port (instead of an LPT, or ISA).
 
  So the first two serial ports are fine, but the second two serial port=
 s and the LPT fail to probe.
 >How-To-Repeat:
  Get a 9710 board with four serial and one LPT, and note that only the =
 first two serial ports work.
 >Fix:
 >>>
 >>> Hi Tommy,
 >>> =A0 =A0This is probably because the subvendor for your particular card
 >>> hasn't been added yet. Could you run devinfo -v and provide us with
 >>> the output, as well as a URL to the specific card that you acquired?
 >>> Thanks!
 >>
 >> =A0 =A0pciconf -lv would be helpful as well so that the devinfo could be
 >> properly mapped back to the appropriate device.
 >
 > Ok... the information you sent me just a while ago was interesting. It
 > appears to be a card with similar attributes to the card I sent out in
 > the past couple of months and Xinli (delphij@) was nice enough to add
 > and MFC. Here's my card (for reference):
 >
 > ua...@pci0:1:0:0: =A0 =A0 =A0 class=3D0x070002 card=3D0x1000a000 chip=3D0=
 x99019710
 > rev=3D0x00 hdr=3D0x00
 > =A0 =A0vendor =A0 =A0 =3D 'MosChip Semiconductors (Was: Netmos Technology=
 )'
 > =A0 =A0class =A0 =A0 =A0=3D simple comms
 > =A0 =A0subclass =A0 =3D UART
 > ua...@pci0:1:0:1: =A0 =A0 =A0 class=3D0x070002 card=3D0x1000a000 chip=3D0=
 x99019710
 > rev=3D0x00 hdr=3D0x00
 > =A0 =A0vendor =A0 =A0 =3D 'MosChip Semiconductors (Was: Netmos Technology=
 )'
 > =A0 =A0class =A0 =A0 =A0=3D simple comms
 > =A0 =A0subclass =A0 =3D UART
 > p...@pci0:1:0:2: =A0 =A0 =A0 =A0class=3D0x070103 card=3D0x2000a000 chip=
 =3D0x99019710
 > rev=3D0x00 hdr=3D0x00
 > =A0 =A0vendor =A0 =A0 =3D 'MosChip Semiconductors (Was: Netmos Technology=
 )'
 > =A0 =A0class =A0 =A0 =A0=3D simple comms
 > =A0 =A0subclass =A0 =3D parallel port
 >
 > What's interesting about your card's details is that it isn't
 > detecting the serial uarts based off the 4-port splitter as uarts, and
 > is instead detecting them as parallel ports. Very interesting
 > indeed...
 >
 > I'm not sure what modifications you've made to your local copy of
 > ppc(4), but definitely back out everything (sans the IDs for ppc3),
 > and add the PCI IDs to /sys/dev/uart/uart_bus_pci.c -- and it *should*
 > detect the appropriate uarts. If not, there's some kind of
 > configuration required that hasn't been setup on either the board or
 > something in software that needs to be done that's specific to the
 > card, or something that needs to be added to device.hints so that it
 > properly configures the card irqs, etc.
 >
 > FWIW my card doesn't function with lpt(4) (it's passing interrupts to
 > and from the driver, but I haven't hooked by the pinouts to see
 > whether or not signals are being passed through). I'm working on
 > root-causing what the issue is because it's related to work and
 > impacts productivity with an internal tools release.
 >
 > Thanks for the documentation though 

misc/147096: test PR

[Mark Linimon]

>Number: 147096
>Category:   misc
>Synopsis:   test PR
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  change-request
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 26 21:00:21 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: test PR
>Release:test PR
>Organization:
Lonesome Dove Computing Services
>Environment:
System: FreeBSD freefall.freebsd.org 8.0-STABLE FreeBSD 8.0-STABLE #42 r204803: 
Sat Mar 6 21:21:56 UTC 2010 
si...@freefall.freebsd.org:/usr/src/sys/i386/compile/FREEFALL i386
test PR
>Description:
test PR
>How-To-Repeat:
test PR
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

misc/147102: IPv6 - route6d deletes site-local routes

[Stephen Hurd]

>Number: 147102
>Category:   misc
>Synopsis:   IPv6 - route6d deletes site-local routes
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-bugs
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu May 27 00:10:03 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: Stephen Hurd
>Release:8.0-RELEASE-p2
>Organization:
>Environment:
FreeBSD cracked.hurd.local 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #0: Mon May 17 
03:36:47 PDT 2010 r...@cracked.hurd.local:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
When route6d is running, it will delete the site-local routes after about five 
minutes.
>How-To-Repeat:
Set up a site-local IPv6 address as well as a public one on an interface and 
enable routing etc (My config snippit follows) and wait five minutes.

The route gets deleted and not logged to /var/log/route.log, but route monitor 
output shows the PID (812) of route6d deleting the route (log snippit follows).

= Start route monitor output =
got message of size 188 on Wed May 26 14:20:21 2010
RTM_DELETE: Delete Route: len 188, pid: 812, seq 6, errno 0, flags:
locks:  inits:
sockaddrs: 
 fec0::  (255)    c0ff
= End route monitor output =

= Start rc.conf bit =
ipv6_enable="YES"
ipv6_router_enable="YES"# Set to YES to enable an IPv6 routing daemon.
ipv6_router_flags="-R /var/log/route.log"   # Flags to IPv6 routing 
daemon.
rtadvd_enable="YES" # Set to YES to enable an IPv6 router
# advertisement daemon. If set to YES,
# this router becomes a possible candidate
# IPv6 default router for local subnets.
rtadvd_interfaces="fxp0 gif0"   # Interfaces rtadvd sends RA packets.
#mroute6d_enable="YES"  # Do IPv6 multicast routing.
ipv6_gateway_enable="YES"
ipv6_firewall_enable="YES"
ipv6_firewall_type="OPEN"
ipv6_network_interfaces="fxp0 lo0 gif0"
# Site-local
ipv6_ifconfig_fxp0_alias0="fec0::1/10"
# DNS Well-known addresses
ipv6_ifconfig_fxp0_alias1="fec0:0:0:::1/10"
ipv6_ifconfig_fxp0_alias2="fec0:0:0:::2/10"
ipv6_ifconfig_fxp0_alias3="fec0:0:0:::3/10"
ipv6_ifconfig_fxp0_alias4="2001:470:d:684::1/64"

# The HE tunnel...
gif_interfaces="gif0"
gifconfig_gif0="76.202.204.42 66.220.18.42"
ifconfig_gif0="inet6 2001:470:c:684::2 2001:470:c:684::1 prefixlen 128"
ipv6_defaultrouter="2001:470:c:684::1"
= End rc.conf bit =
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147102: [ip6] route6d deletes site-local routes

[linimon]

Old Synopsis: IPv6 - route6d deletes site-local routes
New Synopsis: [ip6] route6d deletes site-local routes

Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu May 27 00:24:43 UTC 2010
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=147102
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: misc/146904: [build] [patch] fix make release after lzma import

[delphij]

Synopsis: [build] [patch] fix make release after lzma import

State-Changed-From-To: open->closed
State-Changed-By: delphij
State-Changed-When: Thu May 27 00:35:03 UTC 2010
State-Changed-Why: 
Should have been fixed in latest -HEAD.


Responsible-Changed-From-To: freebsd-bugs->delphij
Responsible-Changed-By: delphij
Responsible-Changed-When: Thu May 27 00:35:03 UTC 2010
Responsible-Changed-Why: 
Take.

http://www.freebsd.org/cgi/query-pr.cgi?pr=146904
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[Andy Farkas]

On Thu, May 27, 2010 at 5:42 AM,   wrote:
> Synopsis: [uart] Serial ports unusable
>
> State-Changed-From-To: open->feedback
> State-Changed-By: remko
> State-Changed-When: Wed May 26 19:42:36 UTC 2010
> State-Changed-Why:
> I send my working serial line to Mayo, set status to feedback
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=147082

Please post it here. I see the same thing.

My system now has a stuck process that will need a reboot to clear:

0 27723 1   0  44  0  3308   892 ttyout IEs+  u0-   0:00.02
/usr/libexec/getty std.9600 cuau0

-andyf
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[Mayo Jordanov]

On 2010-05-26, at 12:42 , re...@freebsd.org wrote:

> Synopsis: [uart] Serial ports unusable
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: remko
> State-Changed-When: Wed May 26 19:42:36 UTC 2010
> State-Changed-Why: 
> I send my working serial line to Mayo, set status to feedback
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=147082

I'm gona re-reply here, to preserve the history.

>>> How-To-Repeat:
>> 1) Edit /etc/ttys, do the ttyu0 line reads:
>> ttyu0"/usr/libexec/getty std.9600"   vt100   on secure
>> 2) kill -HUP 1
>> 3) Try connecting to it with terminal application
> 
> 
> /etc/ttys
> console"/usr/libexec/getty Pc" cons25  on  secure
> 
> /boot/loader.conf
> console="comconsole"
> 
> That enabled serial access to my Soekris device running on FreeBSD8(PFsense), 
> it also works for several remote machines I have.
> 
> Can you confirm that you have these settings in loader.conf and rebooted?!
> 
> -- 
> /"\   Best regards,| re...@freebsd.org
> \ /   Remko Lodder  | re...@efnet
> Xhttp://www.evilcoder.org/|
> / \   ASCII Ribbon Campaign| Against HTML Mail and News

test# cat /boot/loader.conf 
console="comconsole"

looking at the /etc/ttys entry you pasted above, will that enable serial 
console? That looks like a regular console on the machine itself.

I have rebooted numerous times, and I do get the kernel messages during boot on 
serial up to the point where getty starts (presumably... I see portion of the 
messages as nics are getting setup and then nothing).

I have some machines where serial works fine, but I have some machines where it 
doesn't and behaves the same way as described above. If necessary, I can 
provide access to a troublesome machine.

Thanks,
mayo___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[Garrett Cooper]

On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov  wrote:
>
> On 2010-05-26, at 12:42 , re...@freebsd.org wrote:
>
>> Synopsis: [uart] Serial ports unusable
>>
>> State-Changed-From-To: open->feedback
>> State-Changed-By: remko
>> State-Changed-When: Wed May 26 19:42:36 UTC 2010
>> State-Changed-Why:
>> I send my working serial line to Mayo, set status to feedback
>>
>> http://www.freebsd.org/cgi/query-pr.cgi?pr=147082
>
> I'm gona re-reply here, to preserve the history.
>
 How-To-Repeat:
>>> 1) Edit /etc/ttys, do the ttyu0 line reads:
>>> ttyu0        "/usr/libexec/getty std.9600"   vt100   on secure
>>> 2) kill -HUP 1
>>> 3) Try connecting to it with terminal application
>>
>>
>> /etc/ttys
>> console    "/usr/libexec/getty Pc"         cons25  on  secure
>>
>> /boot/loader.conf
>> console="comconsole"
>>
>> That enabled serial access to my Soekris device running on 
>> FreeBSD8(PFsense), it also works for several remote machines I have.
>>
>> Can you confirm that you have these settings in loader.conf and rebooted?!
>>
>> --
>> /"\   Best regards,                        | re...@freebsd.org
>> \ /   Remko Lodder                      | re...@efnet
>> X    http://www.evilcoder.org/    |
>> / \   ASCII Ribbon Campaign    | Against HTML Mail and News
>
> test# cat /boot/loader.conf
> console="comconsole"
>
> looking at the /etc/ttys entry you pasted above, will that enable serial 
> console? That looks like a regular console on the machine itself.
>
> I have rebooted numerous times, and I do get the kernel messages during boot 
> on serial up to the point where getty starts (presumably... I see portion of 
> the messages as nics are getting setup and then nothing).
>
> I have some machines where serial works fine, but I have some machines where 
> it doesn't and behaves the same way as described above. If necessary, I can 
> provide access to a troublesome machine.

All of this is described in more grusome detail at
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
.
HTH,
-Garrett
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[Mayo Jordanov]

On 2010-05-26, at 19:34 , Garrett Cooper wrote:

> On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov  wrote:
>> 
>> On 2010-05-26, at 12:42 , re...@freebsd.org wrote:
>> 
>>> Synopsis: [uart] Serial ports unusable
>>> 
>>> State-Changed-From-To: open->feedback
>>> State-Changed-By: remko
>>> State-Changed-When: Wed May 26 19:42:36 UTC 2010
>>> State-Changed-Why:
>>> I send my working serial line to Mayo, set status to feedback
>>> 
>>> http://www.freebsd.org/cgi/query-pr.cgi?pr=147082
>> 
>> I'm gona re-reply here, to preserve the history.
>> 
> How-To-Repeat:
 1) Edit /etc/ttys, do the ttyu0 line reads:
 ttyu0"/usr/libexec/getty std.9600"   vt100   on secure
 2) kill -HUP 1
 3) Try connecting to it with terminal application
>>> 
>>> 
>>> /etc/ttys
>>> console"/usr/libexec/getty Pc" cons25  on  secure
>>> 
>>> /boot/loader.conf
>>> console="comconsole"
>>> 
>>> That enabled serial access to my Soekris device running on 
>>> FreeBSD8(PFsense), it also works for several remote machines I have.
>>> 
>>> Can you confirm that you have these settings in loader.conf and rebooted?!
>>> 
>>> --
>>> /"\   Best regards,| re...@freebsd.org
>>> \ /   Remko Lodder  | re...@efnet
>>> Xhttp://www.evilcoder.org/|
>>> / \   ASCII Ribbon Campaign| Against HTML Mail and News
>> 
>> test# cat /boot/loader.conf
>> console="comconsole"
>> 
>> looking at the /etc/ttys entry you pasted above, will that enable serial 
>> console? That looks like a regular console on the machine itself.
>> 
>> I have rebooted numerous times, and I do get the kernel messages during boot 
>> on serial up to the point where getty starts (presumably... I see portion of 
>> the messages as nics are getting setup and then nothing).
>> 
>> I have some machines where serial works fine, but I have some machines where 
>> it doesn't and behaves the same way as described above. If necessary, I can 
>> provide access to a troublesome machine.
> 
>All of this is described in more grusome detail at
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
> .
> HTH,
> -Garrett

Unfortunately, the handbook does not help in this case. If there is a solution 
to the problem I describe in the PR description in the handbook, please be so 
kind and point it out to me, because I must be blind.

Also, why do the gettys get stuck and I have to kill them manually (or reboot 
because they can't be killed) to reflect changes to /etc/ttys instead of simple 
`kill -HUP 1`? I've never ever had to do it manually in previous FreeBSD 
installations/versions. Why are they stuck in ttydtd and not in ttyin as they 
are supposed to be?

Thanks,
mayo


___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147088: Re: kern/147086: AHCI not being enabled on PC

[linimon]

Synopsis: Re: kern/147086: AHCI not being enabled on PC

State-Changed-From-To: open->closed
State-Changed-By: linimon
State-Changed-When: Thu May 27 04:27:16 UTC 2010
State-Changed-Why: 
Misfiled followup to kern/147086; content migrated.


Responsible-Changed-From-To: gnats-admin->freebsd-bugs
Responsible-Changed-By: linimon
Responsible-Changed-When: Thu May 27 04:27:16 UTC 2010
Responsible-Changed-Why: 

http://www.freebsd.org/cgi/query-pr.cgi?pr=147088
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[Garrett Cooper]

On Wed, May 26, 2010 at 8:01 PM, Mayo Jordanov  wrote:
>
> On 2010-05-26, at 19:34 , Garrett Cooper wrote:
>
>> On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov  wrote:
>>>
>>> On 2010-05-26, at 12:42 , re...@freebsd.org wrote:
>>>
 Synopsis: [uart] Serial ports unusable

 State-Changed-From-To: open->feedback
 State-Changed-By: remko
 State-Changed-When: Wed May 26 19:42:36 UTC 2010
 State-Changed-Why:
 I send my working serial line to Mayo, set status to feedback

 http://www.freebsd.org/cgi/query-pr.cgi?pr=147082
>>>
>>> I'm gona re-reply here, to preserve the history.
>>>
>> How-To-Repeat:
> 1) Edit /etc/ttys, do the ttyu0 line reads:
> ttyu0        "/usr/libexec/getty std.9600"   vt100   on secure
> 2) kill -HUP 1
> 3) Try connecting to it with terminal application


 /etc/ttys
 console    "/usr/libexec/getty Pc"         cons25  on  secure

 /boot/loader.conf
 console="comconsole"

 That enabled serial access to my Soekris device running on 
 FreeBSD8(PFsense), it also works for several remote machines I have.

 Can you confirm that you have these settings in loader.conf and rebooted?!

 --
 /"\   Best regards,                        | re...@freebsd.org
 \ /   Remko Lodder                      | re...@efnet
 X    http://www.evilcoder.org/    |
 / \   ASCII Ribbon Campaign    | Against HTML Mail and News
>>>
>>> test# cat /boot/loader.conf
>>> console="comconsole"
>>>
>>> looking at the /etc/ttys entry you pasted above, will that enable serial 
>>> console? That looks like a regular console on the machine itself.
>>>
>>> I have rebooted numerous times, and I do get the kernel messages during 
>>> boot on serial up to the point where getty starts (presumably... I see 
>>> portion of the messages as nics are getting setup and then nothing).
>>>
>>> I have some machines where serial works fine, but I have some machines 
>>> where it doesn't and behaves the same way as described above. If necessary, 
>>> I can provide access to a troublesome machine.
>>
>>    All of this is described in more grusome detail at
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
>
> Unfortunately, the handbook does not help in this case. If there is a 
> solution to the problem I describe in the PR description in the handbook, 
> please be so kind and point it out to me, because I must be blind.
>
> Also, why do the gettys get stuck and I have to kill them manually (or reboot 
> because they can't be killed) to reflect changes to /etc/ttys instead of 
> simple `kill -HUP 1`? I've never ever had to do it manually in previous 
> FreeBSD installations/versions. Why are they stuck in ttydtd and not in ttyin 
> as they are supposed to be?

The comconsole bit is in the section of /etc/ttys in the
beforementioned page.
Details about debugging your connection is available here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/term.html .
What's the baud rate for your serial connection?
The part about kill -HUP 1 not working sounds like a possible
syscons/tty bug. Can you try killing init, then provide us with the
wait state in ps/top for the relevant getty instance?
Thanks!
-Garrett
___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"

Re: kern/147082: [uart] Serial ports unusable

[Mayo Jordanov]

On 2010-05-26, at 21:46 , Garrett Cooper wrote:

> On Wed, May 26, 2010 at 8:01 PM, Mayo Jordanov  wrote:
>> 
>> On 2010-05-26, at 19:34 , Garrett Cooper wrote:
>> 
>>> On Wed, May 26, 2010 at 6:42 PM, Mayo Jordanov  wrote:
 
 On 2010-05-26, at 12:42 , re...@freebsd.org wrote:
 
> Synopsis: [uart] Serial ports unusable
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: remko
> State-Changed-When: Wed May 26 19:42:36 UTC 2010
> State-Changed-Why:
> I send my working serial line to Mayo, set status to feedback
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=147082
 
 I'm gona re-reply here, to preserve the history.
 
>>> How-To-Repeat:
>> 1) Edit /etc/ttys, do the ttyu0 line reads:
>> ttyu0"/usr/libexec/getty std.9600"   vt100   on secure
>> 2) kill -HUP 1
>> 3) Try connecting to it with terminal application
> 
> 
> /etc/ttys
> console"/usr/libexec/getty Pc" cons25  on  secure
> 
> /boot/loader.conf
> console="comconsole"
> 
> That enabled serial access to my Soekris device running on 
> FreeBSD8(PFsense), it also works for several remote machines I have.
> 
> Can you confirm that you have these settings in loader.conf and rebooted?!
> 
> --
> /"\   Best regards,| re...@freebsd.org
> \ /   Remko Lodder  | re...@efnet
> Xhttp://www.evilcoder.org/|
> / \   ASCII Ribbon Campaign| Against HTML Mail and News
 
 test# cat /boot/loader.conf
 console="comconsole"
 
 looking at the /etc/ttys entry you pasted above, will that enable serial 
 console? That looks like a regular console on the machine itself.
 
 I have rebooted numerous times, and I do get the kernel messages during 
 boot on serial up to the point where getty starts (presumably... I see 
 portion of the messages as nics are getting setup and then nothing).
 
 I have some machines where serial works fine, but I have some machines 
 where it doesn't and behaves the same way as described above. If 
 necessary, I can provide access to a troublesome machine.
>>> 
>>>All of this is described in more grusome detail at
>>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/serialconsole-setup.html
>> 
>> Unfortunately, the handbook does not help in this case. If there is a 
>> solution to the problem I describe in the PR description in the handbook, 
>> please be so kind and point it out to me, because I must be blind.
>> 
>> Also, why do the gettys get stuck and I have to kill them manually (or 
>> reboot because they can't be killed) to reflect changes to /etc/ttys instead 
>> of simple `kill -HUP 1`? I've never ever had to do it manually in previous 
>> FreeBSD installations/versions. Why are they stuck in ttydtd and not in 
>> ttyin as they are supposed to be?
> 
>The comconsole bit is in the section of /etc/ttys in the
> beforementioned page.
>Details about debugging your connection is available here:
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/term.html .
> What's the baud rate for your serial connection?
>The part about kill -HUP 1 not working sounds like a possible
> syscons/tty bug. Can you try killing init, then provide us with the
> wait state in ps/top for the relevant getty instance?
> Thanks!
> -Garrett

Sorry, I wasn't clear in my problem description above. I just said I modified 
loader.conf, intending that I added console="comconsole".

I'm using 9600 baud. I've tried both 3wire and std connections, I don't get 
prompt with either, I'm sticking to 3wire for the time being.

After boot -- after I see interface configuration, daemons start, etc, right 
when I expect the "login:" prompt -- I get no login prompt and it takes about 3 
minutes for it to show up. (This delay does not exist when I disable ttyd0.) 
SSHing in during those 3 minutes of delay, there are no gettys running. Once 
they do start, the states are:
0  1220 1   0  45  0  6892  1300 ttyin  Is+   u00:00.01 
/usr/libexec/getty 3wire.9600 ttyu0

(which seems right, but the terminal still misbehaves as described before)
Changing the ttyu0 line in /etc/ttys and `kill -HUP 1`:
0  1252 1   0  44  0  6892  1300 ttyout SEs+  u0-   0:00.00 
/usr/libexec/getty 3wire.9600 ttyu0

The reason I was mentioning uart is that I can't even get communication going 
between two ports (kermit to kermit, cu to cu, etc).

It is also worth noting, messages on console generated by kernel (plugging usb 
devices in/out, for eg.) _do_ make it over the serial console immediately as on 
normal console, but nothing else does work.

Thanks,
mayo

___
freebsd-bugs@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"