[current tinderbox] failure on i386/i386

TB --- 2003-07-27 06:25:00 - starting CURRENT tinderbox run for i386/i386 TB --- 2003-07-27 06:25:00 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-27 06:28:41 - building world TB --- cd /home

Re: device driver memory leak in 5.1-20030726?

On Saturday, July 26, 2003, at 10:02 PM, Gary Jennejohn wrote: Mark Blackman writes: I'm seeing the same 'kmem_malloc(4096): kmem_map too small: X total allocated' messages that a few other have reported. [snip] From these symptoms, I'm speculating that one or more device drivers are produci

Re: device driver memory leak in 5.1-20030726?

On Sun, 27 Jul 2003, Mark Blackman wrote: > Perhaps it's a USB bug. There seems to be some correspondence between > the use of the USB Speedtouch ADSL modem and the out-of-control > devbuf allocations. I'm too seeing these annoying kmem_malloc panics on recent -current kernels. The laptop I'm usi

Re: FreeBSD 5.1-R kernel panic

On Sat, Jul 26, 2003 at 10:48:21PM -0600, Stephane Raimbault wrote: > Well, I had compiled "options DDB" into the kernel and today the kernel > panic'd... here is what I got. I ran the following in the db> prompt. > "trace", "show reg", "ps". Let me know if this is the kind of information > you

Re: device driver memory leak in 5.1-20030726?

On Sun, Jul 27, 2003 at 04:43:32PM +0200, Lukas Ertl wrote: > On Sun, 27 Jul 2003, Mark Blackman wrote: > > > Perhaps it's a USB bug. There seems to be some correspondence between > > the use of the USB Speedtouch ADSL modem and the out-of-control > > devbuf allocations. > > I'm too seeing these

[current tinderbox] failure on alpha/alpha

TB --- 2003-07-27 16:00:01 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-27 16:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-27 16:01:57 - building world TB --- cd /

[current tinderbox] failure on amd64/amd64

TB --- 2003-07-27 17:21:58 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-07-27 17:21:58 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-27 17:23:54 - building world TB --- cd /

Re: FreeBSD 5.1-R kernel panic

Hi Bosko, Thanks for your response. I do not use USB on the system... I'll try removing those devices from the kernel and see if the problem continues. I will let you know. Thanks, Stephane Raimbault. - Original Message - From: "Bosko Milekic" <[EMAIL PROTECTED]> Newsgroups: mailing.

Re: device driver memory leak in 5.1-20030726?

Lukas Ertl writes: > On Sun, 27 Jul 2003, Mark Blackman wrote: > > > Perhaps it's a USB bug. There seems to be some correspondence between > > the use of the USB Speedtouch ADSL modem and the out-of-control > > devbuf allocations. > > I'm too seeing these annoying kmem_malloc panics on recent -c

Re: device driver memory leak in 5.1-20030726?

Lukas Ertl wrote this message on Sun, Jul 27, 2003 at 16:43 +0200: > On Sun, 27 Jul 2003, Mark Blackman wrote: > > > Perhaps it's a USB bug. There seems to be some correspondence between > > the use of the USB Speedtouch ADSL modem and the out-of-control > > devbuf allocations. > > I'm too seeing

Re: device driver memory leak in 5.1-20030726?

Gary Jennejohn writes: > I've observed other problems with -current: > 1) mount_msdos results in a kernel panic (NULL pointer deref) > 2) mounting linuxprocfs also results in a panic > Replying to myself. (2) is wrong. It doesn't panic, it just fails with a message that linuxprocfs doesn't supp

SSH from host to jail

I'm trying to set up some jails in a 5.1R system. I've pretty much copied a setup that was working fine in 4.8; but on 5.1 I can't seem to SSH from the host system into one of its jails. It acts like the packets just aren't getting through. I would really appreciate it if somebody would send me r

Re: Feasibility/Practicality of using GBDE to facilitate encryptedswap, md, /tmp, filesystems

In message <[EMAIL PROTECTED]>, John Stockdale writes: >Hopefully PHK has a chance to look this one over, but if anyone else >has any thoughts I'll take any opinions I can get. ;) I have a number of operations I plan to add to the gbde tool, but some of them has be a bit worried about their foot

[PATCH] Add support for the Intel 852 chipset

Here is a bad that adds i852 support to the AGP system. This seems to work fine on my Dell 5150. Others may want to double-check this first since this isn't my area of expertise. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc --- src/sys/pci/agp_intel.c.origSat Jul 26 00:28:34 200

Re: SSH from host to jail

Pat Lashley wrote: I'm trying to set up some jails in a 5.1R system. I've pretty much copied a setup that was working fine in 4.8; but on 5.1 I can't seem to SSH from the host system into one of its jails. It acts like the packets just aren't getting through. I would really appreciate it if someb

Re: device driver memory leak in 5.1-20030726?

