On Tuesday 13 July 2010 03:54:08 PseudoCylon wrote:
> Should the debugging code, usb_pause_mtx(), be left in the code for
> testing? If the drivers don't panic to begin with, we won't know the
> patch really fixed the issue.
>
No, I think it is safe to remove it.
--HPS
___
- Original Message
> From: PseudoCylon
> To: Ganbold Tsagaankhuu
> Cc: Ganbold ; freebsd-current@freebsd.org
> Sent: Tue, July 6, 2010 12:26:58 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> >> From: Ganbold
> >> To: PseudoCylon
> >> Cc: freebsd-
- Original Message
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: Andrew Thompson ; Sam Leffler ;
>PseudoCylon ; freebsd-...@freebsd.org
> Sent: Mon, July 12, 2010 2:01:11 PM
> Subject: Re: [panic] Race in IEEE802.11 layer towards device drivers
>
> Hi Andrew,
>
>
Upgrading your pool to version 15, compared to version 14, you get only
these additional features:
- user and group quotas
- getting rid of the old version message in zpool status (-x)
and these disadvantages:
- not importable and/or operable with pre-v15 kernel module and updated
boot loader code
Howdy,
If anyone is using hwpmc on core architectures, i.e. Core, Core2, Nehalem,
Westmere, can you
please test the following patch which fixes occasional panics of this code on
those
processors? The specific bug address comes when sampling the IAF (Fixed
Function) counters
which are:
IAF
Hi Andrew,
Your patch appears to be working. Can you fix this issue in the other WLAN
drivers aswell? Then send an e-mail to request testing? I had a go at it here:
http://p4web.freebsd.org/@@180844?ac=10
I found another panic issue:
ifconfig wlan0 delete
ifconfig wlan0 destroy
When not assoc
09.07.2010 14:41, Ivan Voras пишет:
On 07/08/10 18:42, Alex Keda wrote:
When booting, I have strange message.
All work OK (processor with hyperthreading, but system seems it as 1 CPU ).
lissyara-gp# dmesg
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 19
2010/7/8 Martin Matuska :
> Hi Jason,
>
> as for me, I am ready to stand for the stability of my v15 upgrade, it
> has been discussed with our zfs team, and we also see it as a kind of a
> starting point.
>
> We generally have two options:
> a) push ZFS v15 now
> - it has been already disussed
> -
On 12 Jul 2010, at 01:07, Andrew Thompson wrote:
> On 8 July 2010 07:13, Hans Petter Selasky wrote:
>> Hi,
>>
>> When supplying wpa_supplicant.conf with incorrect passwords, but a valid
>> SSID,
>> I have seen kernel panics several times when using USB based WLAN dongles.
>> When only supplyin
On Friday, July 09, 2010 10:27:46 pm Boris Kochergin wrote:
> Hans Petter Selasky wrote:
> > On Friday 09 July 2010 19:12:59 Sean Bruno wrote:
> >
> >> In order to come up with the most convoluted problem possible, I present
> >> to you screen shots of a panic from a FreeBSD VM running in QEMU
>
In article <4c3ad4a8@freebsd.org>
Alexander Motin writes:
> I've made a patch to unify PC98 event timer code with the rest of x86.
> Could somebody test it on that hardware, as all I can say now is that it
> builds.
>
> I have no idea about ISA PNP on PC98, so if it doesn't report timer
> pr
Hi.
Kostik Belousov wrote:
> on the HEAD r209908, I see a lot of LORs at the boot. It seems that
> mutex called "ATA state lock" is held over the large period of kernel
> initialization. After the system booted, it seems to operate properly.
Thank you. Now testing alternative solution.
--
Alexa
TB --- 2010-07-12 09:52:36 - tinderbox 2.6 running on freebsd-current.sentex.ca
TB --- 2010-07-12 09:52:36 - starting HEAD tinderbox run for powerpc/powerpc
TB --- 2010-07-12 09:52:36 - cleaning the object tree
TB --- 2010-07-12 09:52:54 - cvsupping the source tree
TB --- 2010-07-12 09:52:54 - /usr
2010/7/12 Doug Barton :
> Howdy,
>
> I use -current on my laptop as my regular X platform, and for the last
> few months I've been noticing that interactivity problems have been
> getting a lot worse, by which I mean that if I have something running in
> the background that is either disk or cpu in
>I use -current on my laptop as my regular X platform, and for the last
>few months I've been noticing that interactivity problems have been
>getting a lot worse, by which I mean that if I have something running in
>the background that is either disk or cpu intensive, anything else I try
>to do on
Hi,
on the HEAD r209908, I see a lot of LORs at the boot. It seems that
mutex called "ATA state lock" is held over the large period of kernel
initialization. After the system booted, it seems to operate properly.
atapci0: port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc000-0xc00f at device 1.1 on pc
Hi.
I've made a patch to unify PC98 event timer code with the rest of x86.
Could somebody test it on that hardware, as all I can say now is that it
builds.
I have no idea about ISA PNP on PC98, so if it doesn't report timer
presence, it may be needed to add to device.hints lines like:
hint.attime
17 matches
Mail list logo
