Well I have supplied the apport file and all the information I found
pertinent. I realise that whoever is dealing with this cant jump at any
1 report, I get it ppl have all sorts of things in live to do.
My comment regarding the no one cares part, really came from the OLDER
bug I linked to on my post where it was reported fixed and indeed its
not if you check down that original bug report to a way older Ubuntu
Distro.
I understand also that have two instances probing the same bus can break
things & potentially damage hardware and that from 2.6.29 has sorta
changed in regards to that so this does not happen. However it does not
explain why a older kernel fixes it like the 2.6.32rc7. Nor does it
explain why froa very long time this was reported on the other report
and no official reply was given.
I apologise if it sounded ungrateful at sme stage, I hope this gets
looked at and the necessary patches applied so that everything works as
expected.
This has forced me to stop doinbg Karmic based custom minimal installs
for the issues posted even before adding any sensors monitoring sw it
already presents conflicts with SMbus access. I can only blame it on
testers not reporting it properly though in this instace its a silent on
boot comment which is apparently not logged.
Heres hoping I can get Karmic posted on my plentifull requests for
custom systems atm Im no longer running Karmic besides on VM.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
linux-image
https://bugs.launchpad.net/bugs/485234
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
