On Dec 30, 2013, at 8:26 PM, Sean Darcy wrote:
> Kernel driver in use: tg3
>
>
> Not sure what to do with this.
Reboot, at grub menu highlight the f20 kernel option, hit e to edit, find the
linux command line, remove quiet rhgb, add rd.blacklist=tg3 and then F10 to
boot.
Chris Murphy
On 12/30/2013 06:39 PM, Chris Murphy wrote:
On Dec 30, 2013, at 3:41 PM, Sean Darcy wrote:
Sadly, it's a real kernel panic. Everything stops. I can't even reboot. It's a
good thing there's a power cord!
I'll copy what's on the screen, and submit it as a bug report. Maybe someone
smarter th
On Dec 30, 2013, at 3:41 PM, Sean Darcy wrote:
>
> Sadly, it's a real kernel panic. Everything stops. I can't even reboot. It's
> a good thing there's a power cord!
>
> I'll copy what's on the screen, and submit it as a bug report. Maybe someone
> smarter than I am can figure out what actuall
On 12/30/2013 11:38 AM, Chris Murphy wrote:
On Dec 29, 2013, at 5:11 PM, Sean Darcy wrote:
Updated to F19, kernel-3.12.5-200.fc19.x86_64.
On boot I get a kernel panic around [2.2]. The trace that's on the screen is
about smp, timers, hpet. Can't read quickly enough to see what actually
hap
On Dec 29, 2013, at 5:11 PM, Sean Darcy wrote:
> Updated to F19, kernel-3.12.5-200.fc19.x86_64.
>
> On boot I get a kernel panic around [2.2]. The trace that's on the screen is
> about smp, timers, hpet. Can't read quickly enough to see what actually
> happened.
The kernel panic halts the st
Updated to F19, kernel-3.12.5-200.fc19.x86_64.
On boot I get a kernel panic around [2.2]. The trace that's on the
screen is about smp, timers, hpet. Can't read quickly enough to see what
actually happened.
/var/log/messages has no log of the kernel boot. Shouldn't there be one?
rsyslogd.conf
