Re: 4.8 "Alternate system clock has died" error

On Tue, 22 Nov 2005, Uwe Doering wrote: Charles Sprickman wrote: On Mon, 21 Nov 2005, John Baldwin wrote: On Saturday 19 November 2005 02:16 pm, Uwe Doering wrote: John Baldwin wrote: [...] Actually, there was a patch that was committed in 5.4 and 6.0 for this issue. You can see the diff her

Re: VIA 6420 RAID 0 problem

On Tue, 22 Nov 2005, Marcin Simonides wrote: I have (had?) two issues, perhaps connected: (I posted a question to freebsd-questions about it some time ago. It contains some additional information: http://lists.freebsd.org/pipermail/freebsd-questions/2005-November/103991.html) The other, pe

Re: 4.8 "Alternate system clock has died" error

Charles Sprickman wrote: On Mon, 21 Nov 2005, John Baldwin wrote: On Saturday 19 November 2005 02:16 pm, Uwe Doering wrote: John Baldwin wrote: [...] Actually, there was a patch that was committed in 5.4 and 6.0 for this issue. You can see the diff here: http://www.freebsd.org/cgi/cvsweb.cgi/

Re: 4.8 "Alternate system clock has died" error

On Mon, 21 Nov 2005, John Baldwin wrote: On Saturday 19 November 2005 02:16 pm, Uwe Doering wrote: John Baldwin wrote: On Friday 18 November 2005 10:05 pm, Charles Sprickman wrote: I tried this query on -stable, hoping someone here can help me further understand and troubleshoot this. Refere

VIA 6420 RAID 0 problem

I have (had?) two issues, perhaps connected: (I posted a question to freebsd-questions about it some time ago. It contains some additional information: http://lists.freebsd.org/pipermail/freebsd-questions/2005-November/103991.html) The first one is a problem with RAID 0, where ar0 device shows

How to check if a processor in the machine is dead

Hi, I am having problem with my dell 2850 server. It has freebsd 5.4 installed. Today the machine is flashing amber light on the face plate.On checking I found that to be PROC Machine Chk which means cpu has failed. The server has dual Intel(R) Xeon(TM) CPU 3.00GHz. I searched and found a utility

Re: sysinit how does nexus find legacy's driver?

On Monday 21 November 2005 11:07 am, kylin wrote: > The nexus_attach(device_t dev) will call > > int > bus_generic_probe(device_t dev) > { > devclass_t dc = dev->devclass; > driverlink_t dl; > > TAILQ_FOREACH(dl, &dc->drivers, link) {//here configure has point out > the relation?

Re: 4.8 "Alternate system clock has died" error

On Saturday 19 November 2005 02:16 pm, Uwe Doering wrote: > John Baldwin wrote: > > On Friday 18 November 2005 10:05 pm, Charles Sprickman wrote: > >>I tried this query on -stable, hoping someone here can help me further > >>understand and troubleshoot this. > >> > >>Reference: > >>http://thread.gm

sysinit how does nexus find legacy's driver?

The nexus_attach(device_t dev) will call int bus_generic_probe(device_t dev) { devclass_t dc = dev->devclass; driverlink_t dl; TAILQ_FOREACH(dl, &dc->drivers, link) {//here configure has point out the relation? DEVICE_IDENTIFY(dl->driver, dev);//here refer

Re: poll()/select()

On Monday 21 November 2005 08:14 am, Konstantin Prokazoff wrote: > Thanks for comment, > > I think, after kernel inspection, problem (maybe) in preemption. While > syscall to poll or select holds sellock, and if another thread (process) > tries to syscall or we have taken interrupt (where handl

Re: Driver crashes after unloading a module

On Sunday 20 November 2005 11:04 am, rashmi ns wrote: > Hello List , > > Thanks for the help you given me . > > We have written driver for hdlc controller .The kernel is crashing > after unloading > the module with trap 12 fault .here is the order in which we release the > resources while detach

Re: Physical memory access from kld

I think that you'll want to use PCIB_READ_CONFIG. This function takes a pointer to a pci bridge device_t and can be used to read an arbitrary register in pci config space. PCIB_READ_CONFIG(pcib, b, s, f, n, w) b -- bus s -- slot f -- function n -- register to read w -- width to read This will h

Re: ATI drivers for FreeBSD - anything? [Slightly OT]

Maxime Henrion wrote: Albert Vest wrote: On Sat, 19 Nov 2005 01:58:25 +0200 (EET) Vladimir Kushnir <[EMAIL PROTECTED]> wrote: Hi all, Is there any project on FreeBSD wrapper for ATI Linux drivers (like nVidia's used to be)? If so - I'd be more than happy to test (sorry I can hardly write i

Re: ATI drivers for FreeBSD - anything?

Albert Vest wrote: > On Sat, 19 Nov 2005 01:58:25 +0200 (EET) > Vladimir Kushnir <[EMAIL PROTECTED]> wrote: > > > Hi all, > > Is there any project on FreeBSD wrapper for ATI Linux drivers (like > > nVidia's used to be)? If so - I'd be more than happy to test (sorry I can > > hardly write it myse

Re: ATI drivers for FreeBSD - anything?

On Sat, 19 Nov 2005 01:58:25 +0200 (EET) Vladimir Kushnir <[EMAIL PROTECTED]> wrote: > Hi all, > Is there any project on FreeBSD wrapper for ATI Linux drivers (like > nVidia's used to be)? If so - I'd be more than happy to test (sorry I can > hardly write it myself). > > Regards, > Vladimir I

Re: poll()/select()

Thanks for comment, I think, after kernel inspection, problem (maybe) in preemption. While syscall to poll or select holds sellock, and if another thread (process) tries to syscall or we have taken interrupt (where handler use selrecord/selwakeup too), kernel will deadlock. I have this sit

Re: poll()/select()

At 10:29 AM 11/21/2005 +0200, Konstantin Prokazoff wrote: | Welcome everybody, | | have a strange issue under 5.x/6.x (checked). | When using a poll()/select() mechanism, which in kernel based on | selrecord/selwakeup (pollscan, kern_select) functions, we have deadlock on | sellock mutex o

poll()/select()

Welcome everybody, have a strange issue under 5.x/6.x (checked). When using a poll()/select() mechanism, which in kernel based on selrecord/selwakeup (pollscan, kern_select) functions, we have deadlock on sellock mutex on heavy load (recursive lock on non-recursive mutex). Have anyone seen