Hi
There is a thread in the sqlite mailing list that was started by me,
but it did not finish because it appears that my findings are more
related to the kernel instead of sqlite. I really hope someone here
can give me some guidance.
The summary of my system is:
- kernel 2.6.39.4 (also tested wit
Hi
I am looking for someone to help explain my findings, which I have
searched the net but could not find any related infomation.
We have 40 linux PCs deployed in a mobile environment, so they are
subjected to pretty harsh conditions that can cause BIOS corruptions.
In one of the units, I notice
Hi
We are stress testing the wireless network driver on our linux system.
We use ping flood to saturate the network, and within 24 hours, we
managed to crash the driver.
This was a good test, as it hightlighted a timer problem in the
driver. After fixing that, we are now getting out of memory err
Hi
We have a WIFI driver that only supports a single device at a time. We
want to use 2 devices with the same vendor/device ID, but spawn 2
instances of the same driver. Each instance will handle a single
device.
If we bought the devices from 2 vendors, we'd have 2 DeviceIDs, we can
modify the d
Hi Oliver
You are initialising an interrupt urb with an initializer for
a bulk urb. The behavior is undefined. In older kernels
by random chance a sensible interval was set.
You need to use the correct initializer and the correct interval,
which usually can be read from the device's descriptors
Hi Oliver
What do you use as arguments for usb_fill_bulk_urb() ? One of the sanity tests
in usb_submit_urb() is triggered.
Usage:
usb_fill_bulk_urb(macp->intr_urb, macp->usb,
usb_rcvbulkpipe(macp->usb, EP_INT_IN),
macp->IntEPBuffer, MAX_EPINT_BUFFER,
Hi
We have been using a Zydas based WIFI drivers under kernel 2.6.16.18
with great success. Recently, when we upgraded to 2.6.20.1 (also
tested on 2.6.21.5), we found that during initialisation, these calls
works with USB2.0 but stopped working on USB1.1:
usb_fill_bulk_urb();
usb_submit_urb();
Hi
After many hours to testing, we found that the Hardware Watchdog Timer
module causes our motherboard's BIOS CPU fan control to stop
controlling the fan. On Linux bootup, the fan speed stays constant all
the time.
Setup:
- kernel 2.6.20.1 and 2.6.21.5
- iTCO_wdt loaded with ICH4 chip on mother
Hi
This is just a general question to understand where the improvement
can be made.
In the first setup, I have these processes:
- mencoder recording from bttv chip at 8 fps (cpu 3.5 %)
- mplayer playing from bttv chip at 10 fps (cpu 2.1 %)
In the second setup, I have these processes:
- mencoder
9 matches
Mail list logo
