After security update ubuntu restarts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.20 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Hi Guys,
Yesterday I received 2 security updates and installed/accepted them (19th July)
A short while later in the day ubuntu started restarting every so often. It appeared that the restarts were only associated with Firefox. I started using Epiphinay and the same thing happens.
I am using unbuntu Feisty 7.04 on an Acer Aspire 5050 Laptop
I have tried googling a solution but only a small handful of people are experiencing the same thing with no replies. Any help would be appreciated. If there is a roll back solution I would welcome that or anything to stop the machine from restarting.
daemon log shows:
Jul 19 09:43:38 blowfish gdm[4845]: gdm_slave_
Jul 19 09:43:50 blowfish NetworkManager: <information>
Jul 19 09:53:31 blowfish gdm[6482]: gdm_slave_
The kernal log shows plenty of :
Jul 19 09:25:17 blowfish kernel: [ 35.538900] hda_codec: invalid dep_range_val 0:7fff all the way up to Jul 19 09:25:17 blowfish kernel: [ 35.632829] hda_codec: invalid dep_range_val 0:7fff
I am not sure if this means anything, it is from the same log
Jul 19 09:39:41 blowfish kernel: [ 573.116697] Losing some ticks... checking if CPU frequency changed.
Jul 19 09:43:49 blowfish kernel: [ 711.427135] hda_codec: num_steps = 0 for NID=0xd
Jul 19 09:53:42 blowfish kernel: [ 1280.941176] hda_codec: num_steps = 0 for NID=0xd
The sys log shows :
Jul 19 09:31:46 blowfish syslogd 1.4.1#20ubuntu4: restart.
Jul 19 09:31:46 blowfish anacron[5084]: Job `cron.daily' terminated
Jul 19 09:31:46 blowfish anacron[5084]: Normal exit (1 job run)
Jul 19 09:39:41 blowfish kernel: [ 573.116697] Losing some ticks... checking if CPU frequency changed.
Jul 19 09:43:38 blowfish gconfd (oliver-5335): Received signal 15, shutting down cleanly
Jul 19 09:43:38 blowfish gconfd (oliver-5335): Exiting
Jul 19 09:43:38 blowfish gdm[4845]: gdm_slave_
Jul 19 09:43:47 blowfish gconfd (oliver-6544): starting (version 2.18.0.1), pid 6544 user 'oliver'
Jul 19 09:43:47 blowfish gconfd (oliver-6544): Resolved address "xml:readonly:
Jul 19 09:43:47 blowfish gconfd (oliver-6544): Resolved address "xml:readwrite:
Jul 19 09:43:47 blowfish gconfd (oliver-6544): Resolved address "xml:readonly:
Jul 19 09:43:47 blowfish gconfd (oliver-6544): Resolved address "xml:readonly:
Jul 19 09:43:47 blowfish gconfd (oliver-6544): Resolved address "xml:readonly:
Jul 19 09:43:48 blowfish gconfd (oliver-6544): Resolved address "xml:readwrite:
Jul 19 09:43:49 blowfish kernel: [ 711.427135] hda_codec: num_steps = 0 for NID=0xd
Jul 19 09:43:50 blowfish NetworkManager: <information>
24th July
The machine restarts whilst browsing.
The last bit of code that I can offer to anyone out there is :
Jul 24 17:01:11 blowfish dhclient: No working leases in persistent database - sleeping.
Jul 24 17:01:21 blowfish gdm[22644]: gdm_slave_
Jul 24 17:03:06 blowfish kernel: [16682.373353] hda_codec: num_steps = 0 for NID=0x19
Jul 24 17:03:06 blowfish NetworkManager: <information>
Jul 24 17:06:07 blowfish dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jul 24 17:06:10 blowfish dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Jul 24 17:06:17 blowfish dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 10
Jul 24 17:06:27 blowfish dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
Jul 24 17:06:39 blowfish dhclient: No DHCPOFFERS received.
Jul 24 17:06:39 blowfish dhclient: No working leases in persistent database - sleeping.
Jul 24 17:08:41 blowfish gdm[23206]: gdm_slave_
Jul 24 17:08:54 blowfish NetworkManager: <information>
Jul 24 17:08:55 blowfish kernel: [16959.272904] hda_codec: num_steps = 0 for NID=0x19
Is there any way to stop the machine from restarting?
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http:// wiki.ubuntu. com/KernelTeamB ugPolicies. Thanks in advance!