Bug#860781: High system load, probably due to interrupts

2017-04-20 Thread Stefan Ott
The message about rtc interrupts seems to be related to the
irqpoll kernel option - without irqpoll I no longer get that
one.

The other issues are still there.

-- 
Stefan Ott
http://www.ott.net/



Bug#860781: linux-image-4.9.0-2-amd64: High system load, probably due to interrupts

2017-04-19 Thread Stefan Ott
Package: src:linux
Version: 4.9.18-1
Severity: normal

Dear Maintainer,

I installed Debian on an older Laptop and noticed that my system load
was very high even though the system was just sitting there being
idle, not even running X:


# uptime
 03:23:45 up 21 min,  2 users,  load average: 7.53, 3.25, 2.10


According to top, the only processes that cause any load are kworkers.
After reading several similar reports from other people I proceeded to
investigate my ACPI interrupts and noticed this:


# cat /sys/firmware/acpi/interrupts/gpe17
  509091  EN enabled  unmasked
# cat /sys/firmware/acpi/interrupts/gpe17
  515942  EN enabled  unmasked


I.e. lots of interrupts happening on gpe17 (these commands were run
within 1 second of eachother). I then disabled gpe17:


echo "disable" >/sys/firmware/acpi/interrupts/gpe17


This brought the load down to about 2.0 (still rather high) when idle.
However, as soon as I start Xorg the load goes up again (currently at
17.1, after about 3 minutes) and this time I don't see anything
interesting in the ACPI interrupts.

The high load does not appear to affect the system's performance much.
I have however noticed that the fans are unusually active and, more
importantly, the acpi command seems to have trouble communicating:


# time acpi -Vi >/dev/null 
real1m22.340s


# time acpi -Vi >/dev/null
real0m13.737s


On a possibly related note, I am getting a lot of these messages:
[ 2325.736093] hpet1: lost 9600 rtc interrupts


The dmesg log attached also shows an issue with the GPU; I don't
think that's related to this problem but at the moment I can't say
for sure.

Are there any other workarounds that I could try?


-- Package-specific info:
** Version:
Linux version 4.9.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170321 (Debian 6.3.0-11) ) #1 SMP Debian 4.9.18-1 (2017-03-30)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-amd64 root=/dev/mapper/vg_vetinari-root ro 
quiet irqpoll

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
sys_vendor: Apple Inc.
product_name: MacBookAir1,1
product_version: 1.0
chassis_vendor: Apple Inc.
chassis_version: Mac-F42C8CC8
bios_vendor: Apple Inc.
bios_version:MBA11.88Z.00BB.B03.0803171226
board_vendor: Apple Inc.
board_name: Mac-F42C8CC8
board_version: PVT

** Loaded modules:
nls_ascii
nls_cp437
vfat
fat
joydev
arc4
iTCO_wdt
iTCO_vendor_support
coretemp
kvm_intel
b43
kvm
applesmc
bcma
input_polldev
mac80211
efi_pstore
i915
irqbypass
btusb
btrtl
btbcm
btintel
uvcvideo
bluetooth
videobuf2_vmalloc
cfg80211
videobuf2_memops
pcspkr
videobuf2_v4l2
sg
videobuf2_core
efivars
asix
snd_hda_codec_realtek
videodev
crc16
drm_kms_helper
usbnet
libphy
rfkill
mii
rng_core
media
bcm5974
snd_hda_codec_generic
drm
evdev
acpi_als
kfifo_buf
snd_hda_intel
industrialio
lpc_ich
snd_hda_codec
i2c_algo_bit
mfd_core
snd_hda_core
video
snd_hwdep
sbs
snd_pcm
apple_bl
sbshc
snd_timer
battery
shpchp
ac
button
snd
soundcore
acpi_cpufreq
tpm_tis
tpm_tis_core
tpm
xfs
libcrc32c
crc32c_generic
xts
gf128mul
algif_skcipher
af_alg
hid_apple
hid_appleir
usbhid
hid
dm_crypt
dm_mod
sd_mod
ata_generic
ahci
libahci
ata_piix
libata
i2c_i801
i2c_smbus
scsi_mod
ssb
mmc_core
pcmcia
ehci_pci
pcmcia_core
uhci_hcd
ehci_hcd
usbcore
usb_common
thermal

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory 
Controller Hub [8086:2a00] (rev 03)
Subsystem: Apple Inc. Mobile PM965/GM965/GL960 Memory Controller Hub 
[106b:00a2]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(primary) [106b:00a2]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 
Integrated Graphics Controller (secondary) [8086:2a03] (rev 03)
Subsystem: Apple Inc. Mobile GM965/GL960 Integrated Graphics Controller 
(secondary) [106b:00a2]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1a.0 USB controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI 
Controller #4 [8086:2834] (rev 03) (prog-if 00 [UHCI])
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  

