[EDGY] Battery not detected on Edgy using linux-image-2.6.17-10 with Acer Ferrar 4005 Laptop

lakin@zedd:~$ cat /proc/acpi/battery/BAT1/
alarm info state
lakin@zedd:~$ cat /proc/acpi/battery/BAT1/
alarm info state
lakin@zedd:~$ cat /proc/acpi/battery/BAT1/alarm
present: no
lakin@zedd:~$ cat /proc/acpi/battery/BAT1/state
present: no
lakin@zedd:~$ cat /proc/acpi/battery/BAT1/info
present: no

sorry for the duplicate posting of the proc information.

It should be noted that this was a Edge RC install earlier today and then updated to the latest packages as of a few hours ago.

I subsequently noticed that the dmesg output that I uploaded was useless. Sorry.

This one should be much more useful, in this one I noticed:
[ 26.498746] ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[c0309000-c03097ff] Max Packet=[2048] IR/IT contexts=[4/8]
[ 27.777828] ieee1394: Host added: ID:BUS[0-00:1023] GUID[00c09f000090feb2]
[ 28.326972] Attempting manual resume
[ 28.455117] irq 11: nobody cared (try booting with the "irqpoll" option)
[ 28.455122]
[ 28.455122] Call Trace: <IRQ> <ffffffff802b68a5>{__report_bad_irq+53}
[ 28.455136] <ffffffff802b6b20>{note_interrupt+544} <ffffffff802b6190>{__do_IRQ+224}
[ 28.455146] <ffffffff802737e2>{do_IRQ+66} <ffffffff80265d08>{ret_from_intr+0} <EOI>
[ 28.455157] <ffffffff8020c9f0>{file_read_actor+0} <ffffffff8020b23e>{touch_atime+142}
[ 28.455165] <ffffffff8020b217>{touch_atime+103} <ffffffff8020bc50>{do_generic_mapping_read+1120}
[ 28.455172] <ffffffff8020c9f0>{file_read_actor+0} <ffffffff8020be6c>{__generic_file_aio_read+364}
[ 28.455184] <ffffffff802b91dc>{generic_file_read+172} <ffffffff80268fe9>{copy_to_user+9}
[ 28.455192] <ffffffff802a3b00>{autoremove_wake_function+0} <ffffffff8020db18>{do_mmap_pgoff+1560}
[ 28.455201] <ffffffff8020aeeb>{vfs_read+219} <ffffffff8026b578>{_spin_unlock_irqrestore+8}
[ 28.455208] <ffffffff802110b3>{sys_read+83} <ffffffff8026580e>{system_call+126}
[ 28.455218] handlers:
[ 28.455220] [<ffffffff8806fb90>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 28.455252] [<ffffffff8806fb90>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 28.455268] [<ffffffff8806fb90>] (usb_hcd_irq+0x0/0x60 [usbcore])
[ 28.455283] [<ffffffff8810f0c0>] (ohci_irq_handler+0x0/0x7ff [ohci1394])
[ 28.455291] Disabling IRQ #11

And at the time I was trying to get my wireless card working which was also reporting that it was on irq 11 ... I tried rebooting with irqpoll, and voila -> Battery is working and wireless is working.

same here. this was working with an edgy daily up until a couple of weeks before release, i think. i dunno, but maybe it has something to do with all those APIC errors.

I managed to prevent these APIC errors flooding my dmesg by removing the ohci1394 module.

However I only get battery when I include irqpoll on the kernel command line.

This is regardless of if I use a fixed DSDT.

This is a definite regression from Dapper for my laptop (Ferrari 4005).
With Dapper neither irqpoll or DSDT were not required for battery state (however I think I was required to run the k8 kernel).

Removing and re-inserting the battery module does not help.

"acpi -V" returns:
     Thermal 1: ok, 37.0 degrees C
  AC Adapter 1: on-line

"lshal | grep battery" returns:
  battery.present = false (bool)
  info.capabilities = {'battery'} (string list)
  info.category = 'battery' (string)
  battery.type = 'primary' (string)
  linux.acpi_path = '/proc/acpi/battery/BAT1' (string)

"cat /proc/acpi/battery/*/state" returns:
present: no

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.