Random reboot without error on jaunty amd64 2.6.28 and 2.6.29

[Bardok]

Hello,

i'm under jaunty up to date and i have a bug : my pc reboot without any error in log and anytime.

See attachments of logs.

Thks for your help.

Bonjour,

je suis sous jaunty à jour et j'ai un problème : mon pc redémarre sans aucune erreur dans les logs et n'importe quand.

ci joint les différentes logs.

Merci pour votre aide.

[Bardok (bardok)]

Hello,

i'm running now under 2.6.29-1 kernel, and i got this bug again.

Yesterday i left my pc without any programs and when i came back, it was on login screen. In kern.log i count 2 reboot.

See new kern.log after 17h15.

[JustMe (baselzinga)]

I have the same problem, the syslog shows a similar entry for the console-kit-daemon that it can't open the file /proc/2355/environ

[JustMe (baselzinga)]

It happens on the live cd, and during the install process.
It happens when running in console mode.
I have been running ubuntu for half a year on the laptop with 32 bit ubuntu and now problems... now I changed to the amd64 version and these random reboot occur. I also did a mem check because am64 will adress the full 4 gig where 32 bit would only use 3 gig. The memory test didn't report any problems.
I thought it might have something do with ext4 but I installed it with reiserfs and still the same problem.

[Bardok (bardok)]

Maybe it's not ext4.
In fact, in the log messages i see this "ACPI: I/O resource w83627ehf [0x295-0x296] conflicts with ACPI region SEN1 [0x295-0x296]", so i decide to find what's wrong.
I found that this is a sensor. I unload this module from system and put him in the blacklist module.

I notice that i have less reboot, less than 2 per day, before this was about more than 5.

I try this about 1 week.

I've got an other error "ACPI: I/O resource vt596_smbus [0x5000-0x5007] conflicts with ACPI region SM06 [0x5006-0x5006]" but i didn't find anything on internet.

Have you ACPI error to?

[JustMe (baselzinga)]

Well I installed 32 bit, since the bug causes a reboot my logs will be gone
when it happens, so.... I can't help with 64 bit anymore. But I will check
my logs on 32 bit. See if the same happens there...
32 bit is rock solid... no problems... only wifi drops sometimes but is
seems that issue is already taken care of in the next kernel release.

2009/4/26 Bardok <email address hidden>

> Maybe it's not ext4.
> In fact, in the log messages i see this "ACPI: I/O resource w83627ehf
> [0x295-0x296] conflicts with ACPI region SEN1 [0x295-0x296]", so i decide to
> find what's wrong.
> I found that this is a sensor. I unload this module from system and put him
> in the blacklist module.
>
> I notice that i have less reboot, less than 2 per day, before this was
> about more than 5.
>
> I try this about 1 week.
>
> I've got an other error "ACPI: I/O resource vt596_smbus [0x5000-0x5007]
> conflicts with ACPI region SM06 [0x5006-0x5006]" but i didn't find
> anything on internet.
>
> Have you ACPI error to?
>
> --
> Random reboot without error on jaunty amd64 2.6.28 and 2.6.29
> https://bugs.launchpad.net/bugs/359173
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Ubuntu: New
>
> Bug description:
> Hello,
>
> i'm under jaunty up to date and i have a bug : my pc reboot without any
> error in log and anytime.
>
> See attachments of logs.
>
> Thks for your help.
>
> Bonjour,
>
> je suis sous jaunty à jour et j'ai un problème : mon pc redémarre sans
> aucune erreur dans les logs et n'importe quand.
>
> ci joint les différentes logs.
>
> Merci pour votre aide.
>

[@ng3l (ma-lizarazo)]

I can confirm this. The same thing happens to me on kernel 2-6-28-13 con 32 bit.

[Norm Dugas (normdugas)]

I'm seeing this on 2 different machines. My 32 bit Mythbuntu backend running kernel 2.6.28-13 and my Kubuntu 64-bit desktop running kernel 2.6.28-13. I haven't seen this on my myth frontend machines but they're only on for a few hours at a time.

[Gabe Gorelick (gabegorelick)]

Is this still an issue on Karmic or Lucid Beta?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.