Bug#689096: [wheezy] ipw2200 crashes on wakeup

2012-10-15 Thread Stefan Ott
Hey

I've been rather busy lately so I didn't have time to try this.
However, I've had the same thing happen twice with kernel 3.5 since. I
hope I find some time to build a 3.6 series kernel and see whether
that fixes things.

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOk=tptl6ab0uyhrsbgbvkaxpovayhsjpkqdto5i_m8nvsy...@mail.gmail.com



Bug#689096: ipw2200 crashes on wakeup

2012-10-07 Thread Stefan Ott
Hey

On Sun, Sep 30, 2012 at 10:57 AM, Jonathan Nieder  wrote:
> Hi Stefan,
>
> Stefan Ott wrote:
>
>> Is there anything I can do to help debug this, other than building &
>> trying dozens of kernel versions to try and find the "bad" commit?
>
> I haven't looked closely into this report, but here are two quick
> ideas:
>
>  A. Have you tried the 3.5.y kernel from experimental?  If it works,
> we can try to find the patch that fixes the bug and apply the same
> to wheezy.  If it doesn't work, that information will make it much
> easier for us to get help from upstream.

I've been using the 3.5-trunk-686-pae kernel for about a week now and
so far there haven't been any further incidents - it might just be a
lucky coincidence but considering how often it happened with the
wheezy kernel I'm inclined to say that the upgrade fixed the issue.

Do you have a particular commit in mind that might be responsible? If
so I could try building a patched kernel.

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOk=tpsv6mgkxlpeeg_zl_smwpksbvmdnumprsjjoqyuwui...@mail.gmail.com



Bug#689096: linux-image-3.2.0-3-686-pae: ipw2200 crashes on wakeup

2012-09-29 Thread Stefan Ott
FYI I have since downgraded to 2.6.32-5-686 from squeeze and haven't
had any further such issues so far. Of course this doesn't prove
anything (it could happen the very next time I suspend the machine)
but to me it is a strong indication that there might be something
fishy with the driver in wheezy.

Is there anything I can do to help debug this, other than building &
trying dozens of kernel versions to try and find the "bad" commit?

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOk=tpt03owxhn071fkeqcdj4qws2fy0l4mpoxkhhqhw28y...@mail.gmail.com



Bug#689096: linux-image-3.2.0-3-686-pae: ipw2200 crashes on wakeup

2012-09-29 Thread Stefan Ott
On Sat, Sep 29, 2012 at 12:43 PM, Ben Hutchings  wrote:
> On Sat, 2012-09-29 at 03:56 +0200, Stefan Ott wrote:
>> Package: src:linux
>> Version: 3.2.23-1
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> Ever since I upgraded to wheezy I get occasional crashes in the ipw2200
>> driver when my laptop wakes up from suspend.
>
> This isn't a crash.

Hmm okay, whatever it is, I need to reload the kernel module
afterwards to get the driver working again.

>> It does't always happen and it used to work flawlessly with squeeze.
> [...]
>
> I suspect that on squeeze it would hang instead.

It never did.

> Are you using the wireless interface in managed or ad-hoc mode?

In managed mode.

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOk=tpt5r0b+pgfkfnwk+5jhv75z--yekvbtgbwpffthfkr...@mail.gmail.com



Bug#689096: linux-image-3.2.0-3-686-pae: ipw2200 crashes on wakeup

2012-09-28 Thread Stefan Ott
Package: src:linux
Version: 3.2.23-1
Severity: normal

Dear Maintainer,

Ever since I upgraded to wheezy I get occasional crashes in the ipw2200
driver when my laptop wakes up from suspend. It does't always happen and
it used to work flawlessly with squeeze.

Here's what dmesg has to say about this:

[59928.488934] wlan: Coming out of suspend...
[59928.488943] ipw2200 :04:02.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[59928.490888] [ cut here ]
[59928.490899] WARNING: at 
/build/buildd-linux_3.2.23-1-i386-qhsd1M/linux-3.2.23/drivers/base/firmware_class.c:537
 _request_firmware+0xad/0x2f9()
