Ultra10 / woody / 120 GB HD / fdisk and geometry
Hi, I'm trying to put a 120GB ATA drive im my ultra 10 running stable with a 2.4.19 kernel A probe-ide shows correctly the drive. The kernel seems to be able to read the geometry as shown below : [EMAIL PROTECTED]:~$ cat /proc/ide/hdc/model Maxtor 6Y120L0 [EMAIL PROTECTED]:~$ cat /proc/ide/hdc/geometry physical 238216/16/63 logical 238216/16/63 But fdisk doesn't want to let me specify a custom geometry (typing ? doesn't do anything) : thething:/home/nath# fdisk -v fdisk v2.11n thething:/home/nath# fdisk /dev/hdc [...] Command (m for help): s Building a new sun disklabel. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. [...] Select type (? for auto, 0 for custom): ? Select type (? for auto, 0 for custom): ? Select type (? for auto, 0 for custom): 0 Heads (1-1024, default 16): 16 Sectors/track (1-1024, default 63): 63 Cylinders (1-65535, default 41606): 238216 Value out of range. Cylinders (1-65535, default 41606): I understand that 238216 65535 and that fdisk can't really accept 238216 as an answer :) but how could I partitionate my hard drive ? If I use the values given by fdisk, I end with a 20GB-like partition scheme, while I'd like to be able to fill up all those GBs :) Thanks in advance, Nathanaël Camelot -- mail : [EMAIL PROTECTED]
Re: Losing my mind, RAID1 on Sparc completely broken?
I'm having the exact same problem. Check out the thread starting with http://lists.debian.org/debian-sparc/2004/debian-sparc-200402/msg00077.html. booting with nodma has made my ide subsystem completely stable, including an md raid1 mirror pair. I'm still trying to get the bug workaround described in that thread working, but my source has been out of town, so I'm stalled for now. Marc
v100 ethernet problems
I'm seeing several problems with the network on my v100 machine. I'm running 2.4.21. I compared the sources between this and 2.4.25, and it looks like nothing relevant has changed, but I'm willing to try a newer kernel if someone tells me it fixes any of these problems. Problem 1: Somewhat correlated with periods of moderate to heavy traffic, the interface stops working and I get an infinite series of these: NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out NETDEV WATCHDOG: eth1: transmit timed out if I log into the serial console and ifdown/ifup the interface, everything works ok until it happens again. Problem 2: Sometimes, after many timeouts as in problem 1, the host panics: \|/ \|/ @'/ .. \`@ /_| \__/ |_\ \__U_/ swapper(0): Kernel bad sw trap 5 TSTATE: 004480f09600 TPC: 00428cb0 TNPC: 00428cb4 Y: Not tainted Using defaults from ksymoops -t elf32-sparc -a sparc g0: 002d g1: g2: g3: f800659b g4: f800 g5: 1de2 g6: 00414000 g7: o0: o1: 0001 o2: 003f o3: 007ab000 o4: 007ab230 o5: sp: 00417091 ret_pc: 00428be8 l0: f80066ff8220 l1: f8006783 l2: f8006058e010 l3: 000f l4: f80067eb8820 l5: 0003 l6: 0003 l7: f800650a7650 i0: 1fff i1: f80067831de2 i2: 0001 i3: 0001 i4: 001b i5: 06898702 i6: 00417151 i7: 005463f8 Caller[005463f8] Caller[005f9df0] Caller[005f0c8c] Caller[0044de84] Caller[0040ef40] Caller[0041a504] Caller[007206f4] Caller[00404638] Caller[] Instruction DUMP: 10680004 0100 9194c000 91d02005 9194c000 81cfe008 91316000 9de3bf40 83366000 ksymoops says: PC; 00428cb0 pci_map_single+110/120 = g6; 00414000 init_task_union+0/4000 o3; 007ab000 reserve.2+38/e0 o4; 007ab230 xtime+0/10 sp; 00417091 init_task_union+3091/4000 ret_pc; 00428be8 pci_map_single+48/120 i6; 00417151 init_task_union+3151/4000 i7; 005463f8 tulip_start_xmit+38/160 Trace; 005463f8 tulip_start_xmit+38/160 Trace; 005f9df0 qdisc_restart+50/120 Trace; 005f0c8c net_tx_action+ac/100 Trace; 0044de84 do_softirq+e4/100 Trace; 0040ef40 __handle_softirq+0/10 Trace; 0041a504 cpu_idle+44/60 Trace; 007206f4 start_kernel+1b4/1e0 Trace; 00404638 tlb_fixup_done+54/5c Trace; Before first symbol Code; 00428ca4 pci_map_single+104/120 _PC: Code; 00428ca4 pci_map_single+104/120 0: 10 68 00 04 unknown Code; 00428ca8 pci_map_single+108/120 4: 01 00 00 00 nop Code; 00428cac pci_map_single+10c/120 8: 91 94 c0 00 unknown Code; 00428cb0 pci_map_single+110/120 = c: 91 d0 20 05 ta 5 = Code; 00428cb4 pci_map_single+114/120 10: 91 94 c0 00 unknown Code; 00428cb8 pci_map_single+118/120 14: 81 cf e0 08 rett %i7 + 8 Code; 00428cbc pci_map_single+11c/120 18: 91 31 60 00 srl %g5, 0, %o0 Code; 00428cc0 pci_unmap_single+0/160 1c: 9d e3 bf 40 save %sp, -192, %sp Code; 00428cc4 pci_unmap_single+4/160 20: 83 36 60 00 srl %i1, 0, %g1 Problem 3: Full-duplex doesn't work right. At boot, the interface autonegotiates to 100baseTx-HD. If I use mii-tool to force it to full duplex, I see reduced throughput, and a transmit error on every packet is reported (but the packets are sent). Marc
Re: v100 ethernet problems
On Sun, 2004-03-14 at 17:41, Marc Horowitz wrote: Problem 3: Full-duplex doesn't work right. At boot, the interface autonegotiates to 100baseTx-HD. If I use mii-tool to force it to full duplex, I see reduced throughput, and a transmit error on every packet is reported (but the packets are sent). Marc My ultra2 did this when it was plugged into my old 10mbit switch(it went to 10 hd) If I forced it to 10 fd, it barely worked. Since I've gotten a new 100mbit switch, I haven't had any problems -- -Justin
Re: mutt / Bus error
On Sat, 2004-03-13 at 14:14, Ben Collins wrote: Try this: mv /usr/lib/v9 /usr/lib/v9-tmp ldconfig Then run mutt and see if it works after that. If so, file a bug on the libssl0.9.7 package regarding it's v9 library. Tried, and sorry: no changes, the bus error was still there. Contents of this v9 directory: u1:~# ls -la /usr/lib/v9/ -rw-r--r--1 root root807136 Nov 7 10:31 libcrypto.so.0.9.6 -rw-r--r--1 root root 1072592 Oct 16 23:07 libcrypto.so.0.9.7 -rw-r--r--1 root root187716 Nov 7 10:31 libssl.so.0.9.6 -rw-r--r--1 root root195032 Oct 16 23:07 libssl.so.0.9.7 regards, Olivier -- ___ Olivier Müller - PGP key ID: 0x0E84D2EA - Switzerland E-Mail: http://omx.ch/mail/ - AIM/iChat: swix3k
Kernel 2.{4,6} on sparc32
Hi, I've been trying to update my SparcStation 5 from the installation kernel of 2.2.0-sun4cdm to a 2.4 or a 2.6 kernel for the last 3 months or so (whenever the new libc6 went in), and have had pretty much zero sucess. If the kernel is above about 1.1Mb, I can't boot the kernel, and get something about the destination being too small, but if the kernel is the right size, I doesn't boot anyway. This happens to any kernel, not just 2.6.3. Booting 2.2.20 gives me: PROMLIB: obio_ranges 1 Booting Linux Booting 2.6.3 gives me: PROMLIB: obio_ranges 1 Watchdog reset Reseting ... The PROM version of the machine is, to my mind, extremly old, which may be why I can't boot anything newer than 2.2. ok .version Release 2.15 Version 5 created 95/03/29 14:21:55 [ Please CC me as I'm not subscribed. ] Thanks, -- Steve I've lost my sig!
