Re: Is DRI on FreeBSD unmaintained?
In message: <[EMAIL PROTECTED]> Lefteris Chatzibarbas <[EMAIL PROTECTED]> writes: : Is DRI on FreeBSD unmaintained? Am I sending my problem report to the : wrong place? What should I do or who should I contact about this? anholt is currently on vacation... Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cardbus and xircom ethernet problem
In message: <[EMAIL PROTECTED]> "Matt" <[EMAIL PROTECTED]> writes: : pccard0: Card has no functions! This means that there are problems reading the CIS. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: nfs_getpages: error 13
On Sat, Jun 21, 2003 at 08:14:22PM -0700, Kris Kennaway wrote: > On Sat, Jun 21, 2003 at 11:04:20PM -0400, Robert Watson wrote: > > > > On Sat, 21 Jun 2003, Kris Kennaway wrote: > > > > > I have 3 machines running off of a 5.1-CURRENT NFS server (updated on > > > June 19), and the 5.1-BETA clients are all getting the following under > > > load: > > > > > > > Jun 20 21:24:35 dalki kernel: nfs_getpages: error 13 > > > > Jun 20 21:24:35 dalki kernel: vm_fault: pager read error, pid 82331 (cp) > > > > > > Any ideas? > > > > 13 is EACCES. Were you by any chance replacing or modifying the cp file > > or one of the shared libraries it relies on in NFS during the accesses? > > (i.e., installworld) > > Not that I'm aware of - this is just a regular package build on the > new korean package cluster, and I'm still getting the errors > intermittently throughout the build. The only nfs mounts that are going on are read-only mounts used to copy things from, so cp seems to be faulting when trying to read data from the NFS server. ps gave me a patch that modifies the nfs_getpages error to report the relevant pathname, so I might be able to get some more information about this. Kris pgp0.pgp Description: PGP signature
Re: nfs_getpages: error 13
On Sat, Jun 21, 2003 at 11:04:20PM -0400, Robert Watson wrote: > > On Sat, 21 Jun 2003, Kris Kennaway wrote: > > > I have 3 machines running off of a 5.1-CURRENT NFS server (updated on > > June 19), and the 5.1-BETA clients are all getting the following under > > load: > > > > > Jun 20 21:24:35 dalki kernel: nfs_getpages: error 13 > > > Jun 20 21:24:35 dalki kernel: vm_fault: pager read error, pid 82331 (cp) > > > > Any ideas? > > 13 is EACCES. Were you by any chance replacing or modifying the cp file > or one of the shared libraries it relies on in NFS during the accesses? > (i.e., installworld) Not that I'm aware of - this is just a regular package build on the new korean package cluster, and I'm still getting the errors intermittently throughout the build. Kris pgp0.pgp Description: PGP signature
Re: nfs_getpages: error 13
On Sat, 21 Jun 2003, Kris Kennaway wrote: > I have 3 machines running off of a 5.1-CURRENT NFS server (updated on > June 19), and the 5.1-BETA clients are all getting the following under > load: > > > Jun 20 21:24:35 dalki kernel: nfs_getpages: error 13 > > Jun 20 21:24:35 dalki kernel: vm_fault: pager read error, pid 82331 (cp) > > Any ideas? 13 is EACCES. Were you by any chance replacing or modifying the cp file or one of the shared libraries it relies on in NFS during the accesses? (i.e., installworld) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
nfs_getpages: error 13
I have 3 machines running off of a 5.1-CURRENT NFS server (updated on June 19), and the 5.1-BETA clients are all getting the following under load: > Jun 20 21:24:35 dalki kernel: nfs_getpages: error 13 > Jun 20 21:24:35 dalki kernel: vm_fault: pager read error, pid 82331 (cp) Any ideas? Kris pgp0.pgp Description: PGP signature
Re[2]: Problems booting install cd of both 4.x and 5.1 on SMP PPROmachine!
Hi. Uhm. I'm not really sure there's any ide in that machine itself. Linux lspci reports: Host bridge: Intel 440FX - 82441FX PMC (Natoma) rev 02 Vga : CL GD 5436 Alpine PCI Bridge: IBM IBM27-82351 (rev 01) SCSI Storage: AIC-7880U AMD 79c970 ethernet adapter.. No ide active atleast. On Sat, 21 Jun 2003 14:15:53 -0700 (PDT) - Julian Elischer <[EMAIL PROTECTED]> wrote: > had a similar problem in a system. It turns out the IDE (!) driver > was at fault.. I had to add a loader variable to disbale DMA on the IDE > drive (I think the IDE stuff came just after teh SCSI stuff so the last > thing I saw was the SCSI delay). > 4.0 worked fine.. Mvh/Best regards, Arnvid L. Karstad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is DRI on FreeBSD unmaintained?
On Sat, Jun 21, 2003 at 04:12:48PM +0300, Lefteris Chatzibarbas wrote: > Hello, > > I believe that the web page related to DRI on BSD (FreeBSD and NetBSD) > is: > > http://people.freebsd.org/~anholt/dri/index.html > > I have mailed both this mailing list and [EMAIL PROTECTED] (contact address > as stated in the aforementioned web page), about a problem with DRI on > FreeBSD and OpenGL and got no answer (10 days have passed since then). > > Is DRI on FreeBSD unmaintained? Am I sending my problem report to the > wrong place? What should I do or who should I contact about this? Eric is on vacation. kris pgp0.pgp Description: PGP signature
Problems booting install cd of both 4.x and 5.1 on SMP PPRO machine!
Hi I yet again tried to install FreeBSD on one of my older smp computer's since I want to use it as a secondary ns. But both 4.7/8 and 5.1 seems to freeze nicely at the Waiting 15 seconds for SCSI devices to settle. The machine is an older IBM PC Server 325. It does however boot other os's. Is there anyway to get around or to perhaps localize the problem? Mvh/Best regards, Arnvid L. Karstad ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Software watchdog patch
On Sat, Jun 21, 2003 at 06:33:41AM -0700, Hiten Pandya wrote: > On Fri, Jun 20, 2003 at 09:47:07PM -0500, Sean Kelly wrote: > Hello Sean, this stuff looks really promising. Anyways, I > can't comment about the code as I have had no time to read it, > but here are a few mdoc nitpicks I did: I believe I have cleaned up the mdoc issues you pointed out. The updated patch is available at the same URL: http://www.sean-kelly.org/watchdog.diff Thanks for the feedback. -- Sean Kelly | PGP KeyID: D2E5E296 [EMAIL PROTECTED] | http://www.zombie.org pgp0.pgp Description: PGP signature
Re: Current kernel Fatal Trap 12
At 12:21 PM 6/20/2003 -0400, Robert Watson wrote: >If you have a version of the kernel in question on disk and with debugging >symbols, could you attach gdb -k to it and send us the results of: > > l *0xc01f6212 > >That will provide a bit more information about where the panic is >occuring. This is likely a NULL pointer dereference. > >Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >[EMAIL PROTECTED] Network Associates Laboratories > >On Fri, 20 Jun 2003, Manfred Antar wrote: > >> For the past week i have not been able to boot with current kernel. >> The last kernel that works is from Sat June 14th. >> When I build and try and boot a current kernel I get: >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x38 >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xc01f6212 >> stack pointer = 0x10:0xc04b1e24 >> frame pointer = 0x10:0xc04b1e24 >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 0 (swapper) >> trap number = 12 >> panic: page fault >> Uptime: 1s >> >> >> Fatal trap 12: page fault while in kernel mode >> fault virtual address = 0x38 >> fault code = supervisor read, page not present >> instruction pointer = 0x8:0xc01f6212 >> stack pointer = 0x10:0xc04b1cec >> frame pointer = 0x10:0xc04b1cec >> code segment= base 0x0, limit 0xf, type 0x1b >> = DPL 0, pres 1, def32 1, gran 1 >> processor eflags= interrupt enabled, resume, IOPL = 0 >> current process = 0 (swapper) >> trap number = 12 >> panic: page fault >> Uptime: 1s >> >> This continues to scroll by many times and I can't get to the debugger. >> The machine is i386 SMP dual pentium-pro overdrive processors. >> Same thing happens with kernel configured as UNIprocessor. >> Removing: options KSTACK_PAGES=3 from kernel config file solved the Fatal Trap 12 Manfred == || [EMAIL PROTECTED] || || Ph. (415) 681-6235 || == ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Wi driver has WEP issues on both 5.0 and 5.1
I've seen this on my older Wavelan card, but not my more recent PRISM card. If I run with WITNESS compiled in, I don't see it, which suggests a timing issue. This came up at USENIX a couple of times and I know Scott and Warner were discussing potential sources and fixes; Scott noticed there were a lot of card resets in the new code not present previously, so one theory was that we needed a delay for a bit to settle during the reset. I've CC'd Warner and Scott to bug them. :-) Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Sat, 21 Jun 2003, BSDVault wrote: > A head up about the wi driver in FreeBSD 5.0 and 5.1. I have a netgear > MA-311 card that supports HostAP mode. The issue is that I get a busy bit > error. The exact error starts with the following.. THIS ONLY OCCURS WHEN > WEP IS ENABLED: > > wi0: timeout in wi_seek to fc00/0; last status 800b > > We then move on to : > > wi0: wi_cmd: busy bit won't clear. > > This seems to cycle until the next error: > > wi0: failed to allocate 1594 bytes on NIC > wi0: tx buffer allocation failed > wi0: mgmt. Buffer allocation failed > > Then back through the entire error sequence again. Eventually the box will > freeze as these errors cycle and then free up again when it starts back at > the timeout error. I was hopeful that the new wi driver in 5.1 would > address this problem as I know several persons with Prism chipsets that have > this very same issue on 5.0 and 5.1. > > Please respond directly as I am not on -current mailing list. > > Thanks > > Ray > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: locking problems in IPv6 code
On Sat, 21 Jun 2003, Hiten Pandya wrote: > On Thu, Jun 19, 2003 at 03:17:03PM -0700, John-Mark Gurney wrote: > > I am running FreeBSD 5.1-R on a sparc64 machine, and am getting warnings > > about mallocing data w/ a lock aquired. > > > > dmesg output: > > malloc() of "64" with the following non-sleepablelocks held: > > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked @ net/netisr.c:215 > > For what it's worth, these warnings also appear if netisr direct > dispatch is enabled with the fxp(4) driver. These messages occur because our link layer address management code does mallocs with M_WAITOK. We need to teach that code to not wait when called from the interrupt path, and pass back up failure modes, or avoid holding locks while calling it. Probably the former, although the latter is also going to be good from a lock order perspective. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Is DRI on FreeBSD unmaintained?
On Sat, 2003-06-21 at 09:12, Lefteris Chatzibarbas wrote: > Hello, > > I believe that the web page related to DRI on BSD (FreeBSD and NetBSD) > is: > > http://people.freebsd.org/~anholt/dri/index.html > > I have mailed both this mailing list and [EMAIL PROTECTED] (contact address > as stated in the aforementioned web page), about a problem with DRI on > FreeBSD and OpenGL and got no answer (10 days have passed since then). > > Is DRI on FreeBSD unmaintained? Am I sending my problem report to the > wrong place? What should I do or who should I contact about this? > > My message to this mailing list: > > http://lists.freebsd.org/pipermail/freebsd-current/2003-June/004859.html There are known problems with the DRI that Eric ([EMAIL PROTECTED]) is currently unable to fix (due to time and $$ problems). I think he got tired of answering the same question over and over, and has resorted to ignoring some emails. He is also very busy with school. You might join #XFree86 on irc.freenode.net if you *really* need to get help. There are many people in there with plenty of experience with the DRI. Eric even stops by on occasion. -- Adam <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: Email accounts on FreeBSD 5.1-RELEASE
Hi, Your language is not the problem, I think everyone here understands what you're saying, just not what you mean. I assume you want to give people e-mail accounts and nothing more. No SSH, no FTP, nothing. In that case, creating a full-blown system account is not only a waste of resources, it's also potentially insecure and adds a lot of administrative concerns. I'd suggest you go with a virtual-domain type of mail hosting. Personally I've used qmail (the mail server - you should replace sendmail with this one on your system anyway) with both vmailmgr and vpopmail, which go about slightly differently trying to solve roughly the same problem. Basically they implement their own authentication scheme, not requiring any system accounts (well .. one is needed for administration and storage of the virtual domains, but that can be either your own account or a special account you set up for that purpose). I'd say vpopmail is closest to what you want, atleast among the solutions I've tested personally. I suggest you do a bit of googling, there are several good HOWTOs out there describing in detail how to set up qmail and these tools. Sometimes you'll have to adopt it a bit for FreeBSD, but in general that's not a problem. Good luck! /Eirik On Fri, 2003-06-20 at 23:16, Alex Ayala wrote: > Ok, maybe...yes I read what I wrote and didn't quite explain what I really > wanted to say. > > I want to setup accounts on my box so users can retrieve emails by accessing > my pop server. Do I need to setup user accounts on my box with the "adduser" > command? I don't want them to be able to have access to the shell by any > means. Is like when I wanted to give someone access to my ftp server I just > created an account and took out the shell part in the passwd file. Sorry my > english is not the greatest. Trying to explain something and can't find the > right words. > > Is that a bit better to understand? > > A > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Mark Murray > Sent: Friday, June 20, 2003 4:51 PM > To: Alex Ayala > Cc: [EMAIL PROTECTED] > Subject: Re: Email accounts on FreeBSD 5.1-RELEASE > > > "Alex Ayala" writes: > > > > I got a question, if I want to create an email account on my Freebsd 5.1 > > box, but not let them have shell access do I just do a "adduser" and > specify > > /sbin/nologin? > > "If I want an off-road vehicle, do I just buy a Land Rover?" It usually > comes to quite a lot more than that, depending on what it is you want > to do _exactly_. > > The above will work in certain circumstances, but simple testing will > tell you that. What we can't tell is whether you need a Land Rover or > a Bulldozer. :-) > > M > -- > Mark Murray > iumop ap!sdn w,I idlaH > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" signature.asc Description: This is a digitally signed message part
Re: Email accounts on FreeBSD 5.1-RELEASE
On Fri, Jun 20, 2003 at 05:16:11PM -0400, Alex Ayala wrote: > Ok, maybe...yes I read what I wrote and didn't quite explain what I really > wanted to say. > > I want to setup accounts on my box so users can retrieve emails by accessing > my pop server. Do I need to setup user accounts on my box with the "adduser" > command? I don't want them to be able to have access to the shell by any > means. Is like when I wanted to give someone access to my ftp server I just > created an account and took out the shell part in the passwd file. Sorry my > english is not the greatest. Trying to explain something and can't find the > right words. > > Is that a bit better to understand? The answer depends a bit on which pop server you're using. If you don't want to create user accounts on the box for mail users then use something like Cyrus, which manages it's own authentication and so doesn't require any system accounts to be created for mail users. -- Tis a wise thing to know what is wanted, wiser still to know when it has been achieved and wisest of all to know when it is unachievable for then striving is folly. [Magician] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Current kernel Fatal Trap 12
At 12:21 PM 6/20/2003 -0400, Robert Watson wrote:
>If you have a version of the kernel in question on disk and with debugging
>symbols, could you attach gdb -k to it and send us the results of:
>
> l *0xc01f6212
>
>That will provide a bit more information about where the panic is
>occuring. This is likely a NULL pointer dereference.
I was able to capture the whole error, there are 2 instruction pointers that I checked:
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000
cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000
io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec0
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0xcf8f9fec
fault code = supervisor write, page not present
instruction pointer = 0x8:0xc032188c
stack pointer = 0x10:0xc04c7bbc
frame pointer = 0x10:0xc04c7bbc
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
trap number = 12
panic: page fault
cpuid = 0; lapic.id =
Uptime: 1s
WARNING: Driver mistake: make_dev(geom.ctl) called before SI_SUB_DRIVERS
(kgdb) l *0xc032188c
0xc032188c is in cpu_thread_setup (../../../i386/i386/vm_machdep.c:312).
307 {
308
309 td->td_pcb =
310 (struct pcb *)(td->td_kstack + KSTACK_PAGES * PAGE_SIZE) - 1;
311 td->td_frame = (struct trapframe *)((caddr_t)td->td_pcb - 16) - 1;
312 td->td_pcb->pcb_ext = NULL;
313 }
314
315 /*
316 * Initialize machine state (pcb and trap frame) for a new thread about to
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0x38
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc01f813e
stack pointer = 0x10:0xc04c776c
frame pointer = 0x10:0xc04c776c
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 0 (swapper)
trap number = 12
panic: page fault
cpuid = 0; lapic.id =
Uptime: 1s
(kgdb) l *0xc01f813e
0xc01f813e is in device_shutdown (../../../kern/subr_bus.c:1499).
1494}
1495
1496int
1497device_shutdown(device_t dev)
1498{
1499if (dev->state < DS_ATTACHED)
1500return (0);
1501return (DEVICE_SHUTDOWN(dev));
1502}
1503
Manfred
==
|| [EMAIL PROTECTED] ||
|| Ph. (415) 681-6235 ||
==
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: locking problems in IPv6 code
Hiten Pandya wrote: > On Thu, Jun 19, 2003 at 03:17:03PM -0700, John-Mark Gurney wrote: > > I am running FreeBSD 5.1-R on a sparc64 machine, and am getting warnings > > about mallocing data w/ a lock aquired. > > > > dmesg output: > > malloc() of "64" with the following non-sleepablelocks held: > > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked @ net/netisr.c:215 > > For what it's worth, these warnings also appear if netisr direct > dispatch is enabled with the fxp(4) driver. There are basically 2 structures of exactly 64 bytes in the kernel; one is the zombie structure, and the other is the template structure for TCP. I'm going to guess that this one is the template structure, if you are interested in tracking down the problem. -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Software watchdog patch
On Fri, Jun 20, 2003 at 09:47:07PM -0500, Sean Kelly wrote: > Greetings. > I look forward to any feedback, whether positive or negative. Hello Sean, this stuff looks really promising. Anyways, I can't comment about the code as I have had no time to read it, but here are a few mdoc nitpicks I did: Index: share/man/man4/watchdog.4 === +is implemented via a trio of sysctl OIDs. When +.Va debug.watchdog.enabled Hmm, the .Va should be replaced with .Li. Also, it is necessary to remove all hard sentence breaks, ie. instead of: "via a trio of sysctl OIDs. When..." It should be: "via a trio of sysctl OIDs. When..." Sysctls should be documented using .Li. +.Sh SEE ALSO +.Xr watchdogd 8 , +.Xr sysctl 8 +.Sh HISTORY Manual pages are first ordered by their section numbers, and then alphabetically, thus watchdogd(8)'s .Xr should be after sysctl(8). +.Sh AUTHORS +.An -nosplit +The +.Nm +code and man page were written by +.An Sean Kelly Aq [EMAIL PROTECTED] . Use `manual page' instead of `man page'. Same sort of comments apply to the watchdogd(8) manual page. Hope that helps. Cheers. -- Hiten ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Is DRI on FreeBSD unmaintained?
Hello, I believe that the web page related to DRI on BSD (FreeBSD and NetBSD) is: http://people.freebsd.org/~anholt/dri/index.html I have mailed both this mailing list and [EMAIL PROTECTED] (contact address as stated in the aforementioned web page), about a problem with DRI on FreeBSD and OpenGL and got no answer (10 days have passed since then). Is DRI on FreeBSD unmaintained? Am I sending my problem report to the wrong place? What should I do or who should I contact about this? My message to this mailing list: http://lists.freebsd.org/pipermail/freebsd-current/2003-June/004859.html Thanks ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: locking problems in IPv6 code
On Thu, Jun 19, 2003 at 03:17:03PM -0700, John-Mark Gurney wrote: > I am running FreeBSD 5.1-R on a sparc64 machine, and am getting warnings > about mallocing data w/ a lock aquired. > > dmesg output: > malloc() of "64" with the following non-sleepablelocks held: > exclusive sleep mutex netisr lock r = 0 (0xc0271890) locked @ net/netisr.c:215 For what it's worth, these warnings also appear if netisr direct dispatch is enabled with the fxp(4) driver. Cheers. -- Hiten ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: acpi patch for dell laptop?
> On Fri, Jun 20, 2003 at 05:29:30PM -0400, Mike Sturdee wrote: > > Where can I find the latest, greatest patch that fixes this? > > Try this URL: > > http://sandcat.nl/~stijn/freebsd/dell.php > > and let me know if it works. > > --Stijn just to confirm that it works on a Dell Latitude C800 danny ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cardbus and xircom ethernet problem
Hi, I have just got hold of an old laptop which has a xircom creditcard ethernet 10/100+ modem 56 card in it (CEM56-100). I installed FreeBSD 5.1-RELEASE on the laptop with no problems at all. Everything is detected and working fine except this ethernet card. This is obviously a really big problem as I wish to cvsup it to -current! The problem I have is that when the card is inserted, or just left in there as the laptop boots I get this appear on console: pccard0: Card has no functions! cbb0: PC Card card activation failed In the boot sequence I see the following: cbb0: at device 4.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 cbb1: at device 4.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1 It is currently FreeBSD 5.1-RELEASE. I have no experience with laptop's and FreeBSD and so I may have just forgotton to do something. I looked through defaults/rc.conf and the only related thing I could find was pccard_enable which I tried setting but I get the same result. I tried recompilnig the kernel with xe, cbb, pcic, pccard, cardbus specifically in there and same thing as GENERIC. The card worked fine when it was running win2k before. Any ideas? Regards, Matt. -- email: [EMAIL PROTECTED] - web: http://xtaz.co.uk/ Hardware, n.: The parts of a computer system that can be kicked. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
WARNING: ttyname(3)/sshd breakage fixed.
If you reinstalled libc with the previous version of ttyname.c your sshd will likely get confused and refuse access. Apologies... Poul-Henning In message <[EMAIL PROTECTED]>, Poul-Henning Kamp writes: >phk 2003/06/21 01:16:12 PDT > > FreeBSD src repository > > Modified files: >lib/libc/gen ttyname.c > Log: > ttyname(3) must return absolute pathnames. > > Noticed by: kris > > Revision ChangesPath > 1.14 +8 -2 src/lib/libc/gen/ttyname.c > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
