View previous topic :: View next topic |
Author |
Message |
rmalagon n00b
Joined: 09 Jul 2004 Posts: 1
|
Posted: Fri Jul 09, 2004 10:41 pm Post subject: Fix to ebuild |
|
|
Code: | I'm getting this when I try to create the digest...
Code:
root@bender love-sources # ebuild love-sources-2.6.7-r8.ebuild digest
>>> Generating digest file...
<<< linux-2.6.7.tar.bz2
<<< 2.6.7-mm7.bz2
<<< 2.6.7-love8.bz2
<<<
ebuild: this ebuild generated output during the depend phase (bad)
Not sure what that means...anyone else? |
The problem in the ebuild is in this line:
LOVEPV_SRC="http://www.obilan.org/love-sources/${KV}.bz2 http://server3.xlhost.de/eggdrop_14019/love-sources/"
I had deleted the last mirror and the digest process is ok now.
LOVEPV_SRC="http://www.obilan.org/love-sources/${KV}.bz2" |
|
Back to top |
|
|
pArt1cl3 n00b
Joined: 01 Sep 2003 Posts: 5
|
Posted: Sat Jul 10, 2004 2:26 am Post subject: vesafb error |
|
|
seems like process vesafb is causing a segfault upon boot, looks like a conflict with the scheduler
not sure though
anyone else having similar? |
|
Back to top |
|
|
HydroSan l33t
Joined: 04 Mar 2004 Posts: 764 Location: The Kremlin (aka Canada)
|
Posted: Sat Jul 10, 2004 2:31 am Post subject: |
|
|
gmichels wrote: | Never had anything similar. |
I had similar problems. It's the 4K stacks hard-locking your system. For some reason, even with the new nVidia drivers, everything segfaults. _________________ I was a Gangster for Capitalism, by Major General Smedley Butler.
Server status: Currently down, being replaced with fresh install - 20% completed. |
|
Back to top |
|
|
phlashback Tux's lil' helper
Joined: 27 Jul 2002 Posts: 142 Location: Normal
|
Posted: Sat Jul 10, 2004 3:36 am Post subject: |
|
|
I I limit my video ram (allocated to Framebuffer) to 16MB, I hang at that point with a message the DCC is not supported by the hardware. Nvidia Ti 4600. If I dont limit the framebuffer memory I happily passes (w/o framebuffer) gets all the way to the point that the init scripts start the RTC or Random number generator (I have forgotto which.) at any rate it hangs right before USB hotplugging is started. I have tride w and w/o 4k stacks and preempt all the same.
Actually I have had this problem since 2.6.7-love6
any ideas _________________ The terrible thing about hell is that when you're there you can't even tell as you move through this life you love so you could be there and not even know |
|
Back to top |
|
|
v3rtigo Apprentice
Joined: 15 Jun 2004 Posts: 179
|
Posted: Sat Jul 10, 2004 3:41 am Post subject: |
|
|
i'm having problem with alsa, it says that it can't find sound driver.
and i have problem to connect to the internet using ppp.
it says ppp0: can't patch intarface info something like this. |
|
Back to top |
|
|
sau2004 n00b
Joined: 29 Jun 2004 Posts: 28
|
Posted: Sat Jul 10, 2004 4:41 am Post subject: |
|
|
Did anyone get ATI drivers working (accelerated)? I tried to emerge ati-drivers, but it wont compile, it gave me this error:
Code: |
Calculating dependencies ...done!
>>> emerge (1 of 1) media-video/ati-drivers-3.9.0-r1 to /
>>> md5 src_uri ;-) fglrx-4.3.0-3.9.0.i386.rpm
* X11 implementation is xfree.
>>> Unpacking source...
>>> Unpacking fglrx-4.3.0-3.9.0.i386.rpm
* Applying fglrx-2.6-vmalloc-vmaddr.patch... [ ok ]
* Applying fglrx-2.6-get-page.patch... [ ok ]
* Applying fglrx-3.9.0-regparm.patch... [ ok ]
>>> Source unpacked.
* Building the DRM module...
make: Entering directory `/usr/src/linux-2.6.7-love8'
CC [M] /var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/agp3.o
CC [M] /var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/nvidia-agp.o
CC [M] /var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/agpgart_be.o
CC [M] /var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/i7505-agp.o
CC [M] /var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/firegl_public.o
/var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/firegl_public.c:48:2: #error unknown or undefined architecture configured
make[1]: *** [/var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod/firegl_public.o] Error 1
make: *** [_module_/var/tmp/portage/ati-drivers-3.9.0-r1/work/lib/modules/fglrx/build_mod] Error 2
make: Leaving directory `/usr/src/linux-2.6.7-love8'
* DRM module not built
|
|
|
Back to top |
|
|
Mafteah Apprentice
Joined: 30 May 2003 Posts: 265 Location: IL
|
|
Back to top |
|
|
tatesworld n00b
Joined: 25 Oct 2003 Posts: 67
|
Posted: Sat Jul 10, 2004 7:33 am Post subject: |
|
|
dont forget to
renice -10 `pidof X`
from the man himself with those new np patches apparantly |
|
Back to top |
|
|
stahlsau Guru
Joined: 09 Jan 2004 Posts: 584 Location: WildWestwoods
|
Posted: Sat Jul 10, 2004 7:45 am Post subject: |
|
|
Kernel from first page works fine here (with 4k-Stacks).
Patch -R fails on 1 hunk, trying to fix now. |
|
Back to top |
|
|
Mafteah Apprentice
Joined: 30 May 2003 Posts: 265 Location: IL
|
Posted: Sat Jul 10, 2004 7:56 am Post subject: |
|
|
stahlsau wrote: | Kernel from first page works fine here (with 4k-Stacks).
Patch -R fails on 1 hunk, trying to fix now. |
You dont need to fix it becuse np7 will apply it back so just leave it! _________________ http://www.mafteah.co.il |
|
Back to top |
|
|
stahlsau Guru
Joined: 09 Jan 2004 Posts: 584 Location: WildWestwoods
|
Posted: Sat Jul 10, 2004 8:22 am Post subject: |
|
|
yeah, i´ve seen. -Rp1 fails, -p1 too. There´s no change between those lines
ok, again, everything works. What´s wrong with love? |
|
Back to top |
|
|
HydroSan l33t
Joined: 04 Mar 2004 Posts: 764 Location: The Kremlin (aka Canada)
|
Posted: Sat Jul 10, 2004 8:39 am Post subject: |
|
|
phlashback wrote: | I I limit my video ram (allocated to Framebuffer) to 16MB, I hang at that point with a message the DCC is not supported by the hardware. Nvidia Ti 4600. If I dont limit the framebuffer memory I happily passes (w/o framebuffer) gets all the way to the point that the init scripts start the RTC or Random number generator (I have forgotto which.) at any rate it hangs right before USB hotplugging is started. I have tride w and w/o 4k stacks and preempt all the same.
Actually I have had this problem since 2.6.7-love6
any ideas |
Bootsplash also freezes for me.
nVidia GeForceFX 5600. _________________ I was a Gangster for Capitalism, by Major General Smedley Butler.
Server status: Currently down, being replaced with fresh install - 20% completed. |
|
Back to top |
|
|
TecHunter Tux's lil' helper
Joined: 15 Feb 2003 Posts: 124
|
Posted: Sat Jul 10, 2004 9:10 am Post subject: |
|
|
i got the similar message...
but it seems everything works fine.
gmichels wrote: | Lots of debugging stuff while booting up, although everything looks just fine.
Code: | dmesg snip...
powernow: Minimum speed 530 MHz. Maximum speed 1788 MHz.
ACPI: (supports S0 S3 S4 S5)
RAMDISK: Couldn't find valid RAM disk image starting at 0.
VFS: Mounted root (reiser4 filesystem) readonly.
Freeing unused kernel memory: 156k freed
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Adding 257032k swap on /dev/hda2. Priority:-1 extents:1
Real Time Clock Driver v1.12
natsemi dp8381x driver, version 1.07+LK1.0.17, Sep 27, 2002
originally by Donald Becker <becker@scyld.com>
http://www.scyld.com/network/natsemi.html
2.4.x kernel port by Jeff Garzik, Tjeerd Mulder
ACPI: PCI interrupt 0000:00:12.0[A] -> GSI 11 (level, low) -> IRQ 11
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
natsemi eth0: NatSemi DP8381[56] at 0xde80c000 (0000:00:12.0), 00:0b:cd:a4:9f:f3, IRQ 11, port TP.
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
ACPI: PCI interrupt 0000:00:02.0[A] -> GSI 10 (level, low) -> IRQ 10
ohci_hcd 0000:00:02.0: ALi Corporation USB 1.1 Controller
ohci_hcd 0000:00:02.0: irq 10, pci mem de80e000
ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected Ati IGP320/M chipset
agpgart: Maximum main memory to use for agp memory: 408M
agpgart: AGP aperture is 64M @ 0xe4000000
eth0: DSPCFG accepted after 0 usec.
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
ACPI: PCI interrupt 0000:00:06.0[A] -> GSI 5 (level, low) -> IRQ 5
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
ACPI: PCI interrupt 0000:00:0a.0[A] -> GSI 11 (level, low) -> IRQ 11
Yenta: CardBus bridge found at 0000:00:0a.0 [0000:0000]
Yenta: ISA IRQ mask 0x0018, PCI irq 11
Socket status: 30000007
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
parport: PnPBIOS parport detected.
parport0: PC-style at 0x378 (0x778), irq 7, dma 0 [PCSPP,TRISTATE,COMPAT,ECP,DMA]
Unable to handle kernel NULL pointer dereference at virtual address 000000b8
printing eip:
c0111d59
*pde = 00000000
Oops: 0000 [#1]
PREEMPT
Modules linked in: parport_pc lp parport yenta_socket pcmcia_core snd_ali5451 snd_ac97_codec snd_pcm snd_page_alloc snd_timer snd soundcore ati_agp agpgart evdev ohci_hcd usbcore natsemi rtc
CPU: 0
EIP: 0060:[<c0111d59>] Not tainted VLI
EFLAGS: 00010216 (2.6.7-love8)
EIP is at dma_alloc_coherent+0x19/0x100
eax: 00000000 ebx: ffffffff ecx: 00000fff edx: 00000000
esi: dbd43660 edi: 00000004 ebp: 00000020 esp: dd6e7e58
ds: 007b es: 007b ss: 0068
Process modprobe (pid: 8647, threadinfo=dd6e6000 task=dd866c30)
Stack: c010cff0 00000007 dc936c20 dfa30a34 c15a3e00 dbd43660 00000004 dbd43684
dfa2ee46 00000000 00001000 dbd4367c 00000020 c15a3e00 dc936c20 dc936c40
ffffffff c15a0000 00000000 00000378 00000007 dfa2fbe4 00000378 00000778
Call Trace:
[<c010cff0>] request_irq+0x80/0xd0
[<dfa2ee46>] parport_pc_probe_port+0x446/0x740 [parport_pc]
[<dfa2fbe4>] parport_pc_pnp_probe+0xa4/0xe0 [parport_pc]
[<dfa2fb40>] parport_pc_pnp_probe+0x0/0xe0 [parport_pc]
[<c02a197e>] pnp_device_probe+0x6e/0xb0
[<c02caa6f>] bus_match+0x3f/0x70
[<c02cab99>] driver_attach+0x59/0x90
[<c02cb235>] bus_add_driver+0xa5/0xd0
[<c02cb8df>] driver_register+0x2f/0x40
[<c02a1a5d>] pnp_register_driver+0x2d/0x60
[<df9fc191>] parport_pc_find_ports+0x71/0x90 [parport_pc]
[<df9fc616>] parport_pc_init+0x1d6/0x1d8 [parport_pc]
[<c0139e4f>] sys_init_module+0x13f/0x280
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Code: 85 74 ff ff ff 51 e8 47 2e 15 00 59 e9 68 ff ff ff 90 55 57 56 53 bb ff ff ff ff 83 ec 10 8b 4c 24 28 8b 44 24 24 8b 6c 24 30 49 <8b> b0 b8 00 00 00 c1 e9 0b 89 4c 24 0c 43 d1 6c 24 0c 75 f9 83
<6>lp: driver loaded but no devices found
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c0130a60>] wait_for_helper+0x0/0xb0
[<c0109297>] kernel_thread_helper+0xb/0x14
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c0130a60>] wait_for_helper+0x0/0xb0
[<c0109297>] kernel_thread_helper+0xb/0x14
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c0130a60>] wait_for_helper+0x0/0xb0
[<c0109297>] kernel_thread_helper+0xb/0x14
eth0: remaining active for wake-on-lan
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
ndiswrapper version 0.8 loaded
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c012445a>] do_group_exit+0x3a/0xb0
[<c010b0f5>] sysenter_past_esp+0x52/0x71
ndiswrapper adding bcmwl5.sys
ACPI: PCI interrupt 0000:00:09.0[A] -> GSI 10 (level, low) -> IRQ 10
wlan0: ndiswrapper ethernet device 00:0b:cd:56:cb:35 using driver bcmwl5.sys
Debug: sleeping function called from invalid context at fs/proc/base.c:1529
in_atomic():1, irqs_disabled():0
[<c011f3a0>] __might_sleep+0xb0/0xe0
[<c018feaf>] proc_pid_flush+0x1f/0x50
[<c0122c1d>] release_task+0x13d/0x1e0
[<c0123a60>] exit_notify+0x380/0x890
[<c012419d>] do_exit+0x22d/0x450
[<c0130a60>] wait_for_helper+0x0/0xb0
[<c0109297>] kernel_thread_helper+0xb/0x14 |
Never had anything similar. |
_________________ Gentoo is GREAT!!! |
|
Back to top |
|
|
Pink Veteran
Joined: 24 Jul 2003 Posts: 1062
|
Posted: Sat Jul 10, 2004 9:29 am Post subject: |
|
|
All the people getting the debugging messages on bootup - are you using reiser4?
Please respond as I'm trying to get a link between the new mm's and the reiser4 problems which are creeping back in - hopefully to try and resolve it somehow. |
|
Back to top |
|
|
pArt1cl3 n00b
Joined: 01 Sep 2003 Posts: 5
|
Posted: Sat Jul 10, 2004 10:33 am Post subject: |
|
|
the messages i get reference the scheduler and vesafb, nothing of reiser processes |
|
Back to top |
|
|
Pink Veteran
Joined: 24 Jul 2003 Posts: 1062
|
Posted: Sat Jul 10, 2004 10:53 am Post subject: |
|
|
pArt1cl3 wrote: | the messages i get reference the scheduler and vesafb, nothing of reiser processes |
Thanks, if you get messages like the ones posted by gmichels, and then qouted just above here by TecHunter can you tell me if you are using resier4.
It doesn't particularly matter what they reference, it's the atomic debugging messages I am interested in and whether ppl get them who use reiser4 or who don't use reiser4.
So, in summary, if you get the atomic messages at boot up can you tell me if you use reiser4 or not.
Many thanks
|
|
Back to top |
|
|
X-Ryl669 Tux's lil' helper
Joined: 16 Feb 2004 Posts: 135
|
Posted: Sat Jul 10, 2004 11:21 am Post subject: |
|
|
USB still not working with me (Hang with USB hotplugging).
Trying USB fix patch from love7 _________________ Think it twice, think it thrice, you never think enough... |
|
Back to top |
|
|
gmichels Guru
Joined: 20 Jun 2003 Posts: 480 Location: Brazil
|
Posted: Sat Jul 10, 2004 2:16 pm Post subject: |
|
|
Yes, reiser4 here on everything (except /boot)
Also using 8k stacks, since 4k hard locks while loading ohci-hcd. |
|
Back to top |
|
|
boroshan l33t
Joined: 16 Apr 2003 Posts: 730 Location: upside down
|
Posted: Sat Jul 10, 2004 2:17 pm Post subject: ack! |
|
|
I compiled it, and found ipw2100 wouldn't emerge.
That turned out to be the missing include problem from two/three loves back. PickedOnion's suggestion of copying the /usr/include file into the kernel include allowed me to compile the module, load it and get online.
Then it hung when I switched virtual consoles, and when I rebooted my R4 root partition was fscked
So I booted back into my emergency r3 partition and am rebuilding my partition. I don't know that it was a love problem - it could have been that I needed to reload the hostap-driver mods or something. But that hang is still worrying. Especially as I was runnning with the recommended renices for X and the R4 demons.
[edit]
....and speaking of the picked one, yes, I too was getting those debug messages in my boot ssequence _________________ Don't let THEM immanentize the Eschaton! |
|
Back to top |
|
|
MrNugget Tux's lil' helper
Joined: 15 Nov 2003 Posts: 144 Location: Germany
|
Posted: Sat Jul 10, 2004 3:19 pm Post subject: |
|
|
Hi, i cannot boot my system because of this error:
Code: | <6>note: vesafb[27] exited with preempt_count 2 |
I read through this post and my lilo looks like this:
Code: | image = /boot/mykernel-2.6.7-love8
root = /dev/hda3
label = Love-8-2.6.7
read-only
append = "video=vesafb:ywrap,mtrr,1024x768-16@60 elevator=cfq devfs=nomount"
initrd=/boot/initrd-1024x768 |
But i still get this error and cannot boot. So what should i do? :/
Regards,
MrNugget
[/url] |
|
Back to top |
|
|
LinuxRocks Guru
Joined: 27 Nov 2003 Posts: 397 Location: New Mexico
|
Posted: Sat Jul 10, 2004 3:52 pm Post subject: |
|
|
I was using Love 4 still and it worked flawlessly. However, now using this new love (Love Eight) and everythin boots fine and runs good, but when I reboot the machine, I get a Seg Fault in /etc/hotplug/usb.rc line 393: 8932 segmentation fault rmmod ohci-hcd > /dev/null 2>&1
I've tried the USB patch for Love7 and it still doesnt work right.
I dont get this with the Love 4 or the CK sources.
Any ideas?
Thanks!!!
Joe |
|
Back to top |
|
|
Ricky Guru
Joined: 30 May 2003 Posts: 341
|
Posted: Sat Jul 10, 2004 4:35 pm Post subject: |
|
|
TecHunter wrote: | i got the similar message...
but it seems everything works fine.
gmichels wrote: | Lots of debugging stuff while booting up, although everything looks just fine.
<snip>
Never had anything similar. |
|
ditto |
|
Back to top |
|
|
LinuxRocks Guru
Joined: 27 Nov 2003 Posts: 397 Location: New Mexico
|
Posted: Sat Jul 10, 2004 4:49 pm Post subject: |
|
|
Ricky wrote: | TecHunter wrote: | i got the similar message...
but it seems everything works fine.
gmichels wrote: | Lots of debugging stuff while booting up, although everything looks just fine.
<snip>
Never had anything similar. |
|
ditto |
Sounds like you have Sleep-inside-spinlock checking enabled in Kernel Hacking.
Dissable that and see if it does away...
Joe |
|
Back to top |
|
|
474 l33t
Joined: 19 Apr 2002 Posts: 714
|
Posted: Sat Jul 10, 2004 4:51 pm Post subject: |
|
|
tatesworld wrote: | dont forget to
renice -10 `pidof X`
from the man himself with those new np patches apparantly |
For a nifty way of addressing that requirement, see the 4th post I made here. |
|
Back to top |
|
|
phlashback Tux's lil' helper
Joined: 27 Jul 2002 Posts: 142 Location: Normal
|
Posted: Sat Jul 10, 2004 5:40 pm Post subject: |
|
|
Ok I have made some progress... still 4k stacks and preempt dont play nice. I can use one or the other no problems with hard locking.
I had to enable all of my usb modules in my /etc/modules.autoload.d/kernel-2.6 except ohci-hcd. If I had nothing in the kernel-2.6 the system would hard lock at the point that USB Hotplugging should start, If I enabled all in the kernel-2.6 I would hard lock as it tried to load it.
my kernel config has 640x480 default frambuffer
not passing any video= command to the kernel i get this, and boot w/o framebuffer
Code: | vesafb: NVidia Corporation, NV25 Board, Chip Rev (OEM: NVidia)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:e350
vesafb: pmi: set display start = c00ce395, set palette = c00ce41a
vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003
d103 d203 d303 d403 d503 da03 ff03
vesafb: hardware doesn't support DCC transfers
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: total memory: 134217728
vesafb: scrolling: redraw
vesafb: abort, cannot ioremap video memory 0x8000000 @ 0xe0000000
vesafb: probe of vesafb0 failed with error -5
Machine check exception polling timer started.
|
if I pass video=vesafb:vram:16,ywrap,mtrr,1280x1024-16@75
i get this: and a hard lock
Code: | vesafb: NVidia Corporation, NV25 Board, Chip Rev (OEM: NVidia)
vesafb: VBE version: 3.0
vesafb: protected mode interface info at c000:e350
vesafb: pmi: set display start = c00ce395, set palette = c00ce41a
vesafb: pmi: ports = b4c3 b503 ba03 c003 c103 c403 c503 c603 c703 c803 c903 cc03 ce03 cf03 d003
d103 d203 d303 d403 d503 da03 ff03
vesafb: hardware doesn't support DCC transfers
vesafb: monitor limits: vf = 0 Hz, hf = 0 kHz, clk = 0 MHz
vesafb: total memory: 16777216
vesafb: scrolling: redraw
Machine check exception polling timer started.
|
Any Ideas here _________________ The terrible thing about hell is that when you're there you can't even tell as you move through this life you love so you could be there and not even know |
|
Back to top |
|
|
|