[59928.490922] Hardware name: 25256NG
[59928.490925] Modules linked in: ipw2200 msr tg3 libphy cryptd aes_i586 
aes_generic lib80211_crypt_ccmp cpufreq_userspace cpufreq_stats 
cpufreq_conservative cpufreq_powersave fuse ext3 jbd mbcache hidp hid rfcomm 
bluetooth crc16 dm_crypt dm_mod snd_intel8x0 snd_ac97_codec ac97_bus 
snd_pcm_oss snd_mixer_oss thinkpad_acpi snd_pcm snd_seq_midi snd_rawmidi 
snd_seq_midi_event snd_seq snd_timer pcmcia libipw snd_seq_device iTCO_wdt 
cfg80211 rfkill iTCO_vendor_support snd lib80211 nvram soundcore yenta_socket 
pcmcia_rsrc pcmcia_core psmouse rng_core snd_page_alloc serio_raw i2c_i801 
pcspkr battery acpi_cpufreq ac power_supply mperf evdev processor xfs sg sd_mod 
crc_t10dif ata_generic ata_piix ahci libahci libata i915 scsi_mod sdhci_pci 
sdhci mmc_core i2c_algo_bit drm_kms_helper drm uhci_hcd ehci_hcd usbcore 
thermal video i2c_core thermal_sys usb_common button [last unloaded: ipw2200]
[59928.491047] Pid: 19479, comm: kworker/0:0 Tainted: GW
3.2.0-3-686-pae #1
[59928.491050] Call Trace:
[59928.491059]  [] ? warn_slowpath_common+0x68/0x79
[59928.491063]  [] ? _request_firmware+0xad/0x2f9
[59928.491068]  [] ? warn_slowpath_null+0xd/0x10
[59928.491073]  [] ? _request_firmware+0xad/0x2f9
[59928.491077]  [] ? request_firmware+0x9/0xc
[59928.491088]  [] ? ipw_up+0xdd/0x1165 [ipw2200]
[59928.491094]  [] ? finish_task_switch+0x6d/0x94
[59928.491109]  [] ? scsi_request_fn+0x303/0x3c3 [scsi_mod]
[59928.491116]  [] ? _raw_spin_lock_irqsave+0x8/0x21
[59928.491121]  [] ? should_resched+0x5/0x1e
[59928.491128]  [] ? ipw_bg_up+0x1c/0x25 [ipw2200]
[59928.491134]  [] ? process_one_work+0x112/0x1fa
[59928.491141]  [] ? ipw_net_init+0x32/0x32 [ipw2200]
[59928.491146]  [] ? worker_thread+0xa9/0x122
[59928.491150]  [] ? manage_workers.isra.23+0x13d/0x13d
[59928.491155]  [] ? kthread+0x63/0x68
[59928.491160]  [] ? kthread_worker_fn+0x101/0x101
[59928.491167]  [] ? kernel_thread_helper+0x6/0x10
[59928.491170] ---[ end trace 489947a6c8cb68b7 ]---
[59928.491174] ipw2200 :04:02.0: firmware: ipw2200-bss.fw will not be loaded
[59928.491178] ipw2200: ipw2200-bss.fw request_firmware failed: Reason -16
[59928.491182] ipw2200: Unable to load firmware: -16


