Re: Lots of PREEMPT on 2.6.7-6 and 2.6.7-3. 2.6.8-3 panics before mounting anything.
ANd the Panic was:
pivot_root: No such file or directory
/usr/sbin..
It has something to do with my SATA-root drive changing from /dev/hdg to
/dev/sda,
but I cannot get i to workSomebody mentioned trying to hack initrd, but I
don't know how.
In The Night ([EMAIL PROTECTED]) wrote:
Home brewed 2.6.6 DOES work so far
Here a snippet from messages:
Sep 12 22:52:37 localhost kernel: PML4 0
Sep 12 22:52:37 localhost kernel: CPU 0
Sep 12 22:52:37 localhost kernel: Modules linked in: nls_cp437 usb_storage
sd_mod snd_pcm_oss snd_mixer_oss sg scsi_m
od lp mousedev ipv6 genrtc af_packet ehci_hcd uhci_hcd emu10k1_gp gameport
snd_emu10k1 snd_rawmidi snd_pcm snd_timer
snd_seq_device snd_ac97_codec snd_page_alloc snd_util_mem snd_hwdep snd
soundcore dm_mod raid1 md capability commonca
p dv1394 ohci1394 ieee1394 parport_pc parport r8169 crc32 nvidia sermouse
psmouse cpuid proc_intf freq_table cpufreq_
userspace cpufreq_powersave button fan processor w83627hf eeprom i2c_sensor
i2c_isa i2c_viapro i2c_core ide_cd cdrom
xfs reiserfs jfs vfat fat isofs ext2 ext3 jbd mbcache ide_disk ide_generic
via82cxxx generic ide_core unix font vesaf
b cfbcopyarea cfbimgblt cfbfillrect
Sep 12 22:52:37 localhost kernel: Pid: 42, comm: kswapd0 Tainted: P
2.6.7-6-amd64-k8
Sep 12 22:52:37 localhost kernel: RIP: 0010:[drop_buffers+117/176]
801758c5{drop_buffers+117}
Sep 12 22:52:37 localhost kernel: RSP: 0018:01003fbf5bf8 EFLAGS: 00010206
Sep 12 22:52:37 localhost kernel: RAX: 01d21fec40d0 RBX: 0100016fa9d0
RCX: 01001fec4080
Sep 12 22:52:37 localhost kernel: RDX: 019e1fec40d0 RSI: 01003fbf5c08
RDI: 0100016fa9d0
Sep 12 22:52:37 localhost kernel: RBP: 01003fbf5de8 R08: 01001fec40d0
R09: 01001fec4080
Sep 12 22:52:37 localhost kernel: R10: 01001fec4080 R11:
R12: 0100212dee20
Sep 12 22:52:37 localhost kernel: R13: 01003fbf5e58 R14: 0100212dee20
R15: 0001
Sep 12 22:52:37 localhost kernel: FS: 002a97cf9380()
GS:803de2c0() knlGS:
Sep 12 22:52:37 localhost kernel: CS: 0010 DS: 0018 ES: 0018 CR0:
8005003b
Sep 12 22:52:37 localhost kernel: CR2: 019e1fec40d8 CR3: 00101000
CR4: 06e0
Sep 12 22:52:37 localhost kernel: Process kswapd0 (pid: 42, threadinfo
01003fbf4000, task 010037865000)
Sep 12 22:52:37 localhost kernel: Stack: 01003fbf5de8 80175965
0100016fa9d0
Sep 12 22:52:37 localhost kernel:01003fbf5de8 8015d0d6
8030c378 000101e81010
Sep 12 22:52:37 localhost kernel:0006 0246
Sep 12 22:52:37 localhost kernel: Call
Trace:80175965{try_to_free_buffers+101} 8015d0d6{shrink_li
st+934}
Sep 12 22:52:37 localhost kernel:
8015be97{__pagevec_release+23} 8015d506{shrink_cache+550
}
Sep 12 22:52:37 localhost kernel:
8015e1e3{balance_pgdat+371} 8015e39a{kswapd+250}
Sep 12 22:52:37 localhost kernel:
80132a20{autoremove_wake_function+0} 80130ee9{finish_tas
k_switch+89}
Sep 12 22:52:37 localhost kernel:
80132a20{autoremove_wake_function+0} 80130f51{schedule_t
ail+17}
Sep 12 22:52:37 localhost kernel:8011226f{child_rip+8}
8015e2a0{kswapd+0}
Sep 12 22:52:37 localhost kernel:80112267{child_rip+0}
Sep 12 22:52:37 localhost kernel:
Sep 12 22:52:37 localhost kernel: Code: 48 89 42 08 48 89 10 4d 89 40 08 4c
89 41 50 4d 39 d1 4c 89
Sep 12 22:52:37 localhost kernel: 6note: kswapd0[42] exited with
preempt_count 1
Any ideas out there...
MSI NEO-K8T FSR (If I remembered correctly) with Athlon 64 3000+
Soundblaster Live 5.1
MSI FX5600 TD 128
Twinmos PC3200 Dual Pack (1024) RAM
2 SATA Drives + 3 PATA Drives + Plextor PX-712A
Texas Intruments based Firewire card.
--
.O. Scream, Scream like the silence of the bits.
..O Dead lies the flag by the feet of the cold one.
OOO Freedom WILL break the walls of mammon.
pgpULKf59lwiy.pgp
Description: PGP signature
Re: Installation Problems
I had a go with the monolithic mini and unfortunately I get the same thing, no drivers found for my built in NIC, only my firewire ports found. Would you have to manually configure this somehow? Frederik Schueler wrote: Hi, the nic-extra-modules udeb has the via-velocity module. Try installing with the monolithic mini.iso. Greetings Frederik Schueler On Mon, Sep 13, 2004 at 07:54:00AM +0100, Mark Collin wrote: I have tried to install AMD64 Sid onto my machine but am having problems finding a working lan driver. I have an Abit AV8 with built in Via Gigabit LAN Ethernet card, unfortunately the Via Rhine drivers don't seem to be working. I have had a hunt around but cannot find any drivers for the Via Velocity 6122 chip. has anybody else tried to install on this board who can give me a few pointers, or does anybody know where I can find drivers that will work with this chip.
Re: Sound modules problème with kde !
On Wed, Sep 15, 2004 at 01:11:28PM +0200, Ludovic watteaux wrote: modprobe snd-via82xx Try snd-via82xx dxs_support=1 -- Raul
Is AMD64 Debian port suitable for production servers
Hello, I need to choose a stable software/hardware server solution based on Debian distribution. I'm planning to buy a 64-bit system (MB GigaByte K8VT800, AMD Athlon 64, socket 754, chipset VIA K8T800+8237 with SATA disks). According to the compatibility list http://alioth.debian.org/docman/view.php/30192/27/mainboards.html the above-mentioned motherboard should work in Linux without problems. I would like to ask if Debian AMD64 port is stable enough for production environments (with the latest kernel). Could you describe your experiences and stability problems with your AMD64 production servers? Do you think Intel P4 (and IA32 MB) is still more suitable for stable servers? All help would be highly appreciated. Pavol -- ___ [EMAIL PROTECTED] [http://trip.sk/wilder/] [talker: ttt.sk 5678] [ICQ:133403556] signature.asc Description: Digital signature
Success report Thunder K8S/AMD-8111/3ware 8506/Broadcomm 5700
Greetings -- A big thank you to everyone who has worked hard to get this port running! It's a thrill to be back on Debian. I just switched my SuSE 9.0 system over, using the cross-install instructions at http://www.burgettsys.com/stories/59455/ and the debian-amd64-howto. Documentation suggestions: It might be really useful for people crossing over if the debian-amd64-howto contained these very simple instructions for crossing over. Since Debian is getting support for amd64 later than some of the other distros, there may be others who start out with a commercial distro and switch. Mention that you need module-init-tools, or no modules will load. Installation problems: There were various small problems with debootstrap -- init scripts retained the FAKE version after install, console-data didn't install, base-config needed to be rerun -- but the problems self-corrected on reinstalling these packages. tasksel never managed to actually install anything. Kernel issues: I kept making kernels that oopsed right at the outset while starting to boot, possibly because I built CONFIG_X86_MSR and CONFIG_X86_CPUID into the kernel (not confirmed). Debian's (Broadcomm's) bcm5700-source driver also killed my system reliably; use tg3. I can't comment on stability at this point, but things are looking good! Cheers, David
Re: Is AMD64 Debian port suitable for production servers
On Tue, 2004-09-14 at 22:06 +0200, Pavol Luptak wrote: I need to choose a stable software/hardware server solution based on Debian distribution. What sort of server will it be? What particular software set do you need to run on it? I've a related question. Are the source packages for Debian amd64 coming from 'testing' or 'unstable'? In honesty I rarely have much trouble with systems running 'testing' with parts of 'unstable' and even 'experimental'. The occasional breakage has been downgradeable... Perhaps for a very important production server you should have both a staging system and the real thing, so that you can test updates on the staging box before putting them onto the deployment server. Maybe that could be done with a chroot? Has anyone tried something like this in real life? -- Karl Hegbloom (o_ mailto:[EMAIL PROTECTED] //\ jabber:[EMAIL PROTECTED] V_/_ yahoo:karlheg
Re: Is AMD64 Debian port suitable for production servers
On Tue, 2004-09-14 at 14:17 -0700, Karl Hegbloom wrote: Perhaps for a very important production server you should have both a staging system and the real thing, so that you can test updates on the staging box before putting them onto the deployment server. Maybe that could be done with a chroot? Has anyone tried something like this in real life? Doesn't 'rpm' have some sort of rollback feature? It would cool to have something like that for 'apt'/'dpkg'... perhaps all you really need to do is back up the conffiles, and 'dpkg-repack' or simply keep backups of the relevant files in your /var/cache/apt/archives? -- Karl Hegbloom (o_ mailto:[EMAIL PROTECTED] //\ jabber:[EMAIL PROTECTED] V_/_ yahoo:karlheg
Re: Installing from SuSE
David Liontooth wrote: I'd like to install Debian on an amd64 currently running SuSE. It doesn't have a CD or floppy drive, so the simplest would be to install from within the current installation. What can I do? http://www.hadrons.org/~guillem/debian/debtakeover/README I used this process just this last weekend on an i686 system to convert it to Debian. I was very much impressed by how well everything worked. The author must have spent a tremendous amount of time working through the details. Very impressive work. The script is written quite cleanly and is easy to follow through the internals. It is not perfect. But certainly close enough to finish the job by hand. In particular in my case the password file remained the old one and did not have all of the pseudo users needed for the new system such as postdrop and others. Also nothing is really done with respect to the kernel and the one from the previous system is left in place. The script was written to convert remote co-located servers. Before using this on a live production system you would want to have tried it and tested it thoroughly on an offline system close at hand. Only when you are convinced that it will do what you want should you commit to converting a remote system with this method. I have not tried this process for amd64. But if the system is a 64-bit amd64 system then I believe this should work. But if it is a 32-bit i686 system then the bootstrap process will not work. Or rather it will work to convert it to another i686 system. Remember that the kernel is left as is in this process. Back in February I used John Goerzen's amd64_pure_test http://people.debian.org/%7Ejgoerzen/amd64_pure_test.tar.bz2 to install into a chroot, which worked fine, but this partition is no more. Is it possible to install from a mounted iso image, such as sid-amd64-netboot.iso? The instructions in debian-amd64-howto.html for installing into a chroot assume you're already running Debian. The only step that is interesting on non-debian systems is getting debootstrap or cdebootstrap. You will need to download the tar.gz file and unpack it manually and build everything up manually. After that you should be able to proceed the same regardless of system. You can get the tar.gz file from the debian.org servers. http://packages.debian.org/unstable/admin/debootstrap Look near the bottom for the link which currently says [debootstrap_0.2.44.tar.gz]. Another resource that you might find useful is the following. It also documents how to build a system from a chroot. http://www.inittab.de/manuals/debootstrap.html Bob pgpNCUyPy5a1h.pgp Description: PGP signature
Re: pivot_root: No such file or directory
In The Night wrote: Hmmm I've tried that. I've tried mkinitrd -r /dev/sdb1 too... The problem seems to be me having root on a SATA-drive mkinitrd fails to find the sata driver necessary to mount your root disk. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=263169 Workaround is to add your sata driver to /etc/mkinitrd/modules and rebuild the initrd. What I _really_ do not understand is why this is not seen as a serious problem. Regards Harri
