DSL modem support in Fedora Core needs system-config-network support.
by David Woodhouse
(Originally sent to fedora-config-list but trapped for moderation, and I
may get volunteers here too...)
Fedora Core 3 supports PPP over ATM (PPPoA) with any DSL modem which the
kernel can use as an ATM device -- currently that's only USB modems
based on the Alcatel SpeedTouch chipset, but we're working on more
hardware drivers.
The updated packages in rawhide also support PPP over Ethernet over ATM.
(PPPoE with a real DSL modem, not over _real_ Ethernet to an external
DSL modem/bridge). That should work fine in FC3 too if you update your
rp-pppoe and install linux-atm packages from the yum repo at
ftp://ftp.infradead.org/pub/linux-atm/
To connect, first you need to install the firmware for your modem
into /lib/firmware (see the speedtouch-firmware.nosrc.rpm in the same
FTP directory) and then you need to configure it. You can just set up an
xDSL connection with system-config-network, then modify the resulting
configuation file /etc/sysconfig/network-scripts/ifcfg-ppp0 as follows.
For PPPoA, remove the 'ETH=' line, and add something like:
LINUX_PLUGIN=pppoatm.so
VCI=0
VPI=38
Replace the '0' and '38' with the appropriate values for your ISP.
There's
a table at http://linux-
usb.sourceforge.net/SpeedTouch/faq/index.html#q12
which may help.
For PPPoE, also remove the 'ETH=' line, and add:
LINUX_PLUGIN=rp-pppoe.so
BR2684DEV=0
VCI=0
VPI=38
(again with corrected VCI= and VPI= values).
It would be useful if system-config-network could do that for you. Any
volunteers for doing that? There's an update for the 'New Device' UI at
http://david.woodhou.se/ADSLInterfaceDruid.glade but I don't talk
Python, and system-config-network from CVS doesn't even build at the
moment due to autocrap problems.
All we need to do is make 'DSL modem' one of the options in the newly-
renamed 'Hardware device' box. Then if 'DSL modem' isn't chosen, shade
out the options for VCI, VPI and protocol. If it _is_ chosen, then write
out the config file according to the above instructions.
The UI for _editing_ devices also wants to be updated similarly.
It might also be useful to extend the providerdb with VPI/VCI/proto
information for various ISPs.
In the longer term, kudzu could perhaps learn to look
in /proc/net/atm/devices for ATM-capable devices, but that wouldn't show
up a SpeedTouch modem before its firmware is present anyway, so I
wouldn't want that to be the _only_ way the user can choose to use a DSL
modem.
--
dwmw2
19 years, 2 months
Re: slow hard drives crushing interactivity
by Phil Anderson
On Mon, 2005-01-24 at 18:29 -0500, Sean wrote:
> On Mon, January 24, 2005 6:01 pm, Havoc Pennington said:
>
> > Maybe a cap on process size, so there can be 1G virtual memory but
> > an
> > individual app can only use 512M?
>
> This already exists of course, you can set a ulimit on RSS and virtual
> memory size.
The kernel doesn't enforce RSS limits. See bug 133675.
Phil
----
http://www.pza.net.au/
19 years, 2 months
FC4 with localized firefox (wishlist)
by Josep Puigdemont
Hi,
Here it is my short wish list for FC4, if I may send one ;-)
I don't know if this has been mentioned before or not, but I for one
would like to see localized versions of Firefox for each installed
language, by default.
I don't know if that's technically very hard or not, though.
It's a pity to install Fedora (FC3) in your language, and see that the
most used application on the desktop is still in English (and Firefox is
the default browser). This renders the desktop _unusable_ for many
users, imho.
A part from that, congratulations, and keep up the good work!
/Josep
19 years, 2 months
problems with xen and kmodule
by Luciano Miguel Ferreira Rocha
On one of my machines, kmodule under xen gets stuck in an infinite loop:
rt_sigprocmask(SIG_SETMASK, ~[], [], 8) = 0
vm86old(0x806a94c) = -1 ENOSYS (Function not
implemented)
rt_sigprocmask(SIG_SETMASK, ~[], [], 8) = 0
vm86old(0x806a94c) = -1 ENOSYS (Function not
implemented)
....
(I can ^C it, when rc.sysinit starts, causing the script to exit and
init to continue to runlevel 3.)
Without xen, it outputs the following:
OTHER i2c-viapro
OTHER parport_pc
NETWORK via-rhine
AUDIO snd-via82xx
USB uhci-hcd
USB uhci-hcd
lspci:
00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 02)
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 22)
00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 10)
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
00:07.3 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 10)
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 20)
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 43)
01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2
Ultra] (rev 15)
cat /proc/cpuinfo:
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 3
model name : AMD Duron(tm) Processor
stepping : 0
cpu MHz : 700.053
cache size : 64 KB
fdiv_bug : no
hlt_bug : yes
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 mmx fxsr pni syscall mmxext 3dnowext 3dnow
bogomips : 1399.19
Regards,
Luciano Rocha
--
2/16
19 years, 2 months
gcc bug in fc 3
by Richard Hubbell
I installed a plain vanilla FC3, it only has xdm and xfce, no gnome or kde.
I was unable to run neither mozilla (dies in PR_dtoa) nor firefox
(dies in JS_dtostr).
Digging and digging I found out that gcc seems to be the problem, maybe.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17560
The only part that doesn't fit is that I wasn't using any optimizations
as far as I know, unless the they occur even with --enable-debug
I tried a Makefile patch I ran across that explicitly turns off optimizations
for prdtoa.c. The problem shows up later during the build when PR_dtoa
gets used by shlibsign.
Anyone know what's going wrong? Please tell me I just need to install
some package to fix this.
tia,
Richard
19 years, 2 months
Help correct Fedora s390 running under VM
by Sysadmin cokzl
> I am run (Fedora Core release Rawhide (Rawhide)Kernel 2.6.10-1.1103_FC4 on
> an s390)
> from vm/esa on s390, and i am see on console:
>
>
****************************************************************************
> ***********
> Booting default (linux)...
> Linux version 2.6.10-1.1103_FC4 (bhcompile(a)spade.z900.redhat.com) (gcc
> version
> .4.3 20050113 (Red Hat 3.4.3-15)) #1 SMP Wed Jan 19 20:40:50 EST 2005
> We are running under VM (31 bit mode)
> This machine has no IEEE fpu
> Built 1 zonelists
> Kernel command line: root=LABEL=/1 BOOT_IMAGE=0
> PID hash table entries: 1024 (order: 10, 16384 bytes)
> Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
> Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
> Memory: 124544k/131072k available (1874k kernel code, 0k reserved, 605k
> data, 1
> 8k init)
> Security Framework v1.0.0 initialized
> SELinux: Initializing.
> SELinux: Starting in permissive mode
> selinux_register_security: Registering secondary module capability
> Capability LSM initialized as secondary
> Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
> Detected 1 CPU's
> Boot cpu address 0
> cpu 0 phys_idx=0 vers=FF ident=100003 machine=9672 unused=0000
> Brought up 1 CPUs
> checking if image is initramfs... it is
> Freeing initrd memory: 899k freed
> debug: Initialization complete
> NET: Registered protocol family 16
>
****************************************************************************
> ***************
> and here cycling
> i am do command vm/esa:
> trace all
> and i see:
> TRACE ALL
> HCPTRI1027I An active trace set has turned RUN off.
> B
> -> 001D196E' SLR 1F33 CC 2
> B
> 001D1970' CS BA342000 002E8454 CC 1
> B
> 001D1974' ???? A744FFFB 0057AD33 CC 1
> B
> -> 001D196A' DIAG 83000044 00000044 CC 1
> B
> 001D196E' SLR 1F33 CC 2
> B
> 001D1970' CS BA342000 002E8454 CC 1
> B
> 001D1974' ???? A744FFFB 0057AD33 CC 1
> B
> -> 001D196A' DIAG 83000044 00000044 CC 1
> B
> 001D196E' SLR 1F33 CC 2
> B
> 001D1970' CS BA342000 002E8454 CC 1
> B
> 001D1974' ???? A744FFFB 0057AD33 CC 1
> B
> -> 001D196A' DIAG 83000044 00000044 CC 1
> B
> 001D196E' SLR 1F33 CC 2
> B
> 001D1970' CS BA342000 002E8454 CC 1
> B
> 001D1974' ???? A744FFFB 0057AD33 CC 1
>
> i am do command vm/esa:
> STORE 001D1974 A7440002:
> and i see:
> CP ST 001D1974 A7440002
> Store complete.
>
> cio: Was not able to determine available CHSCs, cc=2.
> chsc_get_sch_descriptions: Error -22 while doing chsc; processing some
> machine c
> hecks may not work
> appldata info: mem-ops registered]
> appldata info: os-ops registered]
> appldata info: net_sum-ops registered]
> audit: initializing netlink socket (disabled)
> audit(1106763062.926:0): initialized
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> SELinux: Registering netfilter hooks
> Initializing Cryptographic API
> ksign: Installing public key data
> Loading keyring
> - Added public key A151D8E9D3A0BB
> - User ID: Red Hat, Inc. (Kernel Module GPG key)
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27
> Channel measurement facility using basic format (autodetected)
> cpi: no system name specified
> NET: Registered protocol family 2
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP established hash table entries: 8192 (order: 5, 131072 bytes)
> TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
> TCP: Hash tables configured (established 8192 bind 8192)
> Initializing IPsec netlink socket
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Freeing unused kernel memory: 108k freed
> Red Hat nash version 4.2.0.1 starting
> Mounted /proc filesystem
........................................
> and so on
>
> and i see:
> Fedora Core release Rawhide (Rawhide)
> Kernel 2.6.10-1.1103_FC4 on an s390
>
> cokzlb login:
> HELP correct; improve; reform; repair BUG
>
19 years, 2 months
slow hard drives crushing interactivity
by Havoc Pennington
Hi,
On my IBM X31 laptop, the system entirely locks up when there's a lot of
disk access, some common situations are:
- when getting heavily into swap due to a runaway process
- when running rpm/yum
It's not *technically* locked up (i.e. if you wait long enough it will
come back) but in practice you have to reboot if a process has a memory
leak, and you can't do any work while running yum.
I have 512M of physical memory. I tried reducing swap from 1G to 256M so
runaway processes wouldn't require a reboot, but I just now had a
runaway process and discovered that less swap helps a little bit (you
can at least move the mouse pointer) but I still had to reboot because
it was taking multiple minutes to get a window open to run "killall" and
the root login times out before the Password: prompt comes up.
Some people with real hard drives instead of slow-ass laptop drives say
this doesn't happen to them.
Is there any solution (that we can enable by default/automatically, not
much of a solution otherwise)? Right now it's sort of like running an OS
without protected memory.
A bad solution (since most people won't know about it) might be a hotkey
that says "massively lower the priority of any process that's doing a
lot of disk access at the moment" or something. Or just a "kill any
process using more memory than I have physical memory," I don't know.
Maybe a cap on process size, so there can be 1G virtual memory but an
individual app can only use 512M? Maybe when a process reaches 512M we
could suspend it and ask the user whether to
let it grow further? With a kernel event when processes pass a certain
size you could even
do that heuristically (with races) by implementing the "kill -STOP" in
userspace in response to an event.
Would it help to mlock() the X server, window manager, and panel ;-)
Or is it just VM tuning that's needed?
If there's no automatic way to make this work, maybe there's at least a
way to key off a single global desktop vs. server flag rather than
requiring more detailed tuning?
Havoc
19 years, 2 months
Problems with SG_IO ioctls on sd device (verses sg device)
by Burn Alting
All,
I need help. I am using ftp.kernel.org's linux-2.6.10 on a Fedora
Core 3 system. I eventually want my code to work on a 'clean'
Fedora Core system, but I have put the ftp.kernel.org's kernel
up so I can cross-test the same devices with /dev/sgX.
I have a problem when I use /dev/sdX as opposed to /dev/sgX (eg /dev/sda
compared to /dev/sg0). I am setting up SCSI write commands of arbitrary
size, in an sg_io_hdr_t and sending the command to the device with a
SG_IO ioctl call. I am using a LSI Logic LSIFC929 as the HBA in a Dual
Xeon server and a raid as the target. I can issue writes up to 2048
blocks in size to /dev/sg0 but when I write this many to /dev/sda (with
the same code), it fails.
The failure has something to do with the __bio_add_page() routine
in fs/bio.c. I am sailing in totally uncharted waters in this code,
hence my call for help.
Firstly, SHOULD an SG_IO ioctl() call sent to a /dev/sg device
work fine and NOT work when the same SG_IO ioctl() call be sent
to /dev/sda. I realise that the ioctl() calls execute different
code, but conceptually should they both generate the same command
to the device?
If they should, then I include some debug output below of a
simple program that set's the SG_RESERVED_SIZE to: 4194304,
allocates paged aligned memory and then forms a 512 block write to
location 1 on the target. Directly after a reboot of the kernel,
the ioctl() write to /dev/sda works, but the next time it fails
with an EINVAL result.
The following occurs when my write of say 512 blocks is sent
to /dev/sda.
drivers/block/scsi_ioctl.c:scsi_cmd_ioctl() gets called which in
the switch calls drivers/block/scsi_ioctl.c:sg_io().
Everything in sg_io() is fine until the call to blk_rq_map_user()
which returns -22 (EINVAL).
In the test of q->max_sectors is ok as is the length and buffer
existance.
rq = blk_get_request(q, rw, __GFP_WAIT);
is fine but bio = bio_map_user(q, NULL, uaddr, len, rw == READ);
returns an error status.
We get into fs/bio.c:bio_map_user() which calls __bio_map_user()
which is the problem.
For a 512 block write, we require 64 * PAGE_SIZE (it's 4K) so the code
in fs/bio.c:__bio_map_user() looks like
...
/*
* transfer and buffer must be aligned to at least hardsector
* size for now, in the future we can relax this restriction
*/
if ((uaddr & queue_dma_alignment(q)) || (len & queue_dma_alignment
(q))) {
printk("Q %p bad alignment\n", q);
return ERR_PTR(-EINVAL);
}
bio = bio_alloc(GFP_KERNEL, nr_pages);
if (!bio) {
printk("Q %p - no bio_alloc\n", q);
return ERR_PTR(-ENOMEM);
}
ret = -ENOMEM;
pages = kmalloc(nr_pages * sizeof(struct page *), GFP_KERNEL);
if (!pages) {
printk("Q %p - no kmalloc\n", q);
goto out;
}
down_read(¤t->mm->mmap_sem);
ret = get_user_pages(current, current->mm, uaddr, nr_pages,
write_to_vm, 0, pages, NULL);
up_read(¤t->mm->mmap_sem);
if (ret < nr_pages) {
printk("ret %d < nr_pages %d\n", ret, nr_pages);
goto out;
}
bio->bi_bdev = bdev;
offset = uaddr & ~PAGE_MASK;
printk("ret = %d offset = %d, nr_pages = %d, len = %u\n", ret,
offset, nr_pages, len);
for (i = 0; i < nr_pages; i++) {
unsigned int bytes = PAGE_SIZE - offset;
printk("i = %2d bytes %u len %u\n", i, bytes, len);
if (len <= 0)
break;
if (bytes > len)
bytes = len;
/*
* sorry...
*/
k = __bio_add_page(q, bio, pages[i], bytes, offset);
printk("__bio_add_page() returns = %d and bytes is %d\n", k,
bytes);
if (k < bytes)
break;
len -= bytes;
offset = 0;
}
printk("i = %d, nr_pages = %d, PAGE_SIZE %lu\n", i, nr_pages,
PAGE_SIZE);
/*
* release the pages we didn't map into the bio, if any
*/
while (i < nr_pages)
page_cache_release(pages[i++]);
kfree(pages);
/*
* set data direction, and check if mapped pages need bouncing
*/
if (!write_to_vm)
bio->bi_rw |= (1 << BIO_RW);
bio->bi_flags |= (1 << BIO_USER_MAPPED);
return bio;
out:
kfree(pages);
bio_put(bio);
printk("returns bad q %p\n", q);
return ERR_PTR(ret);
and the printk's show (for two successive 512 block writes - the first
works, but the second fails) ...
Jan 26 00:49:17 swtf2 kernel: ret = 64 offset = 0, nr_pages = 64, len =
262144
Jan 26 00:49:17 swtf2 kernel: i = 0 bytes 4096 len 262144
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 1 bytes 4096 len 258048
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 2 bytes 4096 len 253952
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 3 bytes 4096 len 249856
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 4 bytes 4096 len 245760
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 5 bytes 4096 len 241664
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 6 bytes 4096 len 237568
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 7 bytes 4096 len 233472
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 8 bytes 4096 len 229376
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 9 bytes 4096 len 225280
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 10 bytes 4096 len 221184
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 11 bytes 4096 len 217088
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 12 bytes 4096 len 212992
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 13 bytes 4096 len 208896
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 14 bytes 4096 len 204800
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 15 bytes 4096 len 200704
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 16 bytes 4096 len 196608
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 17 bytes 4096 len 192512
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 18 bytes 4096 len 188416
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 19 bytes 4096 len 184320
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 20 bytes 4096 len 180224
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 21 bytes 4096 len 176128
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 22 bytes 4096 len 172032
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 23 bytes 4096 len 167936
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 24 bytes 4096 len 163840
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 25 bytes 4096 len 159744
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 26 bytes 4096 len 155648
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 27 bytes 4096 len 151552
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 28 bytes 4096 len 147456
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 29 bytes 4096 len 143360
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 30 bytes 4096 len 139264
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 31 bytes 4096 len 135168
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 32 bytes 4096 len 131072
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 33 bytes 4096 len 126976
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 34 bytes 4096 len 122880
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 35 bytes 4096 len 118784
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 36 bytes 4096 len 114688
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 37 bytes 4096 len 110592
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 38 bytes 4096 len 106496
Jan 26 00:49:17 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:17 swtf2 kernel: i = 39 bytes 4096 len 102400
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 40 bytes 4096 len 98304
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 41 bytes 4096 len 94208
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 42 bytes 4096 len 90112
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 43 bytes 4096 len 86016
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 44 bytes 4096 len 81920
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 45 bytes 4096 len 77824
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 46 bytes 4096 len 73728
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 47 bytes 4096 len 69632
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 48 bytes 4096 len 65536
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 49 bytes 4096 len 61440
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 50 bytes 4096 len 57344
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 51 bytes 4096 len 53248
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 52 bytes 4096 len 49152
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 53 bytes 4096 len 45056
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 54 bytes 4096 len 40960
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 55 bytes 4096 len 36864
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 56 bytes 4096 len 32768
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 57 bytes 4096 len 28672
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 58 bytes 4096 len 24576
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 59 bytes 4096 len 20480
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 60 bytes 4096 len 16384
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 61 bytes 4096 len 12288
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 62 bytes 4096 len 8192
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 63 bytes 4096 len 4096
Jan 26 00:49:18 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:18 swtf2 kernel: i = 64, nr_pages = 64, PAGE_SIZE 4096
Jan 26 00:49:21 swtf2 kernel: ret = 64 offset = 0, nr_pages = 64, len =
262144
Jan 26 00:49:21 swtf2 kernel: i = 0 bytes 4096 len 262144
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 1 bytes 4096 len 258048
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 2 bytes 4096 len 253952
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 3 bytes 4096 len 249856
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 4 bytes 4096 len 245760
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 5 bytes 4096 len 241664
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 6 bytes 4096 len 237568
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 7 bytes 4096 len 233472
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 8 bytes 4096 len 229376
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 9 bytes 4096 len 225280
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 10 bytes 4096 len 221184
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 11 bytes 4096 len 217088
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 12 bytes 4096 len 212992
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 13 bytes 4096 len 208896
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 14 bytes 4096 len 204800
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 15 bytes 4096 len 200704
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 16 bytes 4096 len 196608
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 17 bytes 4096 len 192512
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 18 bytes 4096 len 188416
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 19 bytes 4096 len 184320
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 20 bytes 4096 len 180224
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 21 bytes 4096 len 176128
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 22 bytes 4096 len 172032
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 23 bytes 4096 len 167936
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 24 bytes 4096 len 163840
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 25 bytes 4096 len 159744
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 26 bytes 4096 len 155648
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 27 bytes 4096 len 151552
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 28 bytes 4096 len 147456
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 29 bytes 4096 len 143360
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 30 bytes 4096 len 139264
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 31 bytes 4096 len 135168
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 32 bytes 4096 len 131072
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 33 bytes 4096 len 126976
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 34 bytes 4096 len 122880
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 35 bytes 4096 len 118784
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 36 bytes 4096 len 114688
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 37 bytes 4096 len 110592
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 38 bytes 4096 len 106496
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 39 bytes 4096 len 102400
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 40 bytes 4096 len 98304
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 41 bytes 4096 len 94208
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 42 bytes 4096 len 90112
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 43 bytes 4096 len 86016
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 44 bytes 4096 len 81920
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 45 bytes 4096 len 77824
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 46 bytes 4096 len 73728
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 47 bytes 4096 len 69632
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 48 bytes 4096 len 65536
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 49 bytes 4096 len 61440
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 50 bytes 4096 len 57344
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 51 bytes 4096 len 53248
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 52 bytes 4096 len 49152
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 53 bytes 4096 len 45056
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 54 bytes 4096 len 40960
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 4096 and bytes
is 4096
Jan 26 00:49:21 swtf2 kernel: i = 55 bytes 4096 len 36864
Jan 26 00:49:21 swtf2 kernel: __bio_add_page() returns = 0 and bytes is
4096
Jan 26 00:49:21 swtf2 kernel: i = 55, nr_pages = 64, PAGE_SIZE 4096
Jan 26 00:49:21 swtf2 kernel: bio->bi_size = 225280 and len = 262144
Jan 26 00:49:21 swtf2 kernel: bio_map_user 2 q f7d5864c
Jan 26 00:49:21 swtf2 kernel: bio is the error
Jan 26 00:49:21 swtf2 kernel: blk_rq_map_user(Q f7d5864c) returns -22
Is anything more needed? Can anyone help?
Regards
Burn Alting
burn(a)goldweb.com.au
19 years, 2 months
loop device creation [was Re: udev: Directory for custom device nodes.]
by Chuck Anderson
On Tue, Jan 25, 2005 at 12:45:41PM +0100, Harald Hoyer wrote:
> tty1 tty2 tty3 tty4 tty5 tty6 loop0 loop1 loop2 loop3 loop4 loop5 loop6
> loop7 lp0 lp1 lp2 lp3 parport0 parport1 parport2 parport3 net/tun ppp
> console null zero
Why doesn't the loop module cause /dev/loop* device node creation at
load time? E.g. I have in /etc/modprobe.conf:
options loop max_loop=128
and /etc/fstab I have many of these:
/iso/FC3-i386-DVD.iso /mnt/heidelberg-i386-DVD iso9660 ro,loop=/dev/loop59,nosuid,nodev 0 0
Shouldn't rc.sysinit's "mount -a" cause all the loop devices to be
created automatically?
It seems to not work at boot time, but later a manual "mount -a" does
create the devices...
19 years, 2 months
Re: rawhide report: 20050121 changes
by Josh Boyer
On Sat, 2005-01-22 at 21:28 +0530, Rahul Sundaram wrote:
> Hi
>
Putting this back on the list because you make some good points and this
is a good discussion.
> >
> > That's because it's not always a technical issue. It's about choice.
> > Default does not mean "this has to be installed". It's just a default.
> > If I don't like the default, I should be given the option of installing
> > an alternative. And that is without needing to download another large
> > ISO after the fact because one didn't realize that KDE wasn't included
> > in Core anymore.
> >
>
> I dont think you read my previous mails completely. Let me explain
> this once more
>
> today fedora core is 4+1 cds. if you limit fedora core to the
> defaults and have it in 1 or 2 cds, you can have fedora extras or a
> subset of it on the rest of the cds. so the totally number of CD's you
> have to download as a KDE user still remains the same. Morever by
With you so far, but I have an issue I'll discuss below.
> limiting fedora core to the default others who are satisfied with the
> defaults and dont want to make choice initially either due to
> ignorance or due to lack of knowledge would be happy to stick with
> what they get. the rest download what they want and install what they
> want from fedora extras and elsewhere
>
> You still have the choice. the choices only increase with the
> formation of fedora extras.
If the Core install CDs give you an option to install from the Extras
CDs at _install_ time, and you have the choice to not accept the
default, then I could be OK with that.
However, my main concern with moving KDE to Extras is not ISO
organization. It's more of a maintainership issue. This whole thread
started because some packages were removed from Core, and then the
community found out that quite a few of those packages were orphaned.
KDE is a large package to maintain both because of it's code size and
it's large user base. Someone from the community maybe well be able to
do the job, but right now KDE is released and maintained as a part of
Core. It has a maintainer, it's part of the daily, weekly, whatever
builds and it probably gets at least some QA testing.
I realize that Fedora is officially an unsupported distribution, but the
fact remains that the kind folks at Red Hat still work on this quite a
bit. If it's moved to Extras and needs a new maintainer (which may not
be the case), how quickly will it be picked up? Who knows?
>
> fedora core however has a defined goal. its called "core" for a reason
> and all I am asking for is for the fedora project to implement that
> goal for FC4. Fedora installer should make it easy for anyone to
> install updates or add repositories and manage to have atleast the
> same software before the formation of fedora extras
>
Could you kindly point me to where the "defined goal of including only
defaults" is stated? I can't seem to find it anywhere. In fact, I find
statements all over the Fedora webpage that are contrary to that:
From: http://fedora.redhat.com/about/
"The goal of The Fedora Project is to work with the Linux community to
build a complete, general purpose operating system exclusively from open
source software."
and
"Fedora Core is intended to be a logical upgrade path for previous users
of Red Hat Linux whose needs are consistent with the objectives of the
Fedora Project."
From: http://fedora.redhat.com/about/objectives.html
"Include a range of popular packages, beyond those included in Red Hat's
commercially supported products. (Limited, of course, to packages that
Red Hat can legally provide; also limited to quality packages as defined
by our standards.)"
I see nothing about Core only containing defaults. Maybe I'm missing it
somewhere. Do you have a link to it? I'm not saying it's not a decent
goal to have, but that I just can't find it anywhere.
If all you want is to reorganize the ISOs so that all the default
options can be on 1 or 2 CDs, that's fine with me. As long as the
installer has the option of installing from the "non-default" CDs as
well.
josh
19 years, 2 months