-- Package-specific info:
** Version:
Linux version 3.2.0-3-686-pae (Debian 3.2.23-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP 
Mon Jul 23 03:50:34 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-3-686-pae 
root=UUID=88262002-52a8-49fa-ab66-637759ec0159 ro acpi_sleep=s3_bios splash 
quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[124138.880450] snd_intel8x0 :00:1e.2: restoring config space at offset 0x1 
(was 0x297, writing 0x293)
[124138.880608] tg3 :02:00.0: restoring config space at offset 0xc (was 
0x0, writing 0xac00)
[124138.880638] tg3 :02:00.0: restoring config space at offset 0x1 (was 
0x100102, writing 0x100106)
[124138.896067] sdhci-pci :04:00.1: BAR 0: set to [mem 
0xa0201000-0xa02010ff] (PCI address [0xa0201000-0xa02010ff])
[124138.896105] sdhci-pci :04:00.1: restoring config space at offset 0x3 
(was 0x80, writing 0x804000)
[124138.896115] sdhci-pci :04:00.1: restoring config space at offset 0x1 
(was 0x210, writing 0x2100106)
[124138.896376] PM: early resume of devices complete after 56.287 msecs
[124138.896531] i915 :00:02.0: power state changed by ACPI to D0
[124138.896536] i915 :00:02.0: power state changed by ACPI to D0
[124138.896545] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[124138.896550] i915 :00:02.0: setting latency timer to 64
[124138.952450] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[124138.952454] uhci_hcd :00:1d.0: power state changed by ACPI to D0
[124138.952461] uhci_hcd :00:1d.0: PCI INT A -> GSI 16 (level, low) -> IRQ 
16
[124138.952469] uhci_hcd :00:1d.0: setting latency timer to 64
[124138.952496] usb usb2: root hub lost power or was reset
[124138.952509] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[124138.952513] uhci_hcd :00:1d.1: power state changed by ACPI to D0
[124138.952519] uhci_hcd :00:1d.1: PCI INT B -> GSI 17 (level, low) -> IRQ 
17
[124138.952527] uhci_hcd :00:1d.1: setting latency timer to 64
[124138.952552] usb usb3: root hub lost power or was reset
[124138.952566] uhci_hcd :

Bug#508685: linux-image-2.6.26-1-amd64: Cannot mute cx8800 v4l card

2010-08-11 Thread Stefan Ott
It seems I failed to properly mark this one as forwarded. Anyway, it's
at https://bugzilla.kernel.org/show_bug.cgi?id=16566

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinf9hprifzjwgby_d7azw55-ass4ck3yxvzh...@mail.gmail.com



Bug#508685: linux-image-2.6.26-1-amd64: Cannot mute cx8800 v4l card

2010-08-11 Thread Stefan Ott
forwarded 508685 https://bugzilla.kernel.org/show_bug.cgi?id=16566
thanks



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinhseaaw5bigdro3zzx2q=dia-tvbznkyfky...@mail.gmail.com



Bug#508685: linux-image-2.6.26-1-amd64: Cannot mute cx8800 v4l card

2010-07-01 Thread Stefan Ott
On Wed, Feb 17, 2010 at 20:56, Moritz Muehlenhoff  wrote:
> On Thu, Aug 27, 2009 at 02:10:29AM +0200, Stefan Ott wrote:
>> > Does this still occur with more recent versions of the kernel?
>>
>> Yes, still happens on linux-image-2.6.30-1-amd64
>
> Sorry for the late reply, this fell through the cracks :-/
>
> The next release of Debian (6.0, code name Squeeze) will be based
> on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
> us whether the problem persists. If so, we should report it upstream
> to the kernel.org developers:
>
> http://bugzilla.kernel.org (Product: Drivers, Component: Video(Other))
>
> The 2.6.32 kernel is available from packages.debian.org and can
> be installed in both Debian stable, testing and unstable
> installations.

Hi

Sorry for my late reply this time, things are a little busy :)

Anyway: yes, this still happens with 2.6.32-5-amd64 (and with vanilla 2.6.34).

Should I go and report it upstream myself or are you going to do that?

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktinwmcmyntilbd8uxwqtliiesrixgr5kidjly...@mail.gmail.com



Bug#570364: Output LVDS gone on Intel Mobile 915GM

2010-05-01 Thread Stefan Ott
>> Have you done this?  I forgot to say, let us know the bug number so we
>> can track it.
>
> Stefan, did you report this upstream or is it fixed in current sid kernel?

Hi

Sorry for the delay - I haven't had time to try newer kernel versions
yet (it takes an awful lot of time to compile a kernel on that
machine).

I'll try 2.6.34-rc6 some time in the next few days and, if it's still
broken, report the issue upstream.

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/t2qdffbd58d1005012053mba993af9oe23d69382b782...@mail.gmail.com



Bug#570364: Output LVDS gone on Intel Mobile 915GM

2010-02-18 Thread Stefan Ott
> Please test the current version, 2.6.32-8, which has many fixes for the
> i915 video driver.

Thanks, I tried but I still get the same result (dmesg attached)

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"


dmesg.2.6.32-2-686
Description: Binary data


Bug#508685: linux-image-2.6.26-1-amd64: Cannot mute cx8800 v4l card

2009-08-26 Thread Stefan Ott
> Does this still occur with more recent versions of the kernel?

Yes, still happens on linux-image-2.6.30-1-amd64

cheers
-- 
Stefan Ott
http://www.ott.net/

"You are not Grey Squirrel?"



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#508685: linux-image-2.6.26-1-amd64: Cannot mute cx8800 v4l card

2008-12-13 Thread Stefan Ott
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-11
Severity: normal


Hi

I cannot seem to mute my cx8800 tv/radio tuner card (tried with various radio
applications). The commands run without errors (eg. "radio -c /dev/radio0 -qm")
but the card keeps sending audio. Reloading the kernel module doesn't help
either, it only resets the tuner's frequency.

If I manually set the tuner type (eg. using radio=59 or radio=61), muting
suddenly seems to work - unfortunately, this breaks tuning (ie. i get white
noise when i start the radio application but as soon as i change frequency all
audio stops).

IMHO this means that there might have to be a new tuner type, using the tuning
mechanism from the auto-detected type and muting/unmuting from type 59 or 61.

