John-Mark Gurney writes:
Gary Jennejohn wrote this message on Mon, Jul 28, 2003 at 12:58 +0200:
It appears to me that the test in usb_block_allocmem() should be
(p-tag-parent == tag || p-tag-parent == tag-parent) and NOT
p-tag == tag! That's because bus_dma_tag_create() uses the tag
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
after
Ok, you asked for it..
Jul 28 10:13:02 maddog kernel: usbd_alloc_xfer() = 0xc1c92900
Jul 28 10:13:02 maddog kernel: usbd_bulk_transfer: start transfer 53 bytes
Jul 28 10:13:02 maddog kernel: usbd_transfer: xfer=0xc1c92900, flags=0,
pipe=0xc1bb5480, running=0
Jul 28 10:13:02 maddog kernel:
On Sun, 27 Jul 2003, John-Mark Gurney wrote:
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
John-Mark Gurney writes:
--E/DnYTRukya0zdZ1
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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,
Gary Jennejohn wrote this message on Mon, Jul 28, 2003 at 12:58 +0200:
It appears to me that the test in usb_block_allocmem() should be
(p-tag-parent == tag || p-tag-parent == tag-parent) and NOT
p-tag == tag! That's because bus_dma_tag_create() uses the tag
passed into usb_block_allocmem() as
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
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 using
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 annoying
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 -current
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 these
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 support
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 online
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 running
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,
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
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 that
A backtrace: (where and where full) for those who can decipher them
uma_core.c seems to have been the trigger.
(kgdb) where
#0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
#1 0xc032cc4c in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:372
#2 0xc032cfd7 in panic () at
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 producing kernel memory leaks and either triggering the
19 matches
Mail list logo
