I've just had a kernel panic on my fairly new 3.06GHz Core2Duo iMac
running MacOS X 10.6.2.
AFAIK, I have added precisely no software which could possible provoke a
kernel panic.
Is there any way of looking into whatever might have caused the problem?
I fired up Console.app and peered at the listing on the left, but
nothing there seemed to relate to a kernel panic. I expect I'm wrong.
I had a couple of external HDDs mounted at the time - Seagate Barracudas
in FW800 enclosures. And a couple of disc images mounted, both of which
lived on one of the external HDDs in question.
Rowland.
--
Remove the animal for email address: rowland....@dog.physics.org
Sorry - the spam got to me
http://www.mag-uk.org http://www.bmf.co.uk
UK biker? Join MAG and the BMF and stop the Eurocrats banning biking
Open up Console.app again and locate the 'panic.log' entry (Note: I'm going
from memory here and it's been a while)
Post it here. Sometimes there's something vaguely human-readable in these
things.
This link may also help (but frankly probably won't):
<http://developer.apple.com/mac/library/technotes/tn2002/tn2063.html#TNTAG31>
Jim
--
http://www.ursaMinorBeta.co.uk http://twitter.com/GreyAreaUK
My Oasis of Calm has dried up. However, my Garden of Angry is
flourishing quite nicely.
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> > That's it, really.
> >
> > I've just had a kernel panic on my fairly new 3.06GHz Core2Duo iMac
> > running MacOS X 10.6.2.
> >
> > AFAIK, I have added precisely no software which could possible provoke a
> > kernel panic.
> >
> > Is there any way of looking into whatever might have caused the problem?
> > I fired up Console.app and peered at the listing on the left, but
> > nothing there seemed to relate to a kernel panic. I expect I'm wrong.
> >
> > I had a couple of external HDDs mounted at the time - Seagate Barracudas
> > in FW800 enclosures. And a couple of disc images mounted, both of which
> > lived on one of the external HDDs in question.
>
> Open up Console.app again and locate the 'panic.log' entry (Note: I'm going
> from memory here and it's been a while)
There ain't no such animal for viewing in Console.app that I can see.
I've just asked EasyFind to search for the file panic.log and it's found
nothing either - looking for invisible and visible files.
> Post it here. Sometimes there's something vaguely human-readable in these
> things.
I was hoping for something like that.
> This link may also help (but frankly probably won't):
>
> <http://developer.apple.com/mac/library/technotes/tn2002/tn2063.html#TNTAG31>
It'd help someone who knows how to use that kind of information. Since
I haven't a clue...
Cheers,
Blast. Sorry. My memory of this predates 10.6, so may not be strictly
accurate.
>> Post it here. Sometimes there's something vaguely human-readable in these
>> things.
>
> I was hoping for something like that.
>
>> This link may also help (but frankly probably won't):
>>
>> <http://developer.apple.com/mac/library/technotes/tn2002/tn2063.html#TNTAG31>
>
> It'd help someone who knows how to use that kind of information. Since
> I haven't a clue...
Sadly, same here.
> On 2009-11-24, Rowland McDonnell
> <real-addr...@flur.bltigibbet.invalid> wrote:
>>>
>>> Open up Console.app again and locate the 'panic.log' entry (Note: I'm
>>> going
>>> from memory here and it's been a while)
>>
>> There ain't no such animal for viewing in Console.app that I can see.
>> I've just asked EasyFind to search for the file panic.log and it's found
>> nothing either - looking for invisible and visible files.
>
> Blast. Sorry. My memory of this predates 10.6, so may not be strictly
> accurate.
>
Console.app -> Files section -> PanicReporter section
They're listed by date and time.
Cheers,
--
James Dore
New College IT Officer
james.dore@new / it-support@new
> Jim <j...@magrathea.plus.com> wrote:
>
> > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> > > That's it, really.
> > >
> > > I've just had a kernel panic on my fairly new 3.06GHz Core2Duo iMac
> > > running MacOS X 10.6.2.
> > >
> > > AFAIK, I have added precisely no software which could possible provoke a
> > > kernel panic.
> > >
> > > Is there any way of looking into whatever might have caused the problem?
> > > I fired up Console.app and peered at the listing on the left, but
> > > nothing there seemed to relate to a kernel panic. I expect I'm wrong.
> > >
> > > I had a couple of external HDDs mounted at the time - Seagate Barracudas
> > > in FW800 enclosures. And a couple of disc images mounted, both of which
> > > lived on one of the external HDDs in question.
> >
> > Open up Console.app again and locate the 'panic.log' entry (Note: I'm going
> > from memory here and it's been a while)
>
> There ain't no such animal for viewing in Console.app that I can see.
> I've just asked EasyFind to search for the file panic.log and it's found
> nothing either - looking for invisible and visible files.
It looks like it's changed in 10.6, I had to look mine up a week or so
ago (luckily I found an entry for tap & tun, which I've now removed).
It's now in the Console under /library/logs/DiagnosticReports, and is
named 'kernel...blah...blah.panic'
--
Andy Hewitt
<http://web.me.com/andrewhewitt1/>
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
[..]
> > > Open up Console.app again and locate the 'panic.log' entry (Note: I'm
> > > going from memory here and it's been a while)
> >
> > There ain't no such animal for viewing in Console.app that I can see.
> > I've just asked EasyFind to search for the file panic.log and it's found
> > nothing either - looking for invisible and visible files.
>
> It looks like it's changed in 10.6, I had to look mine up a week or so
> ago (luckily I found an entry for tap & tun, which I've now removed).
>
> It's now in the Console under /library/logs/DiagnosticReports, and is
> named 'kernel...blah...blah.panic'
It's also duplicated in 'DIAGNOSTIC INFORMATION/System Diagnostic
Reports'.
(I wasn't shouting, that's how it's shown in Console).
I had a few panics under 10.6 and 10.6.1. None of them are listed there.
My recollection is that most of them were sent off to Apple after the
restart (with an opportunity to enter comments), but the last one didn't
offer to do that.
I wonder if the system deletes the panic details after sending them. If
it moves them somewhere else, I can't find them.
--
David Empson
dem...@actrix.gen.nz
DIAGNOSTIC INFORMATION/System Diagnostic Reports' does not exist here.
No such animal here.
/Library/Logs, yes. No /Library/Logs/DiagnosticReports
> Andy Hewitt <thewil...@me.com> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
> >
> > > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> > [..]
> > > > > Open up Console.app again and locate the 'panic.log' entry (Note: I'm
> > > > > going from memory here and it's been a while)
> > > >
> > > > There ain't no such animal for viewing in Console.app that I can see.
> > > > I've just asked EasyFind to search for the file panic.log and it's found
> > > > nothing either - looking for invisible and visible files.
> > >
> > > It looks like it's changed in 10.6, I had to look mine up a week or so
> > > ago (luckily I found an entry for tap & tun, which I've now removed).
> > >
> > > It's now in the Console under /library/logs/DiagnosticReports, and is
> > > named 'kernel...blah...blah.panic'
> >
> > It's also duplicated in 'DIAGNOSTIC INFORMATION/System Diagnostic
> > Reports'.
> >
> > (I wasn't shouting, that's how it's shown in Console).
>
> I had a few panics under 10.6 and 10.6.1. None of them are listed there.
Multiple kernel panics? Really? Isn't that a bit, erm, poor? Or do
you know of some dodgy driver(s) responsible?
> My recollection is that most of them were sent off to Apple after the
> restart (with an opportunity to enter comments), but the last one didn't
> offer to do that.
No such offer here.
> I wonder if the system deletes the panic details after sending them. If
> it moves them somewhere else, I can't find them.
The OS appears to have made no record at all about the kernel panics
I've seen.
> Jim <j...@magrathea.plus.com> wrote:
>
> > Rowland McDonnell wrote:
> >>>
> >>> Open up Console.app again and locate the 'panic.log' entry (Note: I'm
> >>> going
> >>> from memory here and it's been a while)
> >>
> >> There ain't no such animal for viewing in Console.app that I can see.
> >> I've just asked EasyFind to search for the file panic.log and it's found
> >> nothing either - looking for invisible and visible files.
> >
> > Blast. Sorry. My memory of this predates 10.6, so may not be strictly
> > accurate.
> >
>
> Console.app -> Files section -> PanicReporter section
No such animal here.
> They're listed by date and time.
Not here they ain't. I can see lots and lots and *LOTS* of odd stuff in
the Console.app sidebar, but no mention of panic at all.
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> >>
> >> Open up Console.app again and locate the 'panic.log' entry (Note: I'm going
> >> from memory here and it's been a while)
> >
> > There ain't no such animal for viewing in Console.app that I can see.
> > I've just asked EasyFind to search for the file panic.log and it's found
> > nothing either - looking for invisible and visible files.
>
> Blast. Sorry. My memory of this predates 10.6, so may not be strictly
> accurate.
<shrug> I don't see any reason to be surprised that a kernel panic left
no log even if it was supposed to.
[snip]
> David Empson <dem...@actrix.gen.nz> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
[..]
> > I wonder if the system deletes the panic details after sending them. If
> > it moves them somewhere else, I can't find them.
>
> The OS appears to have made no record at all about the kernel panics
> I've seen.
It's possible that the OS crashed at a point where a panic report
couldn't be gathered and saved. I have had an odd one of those on
occasion - I have had one or two kernel panics, but easily attributable
to devices such as USB hubs.
> Andy Hewitt <thewil...@me.com> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
> >
> > > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> > [..]
> > > > > Open up Console.app again and locate the 'panic.log' entry (Note: I'm
> > > > > going from memory here and it's been a while)
> > > >
> > > > There ain't no such animal for viewing in Console.app that I can see.
> > > > I've just asked EasyFind to search for the file panic.log and it's found
> > > > nothing either - looking for invisible and visible files.
> > >
> > > It looks like it's changed in 10.6, I had to look mine up a week or so
> > > ago (luckily I found an entry for tap & tun, which I've now removed).
> > >
> > > It's now in the Console under /library/logs/DiagnosticReports, and is
> > > named 'kernel...blah...blah.panic'
> >
> > It's also duplicated in 'DIAGNOSTIC INFORMATION/System Diagnostic
> > Reports'.
> >
> > (I wasn't shouting, that's how it's shown in Console).
>
> DIAGNOSTIC INFORMATION/System Diagnostic Reports' does not exist here.
Hmm, OS 10.6.2 here, and I have three reports in mine. Of course it may
not appear until you do have such reports.
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
> >
> > > Andy Hewitt <thewil...@me.com> wrote:
> > >
> > > > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> > > [..]
> > > > > > Open up Console.app again and locate the 'panic.log' entry
> > > > > > (Note: I'm going from memory here and it's been a while)
> > > > >
> > > > > There ain't no such animal for viewing in Console.app that I can
> > > > > see. I've just asked EasyFind to search for the file panic.log and
> > > > > it's found nothing either - looking for invisible and visible
> > > > > files.
> > > >
> > > > It looks like it's changed in 10.6, I had to look mine up a week or so
> > > > ago (luckily I found an entry for tap & tun, which I've now removed).
> > > >
> > > > It's now in the Console under /library/logs/DiagnosticReports, and is
> > > > named 'kernel...blah...blah.panic'
> > >
> > > It's also duplicated in 'DIAGNOSTIC INFORMATION/System Diagnostic
> > > Reports'.
> > >
> > > (I wasn't shouting, that's how it's shown in Console).
> >
> > DIAGNOSTIC INFORMATION/System Diagnostic Reports' does not exist here.
>
> Hmm, OS 10.6.2 here, and I have three reports in mine. Of course it may
> not appear until you do have such reports.
Is here but no attual reports as this mac hasn't had a kernal panic.
roger
--
www.rogermerriman.com
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
>
> > David Empson <dem...@actrix.gen.nz> wrote:
> >
> > > Andy Hewitt <thewil...@me.com> wrote:
> [..]
> > > I wonder if the system deletes the panic details after sending them. If
> > > it moves them somewhere else, I can't find them.
> >
> > The OS appears to have made no record at all about the kernel panics
> > I've seen.
>
> It's possible that the OS crashed at a point where a panic report
> couldn't be gathered and saved.
I assumed so.
> I have had an odd one of those on
> occasion - I have had one or two kernel panics, but easily attributable
> to devices such as USB hubs.
Yeah, well, if an external FW HDD can cause a kernel panic (the only
possible trigger in the frame here), I blame the OS's kernel for
defective disc or Firewire drivers.
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
[snip]
> > DIAGNOSTIC INFORMATION/System Diagnostic Reports' does not exist here.
>
> Hmm, OS 10.6.2 here, and I have three reports in mine. Of course it may
> not appear until you do have such reports.
It's appeared - as a greyed-out `nothing exists here' ghost entry.
> Andy Hewitt <thewil...@me.com> wrote:
>
> > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
[..]
> > It's possible that the OS crashed at a point where a panic report
> > couldn't be gathered and saved.
>
> I assumed so.
>
> > I have had an odd one of those on
> > occasion - I have had one or two kernel panics, but easily attributable
> > to devices such as USB hubs.
>
> Yeah, well, if an external FW HDD can cause a kernel panic (the only
> possible trigger in the frame here), I blame the OS's kernel for
> defective disc or Firewire drivers.
That's a distinct possibility. My MacBook won't always boot up if I have
my FW chain connected. It all runs fine after it's booted though. I had
been assuming something tricky with one of my FW bridges though.
> Andy Hewitt <thewil...@me.com> wrote:
>
> > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> >
> > > Andy Hewitt <thewil...@me.com> wrote:
> [snip]
>
> > > DIAGNOSTIC INFORMATION/System Diagnostic Reports' does not exist here.
> >
> > Hmm, OS 10.6.2 here, and I have three reports in mine. Of course it may
> > not appear until you do have such reports.
>
> It's appeared - as a greyed-out `nothing exists here' ghost entry.
Then it exists, and that puzzle is sorted. There's obviously just no
reports there, so you're not going to find anything that'll help you.
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
> >
> > > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> [..]
> > > It's possible that the OS crashed at a point where a panic report
> > > couldn't be gathered and saved.
> >
> > I assumed so.
> >
> > > I have had an odd one of those on
> > > occasion - I have had one or two kernel panics, but easily attributable
> > > to devices such as USB hubs.
> >
> > Yeah, well, if an external FW HDD can cause a kernel panic (the only
> > possible trigger in the frame here), I blame the OS's kernel for
> > defective disc or Firewire drivers.
>
> That's a distinct possibility. My MacBook won't always boot up if I have
> my FW chain connected. It all runs fine after it's booted though. I had
> been assuming something tricky with one of my FW bridges though.
I've read that Apple's FW implementations haven't always been as good as
they might be. It's safe to assume that other vendors fuck up their FW
implementations too. So if you've got a dodgy FW interface at *both*
ends of the wire, Things Will Certainly Go Wrong At Times[1].
But whatever goes wrong, it shouldn't give a kernel panic.
Rowland.
[1] E.g., if I plug both of *those* external HDDs in via FW, the OS
complains and neither disc can be mounted until the Mac is rebooted.
One at a time, fine - add the second, unexpected umounting, and it's all
foobar until a reboot.
Not a major problem - both external boxes have USB 2 and FW and the
discs aren't so big. But if I'd found out about this problem sooner
rather than later, I'd've sent the boxes back as defective.
> Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
>
> > Andy Hewitt <thewil...@me.com> wrote:
> >
> > > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
> > >
> > > > Andy Hewitt <thewil...@me.com> wrote:
> > [snip]
> >
> > > > DIAGNOSTIC INFORMATION/System Diagnostic Reports' does not exist here.
> > >
> > > Hmm, OS 10.6.2 here, and I have three reports in mine. Of course it may
> > > not appear until you do have such reports.
> >
> > It's appeared - as a greyed-out `nothing exists here' ghost entry.
>
> Then it exists, and that puzzle is sorted.
Exists? I thought that was a sign of it not existing, but being in a
state of `I'll turn up when you need me'.
> There's obviously just no
> reports there, so you're not going to find anything that'll help you.
That last clause is certainly correct. I've looked, lots...
> Andy Hewitt <thewil...@me.com> wrote:
>
> > Rowland McDonnell <real-addr...@flur.bltigibbet.invalid> wrote:
[..]
> > > Yeah, well, if an external FW HDD can cause a kernel panic (the only
> > > possible trigger in the frame here), I blame the OS's kernel for
> > > defective disc or Firewire drivers.
> >
> > That's a distinct possibility. My MacBook won't always boot up if I have
> > my FW chain connected. It all runs fine after it's booted though. I had
> > been assuming something tricky with one of my FW bridges though.
>
> I've read that Apple's FW implementations haven't always been as good as
> they might be. It's safe to assume that other vendors fuck up their FW
> implementations too. So if you've got a dodgy FW interface at *both*
> ends of the wire, Things Will Certainly Go Wrong At Times[1].
Indeed, although I've only ever suffered FW problems with iffy
externals, in this case it's only started since I installed a new
FW400-SATA bridge. The older FW800-SATA (from the same supplier) worked
fine.
> But whatever goes wrong, it shouldn't give a kernel panic.
It *shouldn't*, no.
[..]
> > > It's appeared - as a greyed-out `nothing exists here' ghost entry.
> >
> > Then it exists, and that puzzle is sorted.
>
> Exists? I thought that was a sign of it not existing, but being in a
> state of `I'll turn up when you need me'.
Without wishing to get pedantic about it, you did say 'does not exist
here', which would imply that nothing was there at all. If you'd said,
'it's there but is greyed out', that might have saved some confusion.
Yeah, well, that's down to me looking at things in a sightly sideways
fashion. Explaining the point of view in question would be tricky, but
it did make perfect sense when I wrote it.