[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[Bug 212852] Kernel panics/lockups with acpi-cpufreq on a VIA C7 (EN1200 mini-itx board)



Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Kernel panics/lockups with acpi-cpufreq on a VIA C7 (EN1200 mini-itx board)


https://bugzilla.redhat.com/show_bug.cgi?id=212852


redhat subs maneos org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Status Whiteboard| bzcl34nup                  |bzcl34nup
               Flag|                            |needinfo?




------- Additional Comments From redhat subs maneos org  2008-04-17 11:08 EST -------
Apologies for the delay, it took me a while to track down a USB floppy drive for
flashing a newer BIOS.

With BIOS 1.09 (from
<http://www.via.com.tw/en/products/mainboards/downloads.jsp?motherboard_id=399>,
previously running 1.07) and kernel-PAE-2.6.24.4-64.fc8 the box lasted a bit
over a day with cpuspeed enabled.  The symptoms were different though, instead
of a kernel panic I "just" got I/O errors taking the (SATA) disk offline.

Kernel messages on the console were the following:

> kernel: journal commit I/O error
> ext3_abort called
> EXT3-ds error (device sda6): ext3_journal_start_sb: Detected aborted journal
> Remounting filesystem read-only

(repeated once for each mounted filesystem), and dmesg output contained just:

> sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
> end_request: I/O error, dev sda, sector 3720455

repeated ad nauseum.

Not sure whether the change is because of the kernel, the BIOS or both, or even
if it's the same issue (although with cpuspeed off it's been stable for ~10 days
now so it's at least related).

With nohz acpi=off on the kernel command line I did get a panic, but this time
the stack trace ended in

> [<c04052ae>] work_notifysig+0x13/0x19

and the kernel messages ended with

> Fixing recursive fault but reboot is needed!

after the trace.

Dave, ISTR that you have some EN1500 boards (which seem identical to the EN1200
in question modulo the CPU clock and cooling), have you managed to get those
stable with frequency scaling on?


-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]