On Wed, 2010-07-14 at 03:43 +0530, Ritesh Raj Sarraf wrote:
> On Tuesday 13 Jul 2010 00:22:01 Ritesh Raj Sarraf wrote:
> > I applied the 3 patches and tested the kernel. Test results look good.
> > Have not been able to reproduce the bug.
>
> Sorry. It hit back again.
>
>
> [76572.837634] TOMOY
On Tuesday 13 Jul 2010 00:22:01 Ritesh Raj Sarraf wrote:
> I applied the 3 patches and tested the kernel. Test results look good.
> Have not been able to reproduce the bug.
Sorry. It hit back again.
[76572.837634] TOMOYO-WARNING: Domain ' /etc/init.d/kdm
/sbin/start-stop-daemon /usr/bin/kdm /e
On Monday 12 Jul 2010 02:05:59 Ben Hutchings wrote:
> > > Please apply those patches and re-test...
> > Which patches ?
>
> These ones.
I applied the 3 patches and tested the kernel. Test results look good. Have
not been able to reproduce the bug.
Thanks,
Ritesh
--
Ritesh Raj Sarraf | http://p
On Monday 12 Jul 2010 00:17:41 Ben Hutchings wrote:
> > It was triggered again while running `git fsck` on linux tree. Bad part
> > is, the wifi device went offline. Not even a driver reload helped. Had
> > to reboot the laptop. dmesg is attached.
>
> Please apply those patches and re-test...
W
On Sun, 2010-07-11 at 23:42 +0530, Ritesh Raj Sarraf wrote:
> On Thursday 20 May 2010 00:10:52 maximilian attems wrote:
> > yep but without the iwlwifi patches, i have still to add
> > f82a924cc88a5541df1d4b9d38a0968cd077a051 on top of the two patches.
> >
> > currently moving around so most like
On Wed, May 19, 2010 at 11:56:34PM +0530, Ritesh Raj Sarraf wrote:
> On Tuesday 18 May 2010 11:21:10 Ritesh Raj Sarraf wrote:
> > Hello Ben,
> >
> > On Sunday 16 May 2010 01:18:36 Ben Hutchings wrote:
> > > > [29747.217066] iwlagn :03:00.0: Failed to allocate SKB buffer with
> > > > GFP_ATOMIC
On Tuesday 18 May 2010 11:21:10 Ritesh Raj Sarraf wrote:
> Hello Ben,
>
> On Sunday 16 May 2010 01:18:36 Ben Hutchings wrote:
> > > [29747.217066] iwlagn :03:00.0: Failed to allocate SKB buffer with
> > > GFP_ATOMIC. Only 1 free buffers remaining.
> >
> > [...]
> >
> > You are not testing th
Hello Ben,
On Sunday 16 May 2010 01:18:36 Ben Hutchings wrote:
> > [29747.217066] iwlagn :03:00.0: Failed to allocate SKB buffer with
> > GFP_ATOMIC. Only 1 free buffers remaining.
>
> [...]
>
> You are not testing the right kernel version. This error message was
> removed by the first patc
On Sat, 2010-05-15 at 00:05 +0530, Ritesh Raj Sarraf wrote:
> On Friday 14 May 2010 23:00:51 maximilian attems wrote:
> > On Fri, May 14, 2010 at 09:15:37PM +0530, Ritesh Raj Sarraf wrote:
> > > > thanks, not yet boot test, need to finish something.
> > >
> > > Triggered again after 2 suspend cycl
On Sat, May 15, 2010 at 12:05:19AM +0530, Ritesh Raj Sarraf wrote:
> On Friday 14 May 2010 23:00:51 maximilian attems wrote:
> > On Fri, May 14, 2010 at 09:15:37PM +0530, Ritesh Raj Sarraf wrote:
> > > > thanks, not yet boot test, need to finish something.
> > >
> > > Triggered again after 2 suspe
On Fri, May 14, 2010 at 09:15:37PM +0530, Ritesh Raj Sarraf wrote:
> >
> > thanks, not yet boot test, need to finish something.
>
> Triggered again after 2 suspend cycles.
grr, can you repost the first appearance of it.
thanks
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian
On Friday 14 May 2010 06:42:27 maximilian attems wrote:
> dropped the fedora iwlwifi patch queue, this time it's just
> current repo + 2 page Rx patches, checked that they applied:
> (+) OK bugfix/all/0001-iwlwifi-use-paged-Rx.patch
> (+) OK bugfix/all/0001-iwlwifi-fix-AMSDU-Rx-after-paged-Rx
dropped the fedora iwlwifi patch queue, this time it's just
current repo + 2 page Rx patches, checked that they applied:
(+) OK bugfix/all/0001-iwlwifi-use-paged-Rx.patch
(+) OK bugfix/all/0001-iwlwifi-fix-AMSDU-Rx-after-paged-Rx-patch.patch
--> 13 fully applied.
please test this linux-im
On Thu, May 13, 2010 at 03:37:00AM +0100, Ben Hutchings wrote:
>
> I think you've done something wrong in building that kernel. This patch
> removes padding of the RX buffers so that they are order-1 rather than
> order-2 (or on the 3945, order-0 rather than order-1). I don't see any
> way you c
On Tue, 2010-05-11 at 15:47 +0200, maximilian attems wrote:
> On Tue, May 11, 2010 at 02:09:06PM +0530, Ritesh Raj Sarraf wrote:
> > On Tuesday 11 May 2010 12:32:45 Ritesh Raj Sarraf wrote:
> > > Thanks Max. Am currently testing it. Will report results in a day or two.
> >
> > The bug got trigger
On Tue, May 11, 2010 at 02:09:06PM +0530, Ritesh Raj Sarraf wrote:
> On Tuesday 11 May 2010 12:32:45 Ritesh Raj Sarraf wrote:
> > Thanks Max. Am currently testing it. Will report results in a day or two.
>
> The bug got triggered in the very first run. Does not look fixed. dmesg
> attached.
yes
On Monday 10 May 2010 23:19:42 maximilian attems wrote:
> backported both on top of fedora iwlwifi linux-2.6 upstream merged
> patches, test build is at:
> http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.32-5-amd64_2.6.32-13_amd64.deb
> http://charm.itp.tuwien.ac.at/~mattems/linux-image-2.6.
On Thu, 06 May 2010, Ben Hutchings wrote:
> tag 580124 fixed-upstream
> thanks
>
> This should be fixed by the following upstream changes included in Linux
> 2.6.33:
>
> commit 2f301227a1ede57504694e1f64839839f5737cac
> Author: Zhu Yi
> Date: Fri Oct 9 17:19:45 2009 +0800
>
> iwlwifi: us
On Sun, May 09, 2010 at 10:16:55PM +0530, Ritesh Raj Sarraf wrote:
>
> All these messages (this one and the previous one with iwlwifi) get triggered
> only when there is heavy I/O activity.
> I don't think this bug is related to iwlwifi. What do you think ?
it is, can trigger it easily on x61s,
On Sunday 09 May 2010 21:38:25 Ritesh Raj Sarraf wrote:
> On Thursday 06 May 2010 07:16:01 Ben Hutchings wrote:
> > On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
> > > Package: linux-2.6
> > > Version: 2.6.32-11
> > > Severity: normal
> > >
> > > I often keep getting this allocation
On Thursday 06 May 2010 07:16:01 Ben Hutchings wrote:
> On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
> > Package: linux-2.6
> > Version: 2.6.32-11
> > Severity: normal
> >
> > I often keep getting this allocation failure message. My gut feel is
> > that it gets triggered when I do s
tag 580124 fixed-upstream
thanks
This should be fixed by the following upstream changes included in Linux
2.6.33:
commit 2f301227a1ede57504694e1f64839839f5737cac
Author: Zhu Yi
Date: Fri Oct 9 17:19:45 2009 +0800
iwlwifi: use paged Rx
commit fafaf31bf9f965d91462ee115e27ef6c262b74ea
Autho
On Mon, 2010-05-03 at 23:58 +0530, Ritesh Raj Sarraf wrote:
> Package: linux-2.6
> Version: 2.6.32-11
> Severity: normal
>
> I often keep getting this allocation failure message. My gut feel is
> that it gets triggered when I do some I/O. Today, it got triggered when
> I was copying a couple of Gi
Package: linux-2.6
Version: 2.6.32-11
Severity: normal
I often keep getting this allocation failure message. My gut feel is
that it gets triggered when I do some I/O. Today, it got triggered when
I was copying a couple of Gig data from my local encrypted backup
partition to an external USB disk.
24 matches
Mail list logo
