[lkml]   [1999]   [May]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: PCMCIA/network behaviour broken
    > The issue is the behaviour of the kernel when I remove a card.  In 2.0.x,
    > I could remove a live card and it would cleanly remove the associcated
    > interface and routes, and all would be well. This is required in the case
    > where I suspend my laptop and remove the card(s) to fit it into the case.
    > When it resumes, PCMCIA card services shuts down the card (it trivially
    > deals with suddenly non-existant devices, as is the nature of PCMCIA), and
    > the interface disappears.


    > started, never ran those on my laptop), is for the interface to be left in
    > a hung state, with the entire networking stack (or at least the bits I can
    > get to) completely frozen. I'm forced to reboot to clear the state and
    > get back to work.

    The PCMCIA code last time I checked was still calling network device driver
    admin routines from an interrupt. If that hasnt been fixed in pcmcia-cs
    that would explain these kind of behaviours

    > Suspend/resume behaviour has gotten even more strange, with PCMCIA card
    > services removing the modules for the device upon resume, but the
    > interface remaining in the kernel (thus ifconfig output) until I try to
    > remove it, at which point the networking stack freezes.

    If PCMCIA managed to remove a module for an active interface then it is
    broken. Fix the MOD_INC/DEC_USE_COUNT stuff for that module. An interface
    that is up is always 'in use'.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:52    [W:0.080 / U:3.160 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site