Hi, firstly:
RELENG_8 csup'd with date=2010.02.14.00.00 works perfectly for days.
RELENG_8 csup'd with date=2010.02.15.00.00 dead-locks the disk I/O
subsystem. Network still operational but anything needing disk hangs.
Power-cycle required.
kernel config is GENERIC with KDB, DDB and BREAK_TO_DEB
> RELENG_8 csup'd with date=2010.02.14.00.00 works perfectly for days.
>
> RELENG_8 csup'd with date=2010.02.15.00.00 dead-locks the disk I/O
> subsystem. Network still operational but anything needing disk hangs.
> Power-cycle required.
An aditional point (and thanks to Andy for doing all the wor
Hi.
I have problem when probing the ciss device. Causing a kernel panic. This
happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel
works. So something has changed. I am also getting the error on both the
7.3 and the 8.0 install cd's.
The ciss that causing the problem is a Smar
On Mon, Apr 26, 2010 at 10:02 PM, Jeremy Chadwick
wrote:
> On Tue, Apr 27, 2010 at 09:48:41AM +1000, Phil wrote:
>> Jeremy,
>> A good proposal to improve start-up robustness. If I may suggest,
>> waitnetwork_ip should include a short list of alternate IP's in
>> the event of a local network outage
I have a machine where I enabled swap on ZFS somewhat accidentally
(really wanted to dump to ZFS, but that didn't pan out) and then
forgot about it. A month later, under a heavy load (make
-j8 buildworld) it hung with:
swap_pager: indefinite wait buffer: bufobj: 0, blkno: 289218, size: 4096
swap
On Tue, 27 Apr 2010, kama wrote:
>
> Hi.
>
> I have problem when probing the ciss device. Causing a kernel panic. This
> happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel
> works. So something has changed. I am also getting the error on both the
> 7.3 and the 8.0 install cd'
> Well, the following header didn't work:
> Cc: ,
>
> Postfix will re-write this as part of sanitization, so I had to revert
> to creating mbox files by hand. Anyway, could you please test the
> following patch with a wider variety of mails?
Sorry for not getting around to this util now - am testi
Hi,
I was pleasantly surprised to see that puc(4) in 8-stable recognizes my
8 port serial cards and identifies them as follows:
puc0: port
0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f
irq 10 at device 14.0 on pci0
puc0: [FILTER]
uart2: <16550
On Tuesday 27 April 2010 9:30:12 am kama wrote:
>
> Hi.
>
> I have problem when probing the ciss device. Causing a kernel panic. This
> happened when I upgraded from 6.3 to 7.3-stable. Booting the old kernel
> works. So something has changed. I am also getting the error on both the
> 7.3 and the
On 16.04.2010 22:42, Harald Schmalzbauer wrote:
Jack Vogel schrieb am 16.04.2010 22:02 (localtime):
Glad things are better. On the Hartwell, the 0x10D3 adapter, what is the
problem you are seeing?
I just did an MFC, would ask that you try that code, see if it changes
anything.
With latest MFC
Thanks Harald,
Have already been made aware of this, its due to the broadcast WOL being
enabled, I will be
fixing the problem shortly. Sorry for the inconvenience.
Cheers,
Jack
On Tue, Apr 27, 2010 at 2:54 PM, Harald Schmalzbauer <
h.schmalzba...@omnilan.de> wrote:
> On 16.04.2010 22:42, Hara
On Apr 27, 2010, at 12:47 PM, Paul Schenkeveld wrote:
>puc0: port
> 0xe500-0xe51f,0xe520-0xe52f,0xe530-0xe537,0xe538-0xe53f,0xe540-0xe547,0xe548-0xe54f
> irq 10 at device 14.0 on pci0
*snip*
> The first two ports work correctly but the baudrate of the other six
> is incorrect, i.e. I have
I've got another PCI UART card based on OX16PCI952 that needs its
clock multiplied by 8 in order to work correctly. It was some
el-cheapo card I've got at Fry's.
p...@pci0:1:0:0:class=0x070006 card=0x00011415 chip=0x95211415
rev=0x00 hdr=0x00
vendor = 'Oxford Semiconductor Ltd'
13 matches
Mail list logo
