2.6.26-rc8-mm1 - Kernel

This is a discussion on 2.6.26-rc8-mm1 - Kernel ; From: Alan Cox Date: Mon, 7 Jul 2008 21:42:18 +0100 > > 2) You cannot deny the fine mess we have with proprietary modules and > > such these days. It has been quite the pandora's box over time. > ...

+ Reply to Thread
Page 9 of 9 FirstFirst ... 7 8 9
Results 161 to 171 of 171

Thread: 2.6.26-rc8-mm1

  1. Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

    From: Alan Cox
    Date: Mon, 7 Jul 2008 21:42:18 +0100

    > > 2) You cannot deny the fine mess we have with proprietary modules and
    > > such these days. It has been quite the pandora's box over time.

    >
    > You seem to be trying to conflate legal and technical issues here.


    Exactly like the patches we are current discussing.

    Thanks for walking right into that. :-)

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

    > > You seem to be trying to conflate legal and technical issues here.
    >
    > Exactly like the patches we are current discussing.
    >
    > Thanks for walking right into that. :-)


    No - the patches are for technical reasons, certain people seem to be
    trying to attach legal stuff to them - you included, including mad
    conspiracy theories that David was somehow being told by two different
    employers to do this while one of them was also mysteriously not telling
    you to do the same.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

    From: Alan Cox
    Date: Mon, 7 Jul 2008 22:14:27 +0100

    > > > You seem to be trying to conflate legal and technical issues here.

    > >
    > > Exactly like the patches we are current discussing.
    > >
    > > Thanks for walking right into that. :-)

    >
    > No - the patches are for technical reasons,


    Which are? Consistent use of request_firmware()?

    That's pure bullox as far as I can see. Why provide the means to
    do something nobody has had a need for in 6+ years? Who needs
    to load different firmware for the tg3 driver?

    Who needs that capability? Distribution vendors? What for?
    In what case will they need to load different firmware from
    what the driver maintainer tested as a unit?

    Rather, they want separation. I can see no other real impetus.

    And, btw, who has the right to enforce this new burdon upon driver
    maintainers when they have had a working and maintainable system for
    so long?

    I can only see it being about separation, pure and simple.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

    > That's pure bullox as far as I can see. Why provide the means to
    > do something nobody has had a need for in 6+ years? Who needs
    > to load different firmware for the tg3 driver?


    Who needs modules, nobody needed it for years ... you are repeating
    historically failed arguments still.

    > Who needs that capability? Distribution vendors? What for?
    > In what case will they need to load different firmware from
    > what the driver maintainer tested as a unit?


    For some drivers yes. Maybe not tg3.

    > And, btw, who has the right to enforce this new burdon upon driver
    > maintainers when they have had a working and maintainable system for
    > so long?


    The module argument again - see my comment about the sound driver history.

    > I can only see it being about separation, pure and simple.


    Separation - of firmware that can be paged from code that cannot. Of
    stuff that doesn't change from stuff that does. That happens to be good
    engineering.

    Alan
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

    From: Alan Cox
    Date: Tue, 8 Jul 2008 07:36:37 +0100

    > > I can only see it being about separation, pure and simple.

    >
    > Separation - of firmware that can be paged from code that cannot.


    It can't be paged from the drivers we're talking about,
    no matter how hard you try.

    Every chip reset needs the firmware around so it can be
    reloaded into the card.

    This applies to tg3, bnx2, bnx2x, etc. etc. etc.

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. [BUG] 2.6.26-rc8-mm1 - sleeping function called from invalid context at include/linux/pagemap.h:291

    Hi Andrew,

    While booting up and shutting down, x86 machine with 2.6.26-rc8-mm1 kernel,
    kernel bug call trace is shows up in the logs

    iscsid (pid 2163 2162) is running...
    Setting up iSCSI targets: [ 34.577226] BUG: sleeping function called from invalid context at include/linux/pagemap.h:291
    [ 34.602939] in_atomic():1, irqs_disabled():0
    [ 34.615866] 1 lock held by iscsid/2163:
    [ 34.627120] #0: (&mm->mmap_sem){----}, at: [] sys_munmap+0x23/0x3f
    [ 34.649978] Pid: 2163, comm: iscsid Not tainted 2.6.26-rc8-mm1-autotest #1
    [ 34.670212] [] __might_sleep+0xb5/0xba
    [ 34.684660] [] __munlock_pte_handler+0x44/0xf8
    [ 34.701053] [] walk_page_range+0x15b/0x1b4
    [ 34.716574] [] __munlock_vma_pages_range+0x91/0x9e
    [ 34.734022] [] ? __munlock_pmd_handler+0x0/0x10
    [ 34.750860] [] ? __munlock_pte_handler+0x0/0xf8
    [ 34.767654] [] munlock_vma_pages_range+0xf/0x11
    [ 34.784328] [] do_munmap+0xe4/0x1d9
    [ 34.797857] [] sys_munmap+0x30/0x3f
    [ 34.811451] [] sysenter_past_esp+0x6a/0xa5
    [ 34.826806] =======================
    [ OK ]
    [ OK ]

    While shutting down

    Stopping Bluetooth services:[ OK ]
    Starting killall: [ OK ]
    Sending all processes the TERM signal...
    Sending all processes the KILL signal... [ 76.982147] BUG: sleeping function called from invalid context at include/linux/pagemap.h:291
    [ 77.007777] in_atomic():1, irqs_disabled():0
    [ 77.020679] no locks held by iscsid/2163.
    [ 77.033260] Pid: 2163, comm: iscsid Not tainted 2.6.26-rc8-mm1-autotest #1
    [ 77.053985] [] __might_sleep+0xb5/0xba
    [ 77.074205] [] __munlock_pte_handler+0x44/0xf8
    [ 77.098841] [] walk_page_range+0x15b/0x1b4
    [ 77.115703] [] __munlock_vma_pages_range+0x91/0x9e
    [ 77.133117] [] ? __munlock_pmd_handler+0x0/0x10
    [ 77.149880] [] ? __munlock_pte_handler+0x0/0xf8
    [ 77.166634] [] munlock_vma_pages_range+0xf/0x11
    [ 77.183268] [] exit_mmap+0x32/0xf2
    [ 77.196525] [] ? exit_mm+0xc7/0xd3
    [ 77.209911] [] mmput+0x50/0xba
    [ 77.222130] [] exit_mm+0xce/0xd3
    [ 77.234872] [] do_exit+0x20b/0x617
    [ 77.248128] [] ? trace_hardirqs_on+0xb/0xd
    [ 77.263601] [] do_group_exit+0x5f/0x88
    [ 77.277994] [] get_signal_to_deliver+0x2eb/0x32a
    [ 77.294997] [] do_notify_resume+0x93/0x74e
    [ 77.310437] [] ? __lock_acquire+0xbb7/0xbfb
    [ 77.327268] [] ? native_sched_clock+0x84/0x96
    [ 77.342650] [] ? trace_hardirqs_off+0xb/0xd
    [ 77.358450] [] ? native_sched_clock+0x84/0x96
    [ 77.374827] [] work_notifysig+0x13/0x19
    [ 77.389505] =======================
    [ 77.632224] type=1111 audit(1215512324.000:11): user pid=3484 uid=0 auid=4294967295 ses=4294967295 msg='changing system time: exe="/sbin/hwclock" (hostname=?, addr=?, terminal=console res=success)'
    Turning off swap:
    Turning off quotas:
    Unmounting pipe file systems:
    Please stand by while rebooting the system...
    [ 82.377079] md: stopping all md devices.
    [ 83.930821] Restarting system.
    [ 83.940099] machine restart


    0xc046f393 is in sys_munmap (mm/mmap.c:1968).
    1963 struct mm_struct *mm = current->mm;
    1964
    1965 profile_munmap(addr);
    1966
    1967 down_write(&mm->mmap_sem);
    1968 ret = do_munmap(mm, addr, len);
    1969 up_write(&mm->mmap_sem);
    1970 return ret;
    1971 }
    1972

    0xc046cbe9 is in __munlock_pte_handler (include/linux/pagemap.h:291).
    286 /*
    287 * lock_page may only be called if we have the page's inode pinned.
    288 */
    289 static inline void lock_page(struct page *page)
    290 {
    291 might_sleep();
    292 if (TestSetPageLocked(page))
    293 __lock_page(page);
    294 }
    295

    --
    Thanks & Regards,
    Kamalesh Babulal,
    Linux Technology Center,
    IBM, ISTL.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  7. Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin"

    On Jul 3, 2008, David Woodhouse wrote:

    > Now, can someone _please_ give me a straight response to the allegation
    > that the TSO firmware on the tg3 is _optional_ anyway, and that it can
    > work without it?


    FTR, I got two reports from BLAG users, through Jeff Moe, that
    tg3 worked fine with linux-libre, in spite of the complete absence of
    tg3 firmware in there.

    I don't have any specific details about the tg3 hardware in question.

    --
    Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
    Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
    FSFLA Board Member ¡Sé Libre! => http://www.fsfla.org/
    Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  8. Re: 2.6.26-rc8-mm1 - Missing AC97 power save Kconfig?

    Andrew Morton wrote:
    >
    > ftp://ftp.kernel.org/pub/linux/kerne....6.26-rc8-mm1/
    >
    > - Seems to work on my x86 test boxes. It does emit a
    > sleeping-while-atomic warning during exit from an application which
    > holds mlocks. Known problem.
    >
    > - It's dead as a doornail on the powerpc Mac g5. I'll bisect it later.

    [cut]

    I don't know if this is well known, or why no one else noticed if it
    isn't, but the AC97 power-save Kconfig option CONFIG_SND_AC97_POWER_SAVE
    isn't in any of the Kconfig files.

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: 2.6.26-rc8-mm1 - Missing AC97 power save Kconfig?

    On Wed, 09 Jul 2008 15:33:38 -0600 Zan Lynx wrote:

    > Andrew Morton wrote:
    > >
    > > ftp://ftp.kernel.org/pub/linux/kerne....6.26-rc8-mm1/
    > >
    > > - Seems to work on my x86 test boxes. It does emit a
    > > sleeping-while-atomic warning during exit from an application which
    > > holds mlocks. Known problem.
    > >
    > > - It's dead as a doornail on the powerpc Mac g5. I'll bisect it later.

    > [cut]
    >
    > I don't know if this is well known, or why no one else noticed if it
    > isn't, but the AC97 power-save Kconfig option CONFIG_SND_AC97_POWER_SAVE
    > isn't in any of the Kconfig files.


    Did you search for just /SND_AC97_POWER_SAVE/ ? (no CONFIG_)

    ---
    ~Randy
    Linux Plumbers Conference, 17-19 September 2008, Portland, Oregon USA
    http://linuxplumbersconf.org/
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  10. Re: 2.6.26-rc8-mm1 - Missing AC97 power save Kconfig?

    Randy Dunlap wrote:
    > On Wed, 09 Jul 2008 15:33:38 -0600 Zan Lynx wrote:
    >
    >> Andrew Morton wrote:
    >>> ftp://ftp.kernel.org/pub/linux/kerne....6.26-rc8-mm1/
    >>>
    >>> - Seems to work on my x86 test boxes. It does emit a
    >>> sleeping-while-atomic warning during exit from an application which
    >>> holds mlocks. Known problem.
    >>>
    >>> - It's dead as a doornail on the powerpc Mac g5. I'll bisect it later.

    >> [cut]
    >>
    >> I don't know if this is well known, or why no one else noticed if it
    >> isn't, but the AC97 power-save Kconfig option CONFIG_SND_AC97_POWER_SAVE
    >> isn't in any of the Kconfig files.

    >
    > Did you search for just /SND_AC97_POWER_SAVE/ ? (no CONFIG_)


    D'oh! I feel dumb now. Yes, it is in there. Oddly, it is inside
    Generic Devices, which my config has disabled, which somehow disabled
    the option during "make oldconfig" that I *used* to have enabled in
    older configs.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  11. Re: [BUG] 2.6.26-rc8-mm1 - sleeping function called from invalid context at include/linux/pagemap.h:291

    Hi Kamalesh,

    > Hi Andrew,
    >
    > While booting up and shutting down, x86 machine with 2.6.26-rc8-mm1 kernel,
    > kernel bug call trace is shows up in the logs


    That is known bug.
    please turn off CONFIG_UNEVICTABLE_LRU.

    and see below thread.

    [-mm] BUG: sleeping function called from invalid context at include/linux/pagemap.h:290





    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread
Page 9 of 9 FirstFirst ... 7 8 9