This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
Have installed 8.10 server.
Removed the 13GB Quantum ATA33 drive (Primary Master) and replaced with
a ATA133 drive so both primary and secondary IDE channels now run at
ATA100, rather than one at ATA33 and the other at ATA100,
Have also changed the filesystem on the raid1 from xfs to ext3.
Reail
Leann thank you for your comment 2 this machine is supposed to be a
production machine (hence the reason it is running LTS) so taking
offline to rebuild is problematic (admittedly kernel multiple kernel
panics dont do much for uptime), is there a specific feature in the
2.6.27 kernel which you thin
Left the machine on over night, with no nfs clients attached came back
to it in the morning and have a very similar crash, see attached photo.
Process swapper (pid: 0, ti=c0436000 task=c04033a0 task.ti=c0436000)
Stack: 5583 13ab50c0 c1809120 c049b300 c0149b03
Would it be possible for you to test the newer Intrepid ibex 8.10
release which has a 2.6.27 based kernel?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Kernel panic - not syncing: Fatal exception in interrupt
https://bugs.launchpad.net/bugs/310809
You received this bug notif
** Description changed:
8.04 LTS hardy server AMD Athlon(tm) XP 2000+ on a Gigabyte 7VAX
Motherboard, running md (raid1) of /home exported via nfs and samba,
iptables, cups printer etc. Crash is only noticed on an nfs client
machine when everything freezes.
nothing in dmesg or kern.
** Attachment added: "photo of panic text"
http://launchpadlibrarian.net/20680350/DSCF5217.JPG
** Description changed:
8.04 LTS hardy server AMD Athlon(tm) XP 2000+ on a Gigabyte 7VAX
- Motherboard, running md (raid0) of /home exported via nfs and samba,
+ Motherboard, running md (raid1) o
