FS#7598 - 2.6.22 showstoppers
Attached to Project:
Arch Linux
Opened by Thomas Bächler (brain0) - Tuesday, 10 July 2007, 15:20 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 30 July 2007, 20:34 GMT
Opened by Thomas Bächler (brain0) - Tuesday, 10 July 2007, 15:20 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 30 July 2007, 20:34 GMT
|
Details
This is a collection of bugs that need to be fixed before
2.6.22 can be moved to current.
- madwifi is broken (kth5 fixed it for x86_64, i686?? please build!) |
vboxdrv: Trying to deactivate NMI watchdog permanently...
vboxdrv: Successfully done.
general protection fault: 0000 [1] PREEMPT SMP
CPU 1
Modules linked in: vboxdrv nvidia(P) ipv6 usbhid hid ff_memless snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device firewire_ohci firewire_core crc_itu_t snd_pcm_oss snd_mixer_oss snd_hda_intel snd_pcm wlan_scan_sta rtc_cmos rtc_core ath_rate_sample ohci1394 ieee1394 rtc_lib snd_timer snd soundcore snd_page_alloc pcspkr i2c_nforce2 i2c_core k8temp serio_raw ohci_hcd psmouse ath_pci wlan forcedeth ehci_hcd ath_hal(P) tsdev evdev thermal fan button battery ac fuse tun powernow_k8 freq_table processor usbcore ext3 jbd mbcache ide_cd cdrom sd_mod generic sata_nv amd74xx ide_core libata
Pid: 7385, comm: VirtualBox Tainted: P 2.6.22-ARCH #1
RIP: 0010:[<ffffffff888b077a>] [<ffffffff888b077a>] :vboxdrv:g_abExecMemory+0x319a/0x180000
RSP: 0000:ffff81001f2f5f20 EFLAGS: 00010056
RAX: 0000000000001d01 RBX: 0000000000000595 RCX: 00000000c0000080
RDX: 0000000000000000 RSI: 0000000000000d01 RDI: 00002aaaab11b000
RBP: ffff81001f2f5f28 R08: 0000000068747541 R09: 0000000000002001
R10: 0000000001000000 R11: 00000000444d4163 R12: 00002aaaab11b000
R13: 0000000000010004 R14: 00002aaaabc7cb60 R15: 00000000fffffdff
FS: 00000000411c8950(0063) GS:ffff810037ffc340(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00002af83b996d10 CR3: 0000000026d33000 CR4: 00000000000006e0
Process VirtualBox (pid: 7385, threadinfo ffff81001f2f4000, task ffff810037e9c900)
Stack: 0000000000000097 ffff81001f2f5fa8 ffffffff888ada57 00002aaaac035390
00002aaaabc7cb60 00000000fffffdff ffffffff8049bfad 00000000fffffdff
00002aaaabc7cb60 00002aaaac035390 00002aaaab5e1000 00000000411c7ef0
Call Trace:
[<ffffffff888ada57>] :vboxdrv:g_abExecMemory+0x477/0x180000
[<ffffffff8049bfad>] error_exit+0x0/0x84
[<ffffffff888ecf66>] :vboxdrv:g_abExecMemory+0x3f986/0x180000
Code: 0f 30 f7 c6 00 10 00 00 0f 84 27 ff ff ff c6 87 c8 dd 00 00
RIP [<ffffffff888b077a>] :vboxdrv:g_abExecMemory+0x319a/0x180000
RSP <ffff81001f2f5f20>
- vmware doesn't build for 2.6.22, but there are patches available. if you ask me, use virtualbox, it is always the same trouble with vmware
- can anyone fix kvm? I cannot test it at all. Why don't we use the kvm version shipped with 2.6.22?
I suggest to give the kvm modules from the vanilla kernel a try because with kernel 2.6.22 you can use kvm-22 and later. So it seems the time that you have to use a certain version is over. But perhaps my english is too bad and i misunderstood it.-)
Using the kernel26-fallback.img symptoms are identical. Have tried adding legacy_ide earlymodules=sis to the relevant line in grub, to no avail.
This system boots successfully using the stock 2.6.21 kernel (although error message occur during booting when accessing ATA).
worked fine in 2.6.21. but the USB ID of the drive is generally a bit wierd as well being 1234:5678 so dunno if some blacklisting in stock 2.6.22 is to blame.
since this bug is also present in 2 other distro's 2.6.22 packages i've tried(Gentoo,Ubuntu Gutsy).
-------------------------------------------------------------------------------------------
Jul 13 00:04:44 midera usb 4-3: USB disconnect, address 2
Jul 13 00:15:54 midera usb 4-3: new high speed USB device using ehci_hcd and address 5
Jul 13 00:15:54 midera usb 4-3: configuration #1 chosen from 1 choice
Jul 13 00:15:54 midera input: Sarotech Co., Ltd. Shiny new device as /class/input/input5
-------------------------------------------------------------------------------------------
the part of dmesg generated when i re-plug the drive back in. on 2.6.21 it goes right over usb-storage's init sequence and finds the 1 partition and the main device node.
@revellion: I have never seen such a stupid bug. A usb device knows what it is, and confusing a touchscreen with a hard drive shouldn't happen. There has to be something seriously wrong there.
@attila: Someone in the dev team thought it would be a great idea to build KVM separately, I don't know the reasons. I am not in any position to test it, so I won't be able to fix the bugs until I get a definite answer. But your post suggest that building the kvm version included in linux would be a good idea.