-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/15/11 23:21, Yuri wrote:
> I have dual COM port pci card: none7@pci0:8:1:0: class=0x070002
> card=0x32534348 chip=0x32534348 rev=0x10 hdr=0x00 class = simple
> comms subclass = UART bar [10] = type I/O Port, range 32, base
> 0xe8
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
On 08/16/2011 00:48, Xin LI wrote:
A wild guess... (You gotta to provide more details rather than just PCI
IDs).
My guess is that it's using these chips:
http://www.winchiphead.com/product/ch365detail.htm
http://www.winchiphead.com/product/ch353detail.htm
It didn't talked about possible cards
On Tuesday, August 16, 2011 5:25:28 am Yuri wrote:
> On 08/16/2011 00:48, Xin LI wrote:
> > A wild guess... (You gotta to provide more details rather than just PCI
> > IDs).
> >
> > My guess is that it's using these chips:
> >
> > http://www.winchiphead.com/product/ch365detail.htm
> > http://www.w
Hi All
I just ran freebsd-update to upgrade from 7.0 to 7.4 I figured
everything went ok. This is what I did.
1. freebsd-update upgrade -r 7.4-RELEASE
2. freebsd-update install
3. shutdown -r now
4. freebsd-update install
5. shutdown -r now
The system came back up ok but now if I run another
On 08/16/2011 08:57, John Baldwin wrote:
For multiport devices you will want to add an entry to sys/dev/puc/pucdata.c
and use the puc driver instead of patching uart directly. Perhaps this:
John,
I did what you suggested:
puc0: port 0xe880-0xe887,0xe800-0xe807
irq 17 at device 1.0 on pci8
on 15/08/2011 17:56 Steven Hartland said the following:
> (kgdb) x/512a 0xff8d8f357210
[snip]
Can you please also provide the following for this core?
list *vm_map_growstack+93
list *lim_cur+17
list *lim_rlimit+18
Also, it would be interesting to get panic output with DDB option.
--
Andriy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 08/16/11 12:53, Yuri wrote:
> On 08/16/2011 08:57, John Baldwin wrote:
>> For multiport devices you will want to add an entry to
>> sys/dev/puc/pucdata.c and use the puc driver instead of patching
>> uart directly. Perhaps this:
>
> John,
>
>
- Original Message -
From: "Andriy Gapon"
To: "Steven Hartland"
Cc:
Sent: Tuesday, August 16, 2011 9:30 PM
Subject: Re: debugging frequent kernel panics on 8.2-RELEASE
on 15/08/2011 17:56 Steven Hartland said the following:
(kgdb) x/512a 0xff8d8f357210
[snip]
Can you please
On Tuesday, August 16, 2011 3:53:17 pm Yuri wrote:
> On 08/16/2011 08:57, John Baldwin wrote:
> > For multiport devices you will want to add an entry to
sys/dev/puc/pucdata.c
> > and use the puc driver instead of patching uart directly. Perhaps this:
>
> John,
>
> I did what you suggested:
> pu
On 08/16/2011 13:37, Xin LI wrote:
And I think John's patch is right, I've added a new PCI ID for it
though, found from the datasheet. Did you have uart(4) in your kernel
(remove my old patch)?
Yes, uart(4) is in kernel and puc(4) is the loaded module. I think this
might be a problem that puc
On 08/16/2011 13:57, John Baldwin wrote:
Hmmm, can you get devinfo -v output? Specifically there should be two
children of puc0 and they should have extra data specifying what type of port
each child device is.
Here is the only reference to puc0 in devinfo -v output:
pcib8 pnpinfo ve
On Tuesday, August 16, 2011 4:59:42 pm Yuri wrote:
> On 08/16/2011 13:57, John Baldwin wrote:
> > Hmmm, can you get devinfo -v output? Specifically there should be two
> > children of puc0 and they should have extra data specifying what type of
port
> > each child device is.
> >
>
> Here is the
On Tuesday, August 16, 2011 4:57:26 pm Yuri wrote:
> On 08/16/2011 13:37, Xin LI wrote:
> > And I think John's patch is right, I've added a new PCI ID for it
> > though, found from the datasheet. Did you have uart(4) in your kernel
> > (remove my old patch)?
>
> Yes, uart(4) is in kernel and puc(
On 17/08/2011, at 6:57 AM, Yuri wrote:
> On 08/16/2011 13:37, Xin LI wrote:
>> And I think John's patch is right, I've added a new PCI ID for it
>> though, found from the datasheet. Did you have uart(4) in your kernel
>> (remove my old patch)?
>
> Yes, uart(4) is in kernel and puc(4) is the loade
15 matches
Mail list logo