Re: cu: Got hangup signal on sio0 probe

Hi Jeremy, On Wed, May 09, 2007 at 04:06:19PM -0700, Jeremy Chadwick wrote: On Thu, May 10, 2007 at 12:19:27AM +0200, Jeremie Le Hen wrote: % obiwan:root# cat /boot.config % -D % obiwan:root# grep ttyd0 /etc/ttys % ttyd0 /usr/libexec/getty std.9600 dialup on secure This

(no subject)

I'm trying to get work a WMP54G Linksys Wireless card. I should work with .ko normal driver (ra.ko or ral.ko don'r remember) but it doesn't. I tried with ndisgen and so on ... In fact all what i found on google don't work more than 2 seconds. The ndisgen is the one who work the best but as soon as

Re: (no subject)

Hello Oliver, On 5/10/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'm trying to get work a WMP54G Linksys Wireless card. I should work with .ko normal driver (ra.ko or ral.ko don'r remember) but it doesn't. I tried with ndisgen and so on ... In fact all what i found on google don't work more

Re: cu: Got hangup signal on sio0 probe

On Thu, May 10, 2007 at 09:34:55AM +0200, Jeremie Le Hen wrote: On Wed, May 09, 2007 at 04:06:19PM -0700, Jeremy Chadwick wrote: On Thu, May 10, 2007 at 12:19:27AM +0200, Jeremie Le Hen wrote: % obiwan:root# cat /boot.config % -D % obiwan:root# grep ttyd0 /etc/ttys % ttyd0

[releng_5 tinderbox] failure on sparc64/sparc64

TB --- 2007-05-10 14:42:44 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2007-05-10 14:42:44 - starting RELENG_5 tinderbox run for sparc64/sparc64 TB --- 2007-05-10 14:42:44 - cleaning the object tree TB --- 2007-05-10 14:43:10 - checking out the source tree TB --- 2007-05-10 14:43:10

Re: cvsup Änderungen?

Am Donnerstag, den 10.05.2007, 09:46 +0200 schrieb nighthawk: On 5/10/07, Bernd Walter [EMAIL PROTECTED] wrote: On Thu, May 10, 2007 at 01:22:01AM +0200, nighthawk wrote: Naja. Nicht viel und nichts ist schon noch ein Unterschied. In den letzten drei Tagen kam gar nichts und das ist doch

Re: (no subject)

On Thu, May 10, 2007 at 10:03:41AM +0200, [EMAIL PROTECTED] wrote: I'm trying to get work a WMP54G Linksys Wireless card. I should work with .ko normal driver (ra.ko or ral.ko don'r remember) but it doesn't. The problem might be that wireless card manufacturers sometimes switch the chipset on

Re: cvsup Änderungen?

Sorry, I've mixed up adresses here, please ignore ... Marc ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]

6.2-R on Dell Poweredge 2950 with Dell PERC 5/i [mfi(4)]

From a quick look in the lists, I get the impression that the Dell PERC 5/i may be a bit problematic. Since I hadn't any plans on using that hardware, though, I've paid more attention to other things. Well, now a colleague is trying to run 6.2-R on one of these 2950s; dmesg says the controller

panic: spin lock held too long (w/ backtrace)

Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have been able to re-create the problem fairly consistently just by looping a script that tars

Re: panic: spin lock held too long (w/ backtrace)

On Thu, May 10, 2007 at 02:49:45PM -0600, Scott Swanson wrote: Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have been able to

Re: panic: spin lock held too long (w/ backtrace)

Kris Kennaway wrote: On Thu, May 10, 2007 at 02:49:45PM -0600, Scott Swanson wrote: Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have

Re: 6.2-R on Dell Poweredge 2950 with Dell PERC 5/i [mfi(4)]

David Wolfskill wrote: From a quick look in the lists, I get the impression that the Dell PERC 5/i may be a bit problematic. Since I hadn't any plans on using that hardware, though, I've paid more attention to other things. Not sure that this impression is entirely accurate. The biggest

Re: panic: spin lock held too long (w/ backtrace)

Kris Kennaway wrote: On Thu, May 10, 2007 at 02:49:45PM -0600, Scott Swanson wrote: Hello all, I have a couple dozen SuperMicro servers in production and have had reoccurring crashing issues on a couple of them that are under higher load. After managing to pry one out of production, I have

Re: panic: spin lock held too long (w/ backtrace)

On Thu, May 10, 2007 at 07:00:00PM -0600, Scott Swanson wrote: Unread portion of the kernel message buffer: spin lock smp rendezvous held by 0xc95a5900 for 5 seconds What is thread 0xc95a5900 doing? Kris Is this the best way to determine the action of the thread? Regards;

Re: panic: spin lock held too long (w/ backtrace)

Kris Kennaway wrote: On Thu, May 10, 2007 at 07:00:00PM -0600, Scott Swanson wrote: Unread portion of the kernel message buffer: spin lock smp rendezvous held by 0xc95a5900 for 5 seconds What is thread 0xc95a5900 doing? Kris Is this the best way to determine the action of the thread?

Re: panic: spin lock held too long (w/ backtrace)

On Thu, May 10, 2007 at 07:13:51PM -0600, Scott Swanson wrote: Kris Kennaway wrote: On Thu, May 10, 2007 at 07:00:00PM -0600, Scott Swanson wrote: Unread portion of the kernel message buffer: spin lock smp rendezvous held by 0xc95a5900 for 5 seconds What is thread 0xc95a5900 doing?

Re: panic: spin lock held too long (w/ backtrace)

(kgdb) proc 18303 (kgdb) bt #0 0xc0644f5b in sched_switch (td=0xc95a5900, newtd=0xc92aad80, flags=0) at /usr/src/sys/kern/sched_4bsd.c:973 #1 0xeaa6dcb4 in ?? () #2 0x0001 in ?? () #3 0x0ee2c000 in ?? () #4 0x in ?? () #5 0x4000 in ?? () #6 0x in ?? () #7

Re: panic: spin lock held too long (w/ backtrace)

On Thu, May 10, 2007 at 07:44:37PM -0600, Scott Swanson wrote: (kgdb) proc 18303 (kgdb) bt #0 0xc0644f5b in sched_switch (td=0xc95a5900, newtd=0xc92aad80, flags=0) at /usr/src/sys/kern/sched_4bsd.c:973 #1 0xeaa6dcb4 in ?? () #2 0x0001 in ?? () #3 0x0ee2c000 in ?? () #4

Supermicro PDSME+ / 3ware 9650

Hi, I am looking for a new motherboard as the P8SCT only supports CPUs that are no longer made. The PDSME+ has the multitude of PCI slots we need and I am wondering if anyone has any experience with it? I was thinking of pairing it with a 3ware 9650-2LP PCIe card - I note there was a recent

Re: clock problem

In message: [EMAIL PROTECTED] Martin Dieringer [EMAIL PROTECTED] writes: : well now it works without restrict: : # ntpq -p : remote refid st t when poll reach delay offset jitter : == :

Re: clock problem

In message: [EMAIL PROTECTED] Peter Jeremy [EMAIL PROTECTED] writes: : There seems to be a bug in ntpd where the PLL can saturate at : +/-500ppm and will not recover. This problem seems too occur mostly : where the reference servers have lots of jitter (ie a fairly congested : link to

Re: clock problem

In message: [EMAIL PROTECTED] Oliver Fromme [EMAIL PROTECTED] writes: : Martin's Problem with ntpd is not a precision problem. : His problem is that his ntpd does not synchronize at all. : Adding more servers certainly won't solve that problem. There are two causes to not