Comment 50 for bug 132042
Revision history for this message
| Guy Stone (stoneguy3) wrote Re: [Bug 132042] Re: wireless stops working until reboot | #50 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Unfortunately I can't follow up on your request. My base system is 64-bit
Precise, and I only run Quantal in a VM for short periods frequently. This
problem only shows up after several hours of email. torrent, and newsgroup
downloads, and I've never run any VM long enough to show it there. As I
reported previously, the host can be locked up but connectivity in a VM is
unaffected.
I hit the glitch yesterday, so if there's any value in my going through the
apport collect process I'll be happy to do so the next time I hit it.
The problem with replacing my 3.2.0-32-generic kernel with a 3.3.7 version,
even temporarily, is that most likely my VirtualBox installation won't
work, and I'll have to redo the DKMS rigmarole coming and going...
I can't think of a good solution for this without adding another HD and
cloning over my Precise partition. However, I don't have a spare even close
to large enough. Linux is on a 1.10 TB partition of which about 300GB are
in use (including the VDI files current size).
So, if you have any alternative suggestions on how I can be of assistance,
please let me know.
Guy
On Sun, Oct 14, 2012 at 12:47 PM, Christopher M. Penalver <
<email address hidden>> wrote:
> rax_m, thank you for reporting this and helping make Ubuntu better. Fiesty
> reached EOL on October 2008.
> Please see this document for currently supported Ubuntu releases:
> https:/
>
> We were wondering if this is still an issue in a supported release? If
> so, could you please test for this with the latest development release
> of Ubuntu? ISO CD images are available from
> http://
>
> If it remains an issue, could you please run the following command in
> the development release from a Terminal
> (Applications-
> and attach updated debug information to this report:
>
> apport-collect -p linux <replace-
>
> Also, could you please test the latest upstream kernel available following
> https:/
> upstream developers to examine the issue. Please do not test the kernel in
> the daily folder, but the one all the way at the bottom. Once you've tested
> the upstream kernel, please comment on which kernel version specifically
> you tested and remove the tag:
> needs-upstream-
>
> This can be done by clicking on the yellow pencil icon next to the tag
> located at the bottom of the bug description and deleting the text:
> needs-upstream-
>
> If this bug is fixed in the mainline kernel, please add the following tags:
> kernel-
> kernel-
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> If the mainline kernel does not fix this bug, please add the following
> tags:
> kernel-
> kernel-
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> If you are unable to test the mainline kernel, please comment as to why
> specifically you were unable to test it and add the following tags:
> kernel-
> kernel-
>
> where VERSION-NUMBER is the version number of the kernel you tested.
>
> Please let us know your results. Thank you for your understanding.
>
> Helpful Bug Reporting Tips:
> https:/
>
> ** Tags added: fiesty needs-kernel-logs needs-upstream-
>
> ** Attachment removed: "Diff of our rtl8187_dev.c with Linux main kernel"
>
> https:/
>
> ** Changed in: linux (Ubuntu)
> Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> wireless stops working until reboot
>
> To manage notifications about this bug go to:
> https:/
>