** Description changed:

  Tested on 
  Linux host-name 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 
GNU/Linux
  also tested on x686  version of ubuntu 8.10
  Distributor ID:       Ubuntu
  Description:  Ubuntu 8.10
  Release:      8.10
  Codename:     intrepid
  
  When Nvidia proprietary binary modules are loaded.  modules 173 all
  versions, modules 177 all versions, modules 180 all versions.  There is
  a kernel panic every couple boot cycles just after iwlagn begins to
  initiate connection.
  
  this is the last line from the daemon log 
  NetworkManager: <info>  (wlan0): supplicant manager is now in state 1 (from 
0).
  acpid: client connected from 5720[0:0] 
  nm-system-settings: Adding default connection 'Auto eth0' for 
/org/freedesktop/Hal/devices/net_00_22_15_5e_5b_a7
  
  The hardware is an intel 5100 agn chipset and an nvidia 9600gs.  
  blacklisting the iwlagn and iwlcore in /etc/modprobe.d/blacklist stops the 
panic
  
  If there is anything at all that might help solve this problem this is
  very new hardware less than 6 months old I'd be happy to help, my only
  recourse is to try a different wifi card and see if that stops the panic
  as well.
  
  ProblemType: Bug
  Architecture: amd64
  DistroRelease: Ubuntu 8.10
  NonfreeKernelModules: nvidia
  Package: linux-image-2.6.27-11-generic 2.6.27-11.27
  ProcCmdLine: root=UUID=350e9591-f15d-4764-a69c-272e95287576 ro quiet
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.27-11.27-generic
  SourcePackage: linux
+ 
+ Note: This may be interrelated to NetworkManager.   Every 4th or 5th
+ boot  instead of kernel panic or proper boot. NetworkManager has to be
+ manually restarted in order for Wireless to work.
+ 
+ Again this is only a problem if proprietary Nvidia drivers are loaded
+ with iwlagn.

-- 
iwlagn conflicts with nvidia binary drivers 8.10 causes kernel panic
https://bugs.launchpad.net/bugs/329927
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to