Bug 646317 - Fedora 12 13 14B issues with Dell Vostro 3700
Summary: Fedora 12 13 14B issues with Dell Vostro 3700
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-25 06:53 UTC by lukewolf101010
Modified: 2013-01-10 06:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-06-28 11:14:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Dmesg Prior to using proprietary drivers, will upload one with proprietary drivers after I finsh updating so I have a fallback kernel (46.59 KB, application/octet-stream)
2010-10-25 06:53 UTC, lukewolf101010
no flags Details
Dmesg after using Nvidia Driver (44.36 KB, application/octet-stream)
2010-10-25 07:16 UTC, lukewolf101010
no flags Details
Dmesg after using Broadcom wl driver (46.31 KB, application/octet-stream)
2010-10-25 07:17 UTC, lukewolf101010
no flags Details
Dmesg with wl and Bluetooth enabled (48.35 KB, application/octet-stream)
2010-10-25 07:35 UTC, lukewolf101010
no flags Details
Dmesg of a fully working openSUSE 11.3 Installation (77.34 KB, text/plain)
2010-11-05 06:24 UTC, lukewolf101010
no flags Details

Description lukewolf101010 2010-10-25 06:53:12 UTC
Created attachment 455402 [details]
Dmesg Prior to using proprietary drivers, will upload one with proprietary drivers after I finsh updating so I have a fallback kernel

Description of problem:
I receive crashes with Fedora several shortly after:
 plugging in a USB device
 if the Bluetooth is enabled
 When Using the webcam
 When Using Proprietary Broadcom wlan drivers
 When Using Proprietary Nvidia Drivers
I'm able to use it without crashing when I perform none of the above but that cuts down on usability.
Suprisingly Ubuntu works perfectly in this matter but I really don't care to use Ubuntu, I've yet to find the appropriate repos to test with other distros

Version-Release number of selected component (if applicable):
Fedora 12 13 & 14B Potentially other versions of Fedora but untested

How reproducible:
Plug in a USB Device
Turn on Bluetooth in the Bios
Use Proprietary drivers for Broadcom wlan or Nvidia Geforce 330M

Steps to Reproduce:
1. Plug in a USB Device
2. Wait
3. Reboot because of Crash

1. Press F2
2. Go to appropriate menu in bios
3. Turn on Bluetooth
4. wait for it to boot fedora
5. Login
6. Wait
7. Reboot because of crash

1. Start up cheese
2. Watch as the light on the webcam power indicator goes on and as for an instant footage is shown on the screen before it locks up
3. reboot because of crash

1. Install RPM Fusion Repos
2. su -c 'yum install kmod-wl' (or kmod-nvidia)
3. insert password
4. wait for it to install
5. reboot
6. watch as it crashes either shortly after you login or at Plymouth
  
Actual results:
Crashes, cannot enter the ttys, and just generally ruins my day

Expected results:
Fedora to work, with business as usual

Additional info:
The problem seems to get worse if you let it stay, it crashes sooner and sooner after the initial and following attempts to use the system

Also this bug seems related to Bug 613763 & Bug 640755

Comment 1 lukewolf101010 2010-10-25 07:16:48 UTC
Created attachment 455404 [details]
Dmesg after using Nvidia Driver

Comment 2 lukewolf101010 2010-10-25 07:17:16 UTC
Created attachment 455406 [details]
Dmesg after using Broadcom wl driver

Comment 3 lukewolf101010 2010-10-25 07:35:20 UTC
Created attachment 455411 [details]
Dmesg with wl and Bluetooth enabled

Comment 4 lukewolf101010 2010-11-05 06:24:14 UTC
Created attachment 458007 [details]
Dmesg of a fully working openSUSE 11.3 Installation

I've switched over to openSUSE for my laptop, and posted the dmesg, I'm sticking with Fedora for my desktop although in the end openSUSE actually better supports what I need it to do for school, because of the requirement of using M$ "open"XML formats for submitting files for some classes.

Comment 5 Bug Zapper 2011-05-31 10:42:31 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-28 11:14:29 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.