Linux bluetooth development
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: Zan Lynx <zlynx@acm.org>
Cc: reiserfs-dev@namesys.com, bluez-devel@lists.sourceforge.net,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bluez-devel] 2.6.21-rc4-mm1
Date: Wed, 21 Mar 2007 12:52:31 +0300	[thread overview]
Message-ID: <4601005F.7020301@namesys.com> (raw)
In-Reply-To: <20070320223643.d8cbc3f6.akpm@linux-foundation.org>

Andrew Morton wrote:

>On Tue, 20 Mar 2007 17:23:54 -0600 Zan Lynx <zlynx@acm.org> wrote:
>
>  
>
>>On Mon, 2007-03-19 at 20:56 -0800, Andrew Morton wrote:
>>    
>>
>>>Temporarily at
>>>
>>>  http://userweb.kernel.org/~akpm/2.6.21-rc4-mm1/
>>>
>>>Will appear later at
>>>
>>>  ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/
>>>      
>>>
>>First impressions:
>>Several of the same bugs as rc3-mm*:
>>      * Freezes immediately if I touch the wlan0 device after loading
>>        the new Broadcom wireless driver.
>>    
>>
>
>cc linux-wireless
>
>  
>
>>      * Freezes immediately if I allow Bluetooth to configure.
>>    
>>
>
>cc bluez-devel
>
>  
>
>>      * All freezes simply stop, no BUG or panic happens, no watchdog,
>>        soft or NMI ever triggers.  Thinking about it, I wonder if
>>        disabling EDAC_K8 would help here?  Does it steal NMI?  I'll try
>>        that later.
>>    
>>
>
>Mabe that will be fixed by the just-uploaded
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc4/2.6.21-rc4-mm1/hot-fixes/tty-in-tiocsctty-when-we-steal-a-tty-hang-it-up-fix.patch
>
>  
>
>>      * I am using Reiser4 and after one of the above freezes and hard
>>        power cycle, files that were in use *read*only* are filled with
>>        zeros.
>>

did you enable compression announced not so long ago?
anyway, it would be better to check your fs by fsck.reiser4

>>  For example, while testing and experiencing the above
>>        freezes, I lost /etc/ld.so.preload
>>        and /lib/security/pam_limits.so.  What the heck?
>>    
>>
>
>cc reiserfs-dev
>  
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2007-03-21  9:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070319205623.299d0378.akpm@linux-foundation.org>
     [not found] ` <1174433034.62033.16.camel@localhost>
2007-03-21  6:36   ` [Bluez-devel] 2.6.21-rc4-mm1 Andrew Morton
2007-03-21  9:52     ` Edward Shishkin [this message]
2007-03-21 14:12     ` Marcel Holtmann
2007-03-23 19:45       ` Zan Lynx
2007-03-21 16:13     ` Larry Finger
2007-03-23 19:40       ` 2.6.21-rc4-mm1 Zan Lynx
2007-03-24  1:49         ` 2.6.21-rc4-mm1 Larry Finger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4601005F.7020301@namesys.com \
    --to=edward@namesys.com \
    --cc=akpm@linux-foundation.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=reiserfs-dev@namesys.com \
    --cc=zlynx@acm.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox