Yioryos Asprobounitis | 1 Apr 07:47 2012
Picon

3.3 kernel issue (?)

Hi,

I have a strange problem that I _think_ is an aufs issue.

I'm developing puppylinux for the OLPC XO laptops.
Using the latest 3.3 olpc kernel and aufs3.3/aufs-util3, the XO-1 (an AMD Geode-LX, i586 machine) fails to
find the /lib/firmware/usb8633.bin wifi firmware when the file is at the bottom branch.
However, when the same file is copied from the bottom branch to the "middle" branch (the puppy "savefile")
so it is present in both, works fine!
There is nothing in the kernel log relevant other that the notion of failing to find the firmware, and auchk
reports no issues in any branch.

This is something 3.3-specific as 2.6.35- and 3.1-olpc-kernels/aufs work fine with the exact same setup
and firmware file. Also the 3.3-kernel/wifi-firmware work fine with non-aufs kernel/distros

There are several things that are a bit different in puppy/olpc builds that might cause the problem.
Puppy has a patch that allows aufs to load squashfs as a branch. The bottom branch in the distro is an sfs but
the middle one is not.
The wifi module in the specific hardware is a USB module (the non-usb wifi module of the VIA7C, i686, XO-1.5
has no issues with 3.3/aufs in the same setup)
The olpc-kernels has some hardware-specific changes compared to the vanilla ones (though not many in 3.3
and not related to fs or usb)

Besides this problem, I have not noticed any other file/app issues but this is a serious one as the laptop was
no other way to connect to the web.
I would appreciate if you have any insight on how to diagnose this problem, and hopefully fix it.
Thanks.

------------------------------------------------------------------------------
This SF email is sponsosred by:
(Continue reading)

sfjro | 1 Apr 09:42 2012
Picon
Picon

Re: 3.3 kernel issue (?)


Hello Yioryos,

Yioryos Asprobounitis:
> I have a strange problem that I _think_ is an aufs issue.

Please report more info.
(from the aufs README file)
----------------------------------------------------------------------
When you have any problems or strange behaviour in aufs, please let me
know with:
- /proc/mounts (instead of the output of mount(8))
- /sys/module/aufs/*
- /sys/fs/aufs/* (if you have them)
- /debug/aufs/* (if you have them)
- linux kernel version
  if your kernel is not plain, for example modified by distributor,
  the url where i can download its source is necessary too.
- aufs version which was printed at loading the module or booting the
  system, instead of the date you downloaded.
- configuration (define/undefine CONFIG_AUFS_xxx)
- kernel configuration or /proc/config.gz (if you have it)
- behaviour which you think to be incorrect
- actual operation, reproducible one is better
- mailto: aufs-users at lists.sourceforge.net
----------------------------------------------------------------------

Also I'd suggest you to check the whiteouts (or diropq) on the upper branch.

> Puppy has a patch that allows aufs to load squashfs as a branch. The bottom branch in the distro is an sfs but
(Continue reading)

Yioryos Asprobounitis | 1 Apr 12:03 2012
Picon

Re: 3.3 kernel issue (?)

--- On Sun, 4/1/12, sfjro <at> users.sourceforge.net <sfjro <at> users.sourceforge.net> wrote:

> From: sfjro <at> users.sourceforge.net <sfjro <at> users.sourceforge.net>
> Subject: Re: 3.3 kernel issue (?)
> To: "Yioryos Asprobounitis" <mavrothal <at> yahoo.com>
> Cc: aufs-users <at> lists.sourceforge.net
> Date: Sunday, April 1, 2012, 3:42 AM
> 
> Hello Yioryos,
> 
> Yioryos Asprobounitis:
> > I have a strange problem that I _think_ is an aufs
> issue.
> 
> Please report more info.
> (from the aufs README file)
> ----------------------------------------------------------------------
> When you have any problems or strange behaviour in aufs,
> please let me
> know with:
> - /proc/mounts (instead of the output of mount(8))
> - /sys/module/aufs/*
> - /sys/fs/aufs/* (if you have them)
> - /debug/aufs/* (if you have them)
> - linux kernel version
>   if your kernel is not plain, for example modified by
> distributor,
>   the url where i can download its source is necessary
> too.
> - aufs version which was printed at loading the module or
(Continue reading)

sfjro | 1 Apr 16:45 2012
Picon
Picon

Re: 3.3 kernel issue (?)


Yioryos Asprobounitis:
> Thank you for your prompt response.
> The data you requested (and I have) is attached.

Ok, and how did you specify the path "/lib/firmware/usb8633.bin"?
According to olpc-2.6/drivers/net/wireless/libertas/if_usb.c, the
driver searches
- "libertas/usb8388_olpc.bin"
- "libertas/usb8388_v9.bin"
- "libertas/usb8388_v5.bin"
- "libertas/usb8388.bin"
- "usb8388.bin"
- "libertas/usb8682.bin"
by default, and doesn't know about usb8633.bin.
But the behaviour may be changed if you correctly specify the firmware
path. I don't know how to do it though.

> > Also I'd suggest you to check the whiteouts (or diropq) on
> > the upper branch.
> 
> could not see anything strange. Should I be looking for something specific?

If there exists a whiteout (whose name begins with ".wh."), the it may
hide the lower files. You should check it on /initrd/pup_rw.
For example,
# find /initrd/pup_rw -name '.wh.*'

J. R. Okajima

(Continue reading)

Yioryos Asprobounitis | 1 Apr 19:04 2012
Picon

Re: 3.3 kernel issue (?)


--- On Sun, 4/1/12, sfjro <at> users.sourceforge.net <sfjro <at> users.sourceforge.net> wrote:

> From: sfjro <at> users.sourceforge.net <sfjro <at> users.sourceforge.net>
> Subject: Re: 3.3 kernel issue (?)
> To: "Yioryos Asprobounitis" <mavrothal <at> yahoo.com>
> Cc: aufs-users <at> lists.sourceforge.net
> Date: Sunday, April 1, 2012, 10:45 AM
> 
> Yioryos Asprobounitis:
> > Thank you for your prompt response.
> > The data you requested (and I have) is attached.
> 
> Ok, and how did you specify the path
> "/lib/firmware/usb8633.bin"?
> According to
> olpc-2.6/drivers/net/wireless/libertas/if_usb.c, the
> driver searches
> - "libertas/usb8388_olpc.bin"
> - "libertas/usb8388_v9.bin"
> - "libertas/usb8388_v5.bin"
> - "libertas/usb8388.bin"
> - "usb8388.bin"
> - "libertas/usb8682.bin"
> by default, and doesn't know about usb8633.bin.

Correct, but usb8388.bin and the firmware for the  XO-1.5 wifi (sd8686) are the _only_ files in
/lib/firmware in these builds.
Also would be hard to understand why copying this file to the middle layer make it now "discoverable" and "selectable".

(Continue reading)

sfjro | 1 Apr 19:22 2012
Picon
Picon

Re: 3.3 kernel issue (?)


Yioryos Asprobounitis:
> Also I have the same inability to find the firmware, even at first boot with only the lower ro and the upper rw
branches, so whiteouts should not be the issue, I think.

Ok then,
- setup to receive the kernel debug log
- echo 1 > /sys/module/aufs/parameters/debug
- ls /lib/firmware
- file /lib/firmware/usb8633.bin
- echo 0 > /sys/module/aufs/parameters/debug
and show me the kernel debug log.

J. R. Okajima

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

Yioryos Asprobounitis | 1 Apr 22:04 2012
Picon

Re: 3.3 kernel issue (?)

--- On Sun, 4/1/12, sfjro <at> users.sourceforge.net <sfjro <at> users.sourceforge.net> wrote:

> From: sfjro <at> users.sourceforge.net <sfjro <at> users.sourceforge.net>
> Subject: Re: 3.3 kernel issue (?)
> To: "Yioryos Asprobounitis" <mavrothal <at> yahoo.com>
> Cc: aufs-users <at> lists.sourceforge.net
> Date: Sunday, April 1, 2012, 1:22 PM
> 
> Yioryos Asprobounitis:
> > Also I have the same inability to find the firmware,
> even at first boot with only the lower ro and the upper rw
> branches, so whiteouts should not be the issue, I think.
> 
> Ok then,
> - setup to receive the kernel debug log
> - echo 1 > /sys/module/aufs/parameters/debug
> - ls /lib/firmware
> - file /lib/firmware/usb8633.bin
> - echo 0 > /sys/module/aufs/parameters/debug
> and show me the kernel debug log.

Attached.

Hopefully you can get some idea because I don't :-)

Thanks again
Yioryos

> 
> 
(Continue reading)

sfjro | 2 Apr 05:05 2012
Picon
Picon

Re: 3.3 kernel issue (?)


Yioryos Asprobounitis:
> > - setup to receive the kernel debug log
> > - echo 1 > /sys/module/aufs/parameters/debug
> > - ls /lib/firmware
> > - file /lib/firmware/usb8633.bin
> > - echo 0 > /sys/module/aufs/parameters/debug
> > and show me the kernel debug log.
>
> Attached.
>
> Hopefully you can get some idea because I don't :-)

Unfortunately I am afraid that you made something wrong with logging.
This log doesn't contain the necessary info.
- ls logs several lines, but it opens only librt-2.10.1.so,
  libc-2.10.1.so, libpthread-2.10.1.so, locale.alias, and LC_COLLATE.
  the log opening /lib/firmware is not left.
- the log messages from file are totally gone.
Will you try again?

Acording to the output of these commands, the file exists and aufs shows
it to you, right?

J. R. Okajima

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
(Continue reading)

sfjro | 2 Apr 05:13 2012
Picon
Picon

Re: 3.3 kernel issue (?)


I looked olpc-2.6#x86-3.3 again, and found the recent bug is kept in
this branch.
The commit
f132c5b 2012-03-22 Fix full_name_hash() behaviour when length is a multiple of 8
is very important and you should merge it.
I am not sure this is releated to your problem, but it should be surely merged.

J. R. Okajima

> Yioryos Asprobounitis:
> > > - setup to receive the kernel debug log
> > > - echo 1 > /sys/module/aufs/parameters/debug
> > > - ls /lib/firmware
> > > - file /lib/firmware/usb8633.bin
> > > - echo 0 > /sys/module/aufs/parameters/debug
> > > and show me the kernel debug log.
> >
> > Attached.
> >
> > Hopefully you can get some idea because I don't :-)
>
> Unfortunately I am afraid that you made something wrong with logging.
> This log doesn't contain the necessary info.
> - ls logs several lines, but it opens only librt-2.10.1.so,
>   libc-2.10.1.so, libpthread-2.10.1.so, locale.alias, and LC_COLLATE.
>   the log opening /lib/firmware is not left.
> - the log messages from file are totally gone.
> Will you try again?
>
(Continue reading)

sfjro | 2 Apr 05:50 2012
Picon
Picon

aufs2 and aufs3 GIT release


o news
- simply follow the changes in linux-3.4-rcN.

J. R. Okajima

----------------------------------------------------------------------

- aufs2-2.6.git
  none
- aufs2-standalone.git
  none

- aufs3-linux.git
      aufs: update the donator

- aufs3-linux.git#aufs3.x-rcN branch
  Addition to above
      aufs: simply follow the changes for 3.4-rcN

- aufs3-standalone.git
  ditto

- aufs-util.git
  none

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
(Continue reading)


Gmane