On Sun, 27 Jul 2003, John-Mark Gurney wrote: > Lukas Ertl wrote this message on Sun, Jul 27, 2003 at 16:43 +0200: > > > > I'm too seeing these annoying kmem_malloc panics on recent -current > > kernels. The laptop I'm using is way off of being overloaded at all, the > > only thing I do is going on

LOR with filedesc structure and Giant

After upgrading last night, one of the package machines found this: lock order reversal 1st 0xc6c1c334 filedesc structure (filedesc structure) @ /a/asami/portbuild/i386/src-client/sys/kern/sys_generic.c:902 2nd 0xc04aa120 Giant (Giant) @ /a/asami/portbuild/i386/src-client/sys/fs/specfs/spec_vn

dereferencing type-punned pointer will break strict-aliasing rules

Is this caused by -oS option? - in making BOOTMFS in make release cc -c -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/u

Re: device driver memory leak in 5.1-20030726?

Lukas Ertl wrote this message on Mon, Jul 28, 2003 at 01:11 +0200: > On Sun, 27 Jul 2003, John-Mark Gurney wrote: > Then I have no explanation. I'm running the box with a WiFi card, > generating lots of network traffic, and the box is running fine, no > panics, and low devbuf allocation. I'm runn

Re: LOR with filedesc structure and Giant

On Sun, Jul 27, 2003 at 04:33:51PM -0700, Kris Kennaway wrote: > After upgrading last night, one of the package machines found this: > > lock order reversal > 1st 0xc6c1c334 filedesc structure (filedesc structure) @ > /a/asami/portbuild/i386/src-client/sys/kern/sys_generic.c:902 > 2nd 0xc04aa12

Re: device driver memory leak in 5.1-20030726?

Lukas Ertl wrote this message on Mon, Jul 28, 2003 at 01:11 +0200: > Then I have no explanation. I'm running the box with a WiFi card, > generating lots of network traffic, and the box is running fine, no > panics, and low devbuf allocation. I'm running the box with the USB > Bluetooth dongle, ge

Re: LiveCD FBSD Current

On Sat, 2003-07-26 at 21:09, Sebastian Yepes [ESN] wrote: > On Fri, Jul 25, 2003 at 09:57:04PM -0700, Kris Kennaway wrote: > > On Sat, Jul 26, 2003 at 06:31:03AM +0200, Sebastian Yepes [ESN] wrote: > > > > > > Hi all > > > > > > I have made a liveCD of FreeBSD Current and it boot's and looks like

Re: dereferencing type-punned pointer will break strict-aliasingrules

At Mon, 28 Jul 2003 00:30:35 + (UTC), kuriyama wrote: > Is this caused by -oS option? Grrr, of course this should be s/-oS/-Os/. These warnings are caused from DROP_GIANT() macro. By tracking this down, actual source is __PCPU_GET() macro (line: 115) in sys/i386/include/pcpu.h.

Re: dereferencing type-punned pointer will break strict-aliasingrules

On Mon, Jul 28, 2003 at 10:35:22AM +0900, Jun Kuriyama wrote: > At Mon, 28 Jul 2003 00:30:35 + (UTC), > kuriyama wrote: > > Is this caused by -oS option? > > Grrr, of course this should be s/-oS/-Os/. > > These warnings are caused from DROP_GIANT() macro. By tracking this > down, actual sour

Re: dereferencing type-punned pointer will break strict-aliasingrules

On Mon, 2003/07/28 at 09:30:08 +0900, Jun Kuriyama wrote: > > Is this caused by -oS option? > > - in making BOOTMFS in make release > cc -c -Os -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions

Re: dereferencing type-punned pointer will break strict-aliasingrules

On Mon, 2003/07/28 at 03:59:00 +0200, Thomas Moestl wrote: > Yes, by implying -fstrict-aliasing, so using -fno-strict-aliasing is a > workaround. The problem is caused by the i386 PCPU_GET/PCPU_SET > implementation: > > #define __PCPU_GET(name) ({

Re: Mapping Video BIOS?

On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> Presuming that it's the ROM driver, I get this in the dmesg I posted: >> pnpbios: Bad PnP BIOS data checksum > > That's likely the

Re: Mapping Video BIOS?

In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote: : > In message: <[EMAIL PROTECTED]> : > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : >> Presuming that it's the ROM d

Re: Mapping Video BIOS?

On Sunday, 27 July 2003 at 21:42:35 -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> On Saturday, 26 July 2003 at 22:18:59 -0600, M. Warner Losh wrote: >>> In message: <[EMAIL PROTECTED]> >>> "Greg 'groggy'

Re: Mapping Video BIOS?

In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : Sure. The data at offset 0xc are: : : C000: 55 AA 78 E9 44 06 00 00-00 00 00 00 00 00 00 00 U.x.D... : : The 0xaa55 is the BIOS signature ("Here be a BIOS"), and the 0x78 is : the l

Re: Mapping Video BIOS?

