Your message dated Mon, 31 Jul 2006 18:48:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old kernel bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: kernel-image-2.2.19-pmac
Version: 2.2.19-2
Severity: normal
Greetings,
2.2.19 has generally been crash-free for me, but the two crashes I've
seen have happened during the last two upgrades of autofs. In the most
recent one, I copied what I could from the screen before reboot, which
went something like:
Unable to handle (forgot) address 00000004 (error 20000000)
NIP: C0055568 XER: 00000000 LR: C0056078 regs c11abc90 TRAP: 0300
(lots of other stuff)
Call backtrace:
00000001 C0056078 C005618C C002F994 C0003EC4 6FFD91A8 6FFD9998 1000A2FC
1000A9FC 6FEAE3F8 00000000
Kernel panic: kernel access of bad area pc C0055568 lr C0056078 address
00000004 tsk ps/8022
What's funny is that both times, when I rebooted, automount started
just fine; and when I did "dpkg --configure --all", automount set up
just fine, complete with start and stop. So I don't know why this
only happens during the first apt-get dselect-upgrade.
Thanks,
--
Adam P.
GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6
Welcome to the best software in the world today cafe!
<http://lyre.mit.edu/~powell/The_Best_Stuff_In_The_World_Today_Cafe.ogg>
--- End Message ---
--- Begin Message ---
no current report about ppc autofs troubles,
therefor closing this bugreport.
feel free to reopen if pain subsists.
--
maks
--- End Message ---