My lspci entries for the card are:

05:04.1 Multimedia controller [0480]: Conexant Systems, Inc. 
CX23880/1/2/3 PCI Video and Audio Decoder [Audio Port] [14f1:8811] (rev 03)
Subsystem: Hauppauge computer works Inc. Hauppauge WinTV 34xxx 
models [0070:3401]

(for details, see below)

cheers
Stefan

-- Package-specific info:
** Version:
Linux version 2.6.26-1-amd64 (Debian 2.6.26-11) (wa...@debian.org) (gcc version 
4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Nov 26 18:26:02 UTC 
2008

** Command line:
root=/dev/md1 ro irqpoll vga=0x317 

** Not tainted

** Kernel log:
[7.331482] md: md1 stopped.
[7.387476] md: bind
[7.395471] md: bind
[7.403466] raid1: raid set md1 active with 2 out of 2 mirrors
[7.495048] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
[7.501992] SGI XFS Quota Management subsystem
[7.511043] Filesystem "md1": Disabling barriers, not supported by the 
underlying device
[7.515213] XFS mounting filesystem md1
[7.598957] Ending clean XFS mount for filesystem: md1
[9.239769] udevd version 125 started
[9.868827] input: Power Button (FF) as /class/input/input5
[9.923407] ACPI: Power Button (FF) [PWRF]
[9.928959] input: Power Button (CM) as /class/input/input6
[9.988223] ACPI: Power Button (CM) [PWRB]
[   10.103222] input: PC Speaker as /class/input/input7
[   10.178000] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.03 (30-Apr-2008)
[   10.182083] iTCO_wdt: Found a ICH9 TCO device (Version=2, TCOBASE=0x0460)
[   10.188775] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   10.257155] ACPI: PCI Interrupt :00:1f.3[B] -> GSI 18 (level, low) -> 
IRQ 18
[   10.537012] Error: Driver 'pcspkr' is already registered, aborting...
[   10.566113] ACPI: PCI Interrupt :00:1b.0[A] -> GSI 22 (level, low) -> 
IRQ 22
[   10.570249] PCI: Setting latency timer of device :00:1b.0 to 64
[   10.600332] hda_codec: Unknown model for ALC883, trying auto-probe from 
BIOS...
[   12.236344] Filesystem "md1": Disabling barriers, not supported by the 
underlying device
[   13.226982] loop: module loaded
[   13.291520] w83627ehf: Found W83627DHG chip at 0x290
[   13.314149] coretemp coretemp.0: Using relative temperature scale!
[   13.319572] coretemp coretemp.1: Using relative temperature scale!
[   13.388409] md: md0 stopped.
[   13.582997] md: bind
[   13.591014] md: bind
[   13.645679] raid1: raid set md0 active with 2 out of 2 mirrors
[   13.656061] md: md2 stopped.
[   13.706166] md: bind
[   13.714604] md: bind
[   13.744115] raid1: raid set md2 active with 2 out of 2 mirrors
[   13.748230] md: md3 stopped.
[   13.823695] md: bind
[   13.828373] md: bind
[   13.862518] raid1: raid set md3 active with 2 out of 2 mirrors
[   14.613632] kjournald starting.  Commit interval 5 seconds
[   14.647049] EXT3 FS on md0, internal journal
[   14.655429] EXT3-fs: mounted filesystem with ordered data mode.
[   14.683412] Filesystem "md2": Disabling barriers, not supported by the 
underlying device
[   14.683472] XFS mounting filesystem md2
[   14.768482] Ending clean XFS mount for filesystem: md2
[   14.812902] Filesystem "md3": Disabling barriers, not supported by the 
underlying device
[   14.816598] XFS mounting filesystem md3
[   15.088970] Ending clean XFS mount for filesystem: md3
[   16.515531] sky2 eth0: enabling interface
[   18.310461] NET: Registered protocol family 10
[   18.314189] lo: Disabled Privacy Extensions
[   18.317060] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   18.387798] sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
[   18.392605] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   26.695365] ACPI: PCI Interrupt :01:00.0[A] -> GSI 16 (level, low) -> 
IRQ 16
[   26.864082] [drm] Initialized drm 1.1.0 20060810
[   26.876838] PCI: Setting latency timer of device :01:00.0 to 64
[   26.876838] [drm] Initialized radeon 1.29.0 20080528 on minor 0
[   27.289257] [drm] Setting GART location based on new memory map
[   27.289257] [drm] Loading R500 Microcode
[   27.289257] [drm] Num pipes: 3
[   27.289257] [drm] writeback test succeeded in 1 usecs
[   29.548067] eth0: no IPv6 routers pre