On Sunday, 27 July 2003 at 22:03:57 -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> Sure. The data at offset 0xc are: >> >> C000: 55 AA 78 E9 44 06 00 00-00 00 00 00 00 00 00 00 U.x.D... >> >> The

Re: Mapping Video BIOS?

Where are you getting the data? A windows tool? Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Mapping Video BIOS?

On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote: > Where are you getting the data? A windows tool? If you're talking about the BIOS contents I'm printing, yes, I'm using a Microsoft tool called DEBUG (which has been around since before Microsoft bought DOS :-). Greg -- See comple

Re: Mapping Video BIOS?

In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote: : > Where are you getting the data? A windows tool? : : If you're talking about the BIOS contents I'm printing, yes, I'm using : a Micro

Re: dereferencing type-punned pointer will break strict-aliasingrules

Hmm, it seems this macro is John's baby. John? At Mon, 28 Jul 2003 02:00:50 + (UTC), Thomas Moestl wrote: > > [1 ] > On Mon, 2003/07/28 at 09:30:08 +0900, Jun Kuriyama wrote: > > > > Is this caused by -oS option? > > > > - in making BOOTMFS in make release > > cc -c -Os -pipe -Wall -

Re: Mapping Video BIOS?

On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> On Sunday, 27 July 2003 at 22:11:29 -0600, M. Warner Losh wrote: >>> Where are you getting the data? A windows tool? >> >> If you're

Re: Mapping Video BIOS?

In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote: : > In message: <[EMAIL PROTECTED]> : > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : >> On Sunday, 27 July 2003 at 22:1

Re: Mapping Video BIOS?

On Sunday, 27 July 2003 at 22:32:42 -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> On Sunday, 27 July 2003 at 22:17:32 -0600, M. Warner Losh wrote: >>> In message: <[EMAIL PROTECTED]> >>> "Greg 'groggy' L

Re: Mapping Video BIOS?

In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : On Sunday, 27 July 2003 at 22:32:42 -0600, M. Warner Losh wrote: : > In message: <[EMAIL PROTECTED]> : > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : >> On Sunday, 27 July 2003 at 22:1

[current tinderbox] failure on alpha/alpha

TB --- 2003-07-28 04:00:03 - starting CURRENT tinderbox run for alpha/alpha TB --- 2003-07-28 04:00:03 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-28 04:02:25 - building world TB --- cd /

Recommended kernel config for a dell 8450, 8 cpu, 8GB of ram.

Hi Guys, Just seeking some general information. I've got a couple of dell 8 cpu boxes here running FreeBSD 5.1-RELEASE and am interested in peoples thoughts on the best kernel configs for this type of machine. I'm interested in the best way of making use of 8 cpu's and also seeing the whol

Re: device driver memory leak in 5.1-20030726?

John-Mark Gurney wrote: Lukas Ertl wrote this message on Sun, Jul 27, 2003 at 16:43 +0200: On Sun, 27 Jul 2003, Mark Blackman wrote: Perhaps it's a USB bug. There seems to be some correspondence between the use of the USB Speedtouch ADSL modem and the out-of-control devbuf allocations. I'm too

Re: device driver memory leak in 5.1-20030726?

Scott Long wrote this message on Sun, Jul 27, 2003 at 23:33 -0600: > John-Mark Gurney wrote: > > >It may be leaking, but it won't be leaking devbuf memory. The only > >thing that is in usb (in dev/usb) that uses M_DEVBUF is ukbd. > > bus_dma_tag_create() allocates out of M_DEVBUF. Could it be t

Re: cvs commit: src/sys/cam cam_ccb.h src/sys/cam/scsi scsi_cd.c scsi_da.c src/sys/dev/ata atapi-cam.c src/sys/dev/usb umass.c src/sys/dev/firewire sbp.c

On Sun, 27 Jul 2003, Nate Lawson wrote: > Modified files: > sys/cam cam_ccb.h > sys/cam/scsi scsi_da.c scsi_cd.c > sys/dev/ata atapi-cam.c > sys/dev/usb umass.c > sys/dev/firewire sbp.c > Log: > Add a PATH_INQ flag, PIM_NO_6_BYTE,

[current tinderbox] failure on amd64/amd64

TB --- 2003-07-28 05:22:26 - starting CURRENT tinderbox run for amd64/amd64 TB --- 2003-07-28 05:22:26 - checking out the source tree TB --- cd /home/des/tinderbox/CURRENT/amd64/amd64 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -A src TB --- 2003-07-28 05:24:14 - building world TB --- cd /

Re: device driver memory leak in 5.1-20030726?

Lukas Ertl wrote this message on Sun, Jul 27, 2003 at 16:43 +0200: > I have different core dumps and backtraces available, but they don't seem > to be of much use in this case. I really suspect the USB stuff to be > leaking. Ok, if you truely think this is the case, recompile w/ USB_DEBUG, and aft