Processed: Re: Bug#286226: Compiler errors with new 2.4.27-6 (-5 works)
Processing commands for [EMAIL PROTECTED]: tag 286226 +patch Bug#286226: Compiler errors with new 2.4.27-6 (-5 works) There were no tags set. Tags added: patch tag 286226 +pending Bug#286226: Compiler errors with new 2.4.27-6 (-5 works) Tags were: patch Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#286226: Compiler errors with new 2.4.27-6 (-5 works)
tag 286226 +patch tag 286226 +pending thanks On Sat, Dec 18, 2004 at 04:38:15PM +0100, Rene Konasz wrote: Package: kernel-source-2.4.27 Version: 2.4.27-6 Severity: important Hello, I get compile errors on two different Systems (P4 and Opteron (compile only)) with 2.4.27-6, 2.4.27-5 and all before compile and run without any problem and still do, always the same kernel config, Systems are both up to date Sarge. make menuconfig (import kernel config, is in the mail attachment) fakeroot -- make-kpkg --revision=test.0.4 kernel_image init/main.o(.text.init+0x868): In function `start_kernel': : undefined reference to `acpi_early_init' make[1]: *** [vmlinux] Error 1 make[1]: Leaving directory `/usr/src/kernel-source-2.4.27' make: *** [stamp-build] Error 2 Hi Rene, thanks for reporting this bug, and thanks for including your kernel config. I have been able to reproduce the problem and believe that the attached patch from uptream resolves it. I will this patch in the next release. -- Horms
Bug#286628: Filesystem coruption. local attack for setuid root executable?
Package: unknow
Version: unknow
On Debian sarge net install whit ext3 filesystem i got somme verry
strange file and error. somme file read as follow:
?rwx-wS-wt 6743 1909420011 2288661400 3.7G 1962-09-28 08:23
?r-s-wSrwt 59484 2155108859 3093106996 3.8G 1951-08-27 16:14
b-wsr-sr-x 58990 2148981355 1947303819 165, 77 1920-03-04 05:03
c-wx-w--wT 58075 3390588804 4291936288 181, 122 1992-01-03 06:27
?--Sr--r-t 32243 3182936007 1421612276 2.7G 1961-05-16 20:05
?rwx-wsr-t 40822 3819429815 896982909 4.0G 1930-08-30 05:12
p-wS--x--x 61104 456274484 3143202295 419M 1952-04-16 01:20
?rwSrwSrwT 27385 3445454714 3915889634 2.8G 2009-06-27 23:08
?r--rwxrwt 45494 1042776226 3513874223 2.7G 2015-08-01 10:46
?-wS--x-wt 28663 2080074714 3750305767 3.6G 1989-08-16 08:13
s-ws-wSrwT 18770 1943752241 4021181408 3.7G 1918-11-18 14:58
they where all created by my user(uid 1000)
Could somme exectable be crafted to have set uid bit and
owner of uid 0?
i was also building a cvs checkout of wine. the first
build was successfull, then i make clean and make again.
it stop on that error:
async.c:75:19: warning: netdb.h: Value too large for defined data type
async.c:83:21: warning: resolv.h: No such device
i've never see somme thing like that before.
additionaly logs report:
hdb: dma_timer_expiry: dma status == 0x60
hdb: DMA timeout retry
hdb: timeout waiting for DMA
hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdb: drive not ready for command
init_special_inode: bogus i_mode (173005)
Cyclades driver 2.3.2.20 2004/02/25 18:14:16
built Nov 25 2004 04:25:23
init_special_inode: bogus i_mode (153723)
init_special_inode: bogus i_mode (77527)
init_special_inode: bogus i_mode (115045)
init_special_inode: bogus i_mode (173735)
init_special_inode: bogus i_mode (167666)
init_special_inode: bogus i_mode (71477)
init_special_inode: bogus i_mode (155213)
Whit the DMA timer expire, i look like a hardware probleme
but i've been runing other distribution before on this
system and i never got surch error.
Bug#277298: testing workaround
On Tue, Dec 21, 2004 at 09:32:19AM +0100, Geert Stappers wrote: On Tue, Dec 21, 2004 at 02:43:04AM +0100, Erik van Konijnenburg wrote: Tested on Dell GX280, ICH6 instead of ICH5; your workaround seems to work: framboos:~# hwclock --show Tue 21 Dec 2004 03:05:02 AM CET -0.672601 seconds framboos:~# hwclock-2.12 --show select() to /dev/rtc to wait for clock tick timed out framboos:~# Okay, that is the easy part :-) Does the workaround allow reboot without apci=off and without pressing Control-C ? That worked already, util-linux-2.12h has working timeout on rtc failures. In d-i rc2 the hang is gone, so the only motivation for the workaround would be to create a working hwclock. Just tested reboot: as expected the timeout error is gone now. Regards, Erik
Processed: Re: 2.6.9 kernel breaks kernel compilation
Processing commands for [EMAIL PROTECTED]: severity 282119 normal Bug#282119: 2.6.9 kernel breaks kernel compilation Severity set to `normal'. tags 282119 + moreinfo unreproducible Bug#282119: 2.6.9 kernel breaks kernel compilation Tags were: sid Tags added: moreinfo, unreproducible thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices
On Mon, Dec 20, 2004 at 02:52:50AM +0100, Goswin von Brederlow wrote:
Marc Singer [EMAIL PROTECTED] writes:
On running mdadm --assemble /dev/md0
mdadm[4247]: segfault at 002c rip 0804b19e rsp
db80 error 4
mdadm[4253]: segfault at 002c rip 0804b19e rsp
db80 error 4
That doesn't mean much. Unaligned access gets reported as such as
well for example.
Could you paste a gdb stack backtrace preverably after rebuilding
mdadm with debug info?
I've had a look at the mdadm side of this problem. It looks like it
is crashing because there is no configuration file. From mdadm.c
break;
case ASSEMBLE:
if (devs_found == 1 ident.uuid_set == 0
ident.super_minor == UnSet !scan ) {
/* Only a device has been given, so get details from config
file */
mddev_ident_t array_ident = conf_get_ident(configfile,
devlist-devname);
mdfd = open_mddev(devlist-devname, array_ident-autof);
The conf_get_ident() is returning 0 which is then dereferenced by the
open_mddev() call and segfault'ing. configfile is NULL because none
was given. AFAICT, configfile never defaults. And even if it did,
there is no config file on my machine.
I haven't yet looked into the code within the initrd to see what it
does. It is possible that the only way that my setup can work is if
the md driver is compiled in.
Still, I wonder about the ioctl errors that I see with fdisk.
Bug#286731: USB Support for old USB 1.0 devices broken in 2.6 kernels
Package: kernel Version: 2.6 Hello, I think there's a problem with the support for old USB devices in 2.6 kernels. I noticed it when upgraded from 2.4.27, where my Pinnacle PCTV USB (1.0) was performing nicely with package usbvision and got broken upon upgrade to kernel 2.6. Since then I get this in kern.log each time I try to run xawtv: Dec 21 21:19:10 casagrande kernel: /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision_probe: Pinnacle Studio PCTV USB (PAL) FM found Dec 21 21:19:10 casagrande kernel: /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision[0]: registered video device /dev/video0 Dec 21 21:19:10 casagrande kernel: /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision[0]: registered radio device /dev/radio0 Dec 21 21:19:10 casagrande kernel: usbcore: registered new driver USBVision Video Grabber Dec 21 21:19:10 casagrande kernel: /usr/src/usbvision-0.9.8/src/usbvision.c: USBVISION USB Video Device Driver for Linux : 0.9.8 for Linux kernels 2.4.19-2.4.27 + 2.6.0-2.6.9, compiled at Dec 21 2004, 18:15:58 Dec 21 21:19:21 casagrande kernel: /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision_isocIrq: usb_submit_urb failed: error -1 Dec 21 21:19:21 casagrande kernel: /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision_isocIrq: usb_submit_urb failed: error -1 Dec 21 21:21:09 casagrande kernel: usbcore: deregistering driver USBVision Video Grabber Also I get the following from lsusb command: cannot get string descriptor 1, error = Broken pipe(32) cannot get string descriptor 2, error = Broken pipe(32) cannot get string descriptor 3, error = Broken pipe(32) Bus 002 Device 002: ID 2304:0110 Pinnacle Systems, Inc. [hex] Language IDs: none (cannot get min. string descriptor; got len=-1, error=32:Broken pipe) Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.00 bDeviceClass0 Interface bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x2304 Pinnacle Systems, Inc. [hex] idProduct 0x0110 bcdDevice2.00 iManufacturer 1 iProduct2 iSerial 3 bNumConfigurations 1 cannot get config descriptor 0, Broken pipe (32) Language IDs: none (cannot get min. string descriptor; got len=-1, error=32:Broken pipe) And dmesg says this on boot: USB Universal Host Controller Interface driver v2.2 uhci_hcd :00:07.2: Intel Corp. 82371AB/EB/MB PIIX4 USB uhci_hcd :00:07.2: irq 9, io base ef80 uhci_hcd :00:07.2: new USB bus registered, assigned bus number 2 hub 2-0:1.0: USB hub found hub 2-0:1.0: 2 ports detected Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. usbcore: registered new driver usbhid usb 2-2: control timeout on ep0in usb 2-2: control timeout on ep0in usb 2-2: control timeout on ep0in usb 2-2: control timeout on ep0in usb 2-2: control timeout on ep0in usb 2-2: control timeout on ep0in usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -32 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 9 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 9 ret -32 usb 2-2: control timeout on ep0in usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -32 /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision_probe: Pinnacle Studio PCTV USB (PAL) FM found /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision[0]: registered video device /dev/video0 /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision[0]: registered radio device /dev/radio0 usbcore: registered new driver USBVision Video Grabber /usr/src/usbvision-0.9.8/src/usbvision.c: USBVISION USB Video Device Driver for Linux : 0.9.8 for Linux kernels 2.4.19-2.4.27 + 2.6.0-2.6.9, compiled at Dec 21 2004, 18:15:58 /src/usbvision-0.9.8/src/usbvision.c: usbvision_isocIrq: usb_submit_urb failed: error -1 /usr/src/usbvision-0.9.8/src/usbvision.c: usbvision_isocIrq: usb_submit_urb failed: error -1 usbcore: deregistering driver USBVision Video Grabber usb 2-2: control timeout on ep0in usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -32 usb 2-2: control timeout on ep0in usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -32 usb 2-2: control timeout on ep0in usb 2-2: usbfs: USBDEVFS_CONTROL failed cmd lsusb rqt 128 rq 6 len 256 ret -110 usb 2-2: usbfs:
kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes UNACCEPT
Rejected: Rejected: kernel-image-power3-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2.dsc: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power3_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-headers-2.6.9_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. === Despite being ACCEPTed, this package failed the database sanity checks at the time of install. This should only happen rarely and in corner-cases (a binary upload of a package which has since been melanie'd for example), so no code to do the necessary unaccept actions has been written. These actions (e.g. bug reopening, announcement rescinding, etc.) will have to be done by hand. Also, the files have been left in the accepted directory; please deal with them as well.
Bug#286733: initrd-tools: sg.ko required by SATA machine
Package: initrd-tools Version: 0.1.74 Severity: normal As request by one of the AMD64 developers: http://lists.debian.org/debian-amd64/2004/12/msg00477.html An SATA workstation requires sg.ko to boot properly. I had to roll our own initrd, but it'd be nice if the standard deb came with an initrd that had the right module. kernel-image-2.6.9-9-amd64-k8 Here's the requested output: $ lspci :00:06.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8111 PCI (rev 07) :00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-8111 LPC (rev 05) :00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-8111 IDE (rev 03) :00:07.2 SMBus: Advanced Micro Devices [AMD] AMD-8111 SMBus 2.0 (rev 02) :00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-8111 ACPI (rev 05) :00:07.5 Multimedia audio controller: Advanced Micro Devices [AMD] AMD-8111 AC97 Audio (rev 03) :00:0a.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) :00:0a.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) :00:0b.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) :00:0b.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :01:02.0 Unknown mass storage controller: Silicon Image, Inc. (formerly CMD Technology Inc) SiI 3512 [SATALink/SATARaid] Serial ATA Controller (rev 01) :01:03.0 USB Controller: NEC Corporation USB (rev 43) :01:03.1 USB Controller: NEC Corporation USB (rev 43) :01:03.2 USB Controller: NEC Corporation USB 2.0 (rev 04) :01:04.0 FireWire (IEEE 1394): Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) :03:01.0 Network controller: Texas Instruments ACX 111 54Mbps Wireless Interface :03:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet (rev 02) :08:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-8151 System Controller (rev 14) :08:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8151 AGP Bridge (rev 14) :08:03.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) :08:03.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) :08:04.0 PCI bridge: Advanced Micro Devices [AMD] AMD-8131 PCI-X Bridge (rev 12) :08:04.1 PIC: Advanced Micro Devices [AMD] AMD-8131 PCI-X APIC (rev 01) :09:00.0 VGA compatible controller: nVidia Corporation NV18GL [Quadro4 NVS AGP 8x] (rev c1) :13:04.0 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10) :13:04.1 SCSI storage controller: Adaptec AIC-7902B U320 (rev 10) $ lspci -n :00:06.0 0604: 1022:7460 (rev 07) :00:07.0 0601: 1022:7468 (rev 05) :00:07.1 0101: 1022:7469 (rev 03) :00:07.2 0c05: 1022:746a (rev 02) :00:07.3 0680: 1022:746b (rev 05) :00:07.5 0401: 1022:746d (rev 03) :00:0a.0 0604: 1022:7450 (rev 12) :00:0a.1 0800: 1022:7451 (rev 01) :00:0b.0 0604: 1022:7450 (rev 12) :00:0b.1 0800: 1022:7451 (rev 01) :00:18.0 0600: 1022:1100 :00:18.1 0600: 1022:1101 :00:18.2 0600: 1022:1102 :00:18.3 0600: 1022:1103 :01:02.0 0180: 1095:3512 (rev 01) :01:03.0 0c03: 1033:0035 (rev 43) :01:03.1 0c03: 1033:0035 (rev 43) :01:03.2 0c03: 1033:00e0 (rev 04) :01:04.0 0c00: 104c:8023 :03:01.0 0280: 104c:9066 :03:02.0 0200: 14e4:16a7 (rev 02) :08:00.0 0600: 1022:7454 (rev 14) :08:01.0 0604: 1022:7455 (rev 14) :08:03.0 0604: 1022:7450 (rev 12) :08:03.1 0800: 1022:7451 (rev 01) :08:04.0 0604: 1022:7450 (rev 12) :08:04.1 0800: 1022:7451 (rev 01) :09:00.0 0300: 10de:018a (rev c1) :13:04.0 0100: 9005:801d (rev 10) :13:04.1 0100: 9005:801d (rev 10) -- System Information: Debian Release: 3.1 Architecture: amd64 (x86_64) Kernel: Linux 2.6.9-9-amd64-k8 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages initrd-tools depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii cpio 2.5-1.1GNU cpio -- a program to manage ar ii cramfsprogs 1.1-6 Tools for CramFs (Compressed ROM F ii dash 0.5.1-3The Debian Almquist Shell ii fileutils 5.2.1-2The GNU file management utilities ii util-linux2.12l-1Miscellaneous system utilities -- no debconf information
Bug#286733: initrd-tools: sg.ko required by SATA machine
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The sg driver was used to access scsi scanners, scsi cd writers, etc. I don't have any experience with your hardware, but using sg to access your root disk is pretty unusual. Have you tried the sata_sil driver? Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFByJ7YUTlbRTxpHjcRAjsHAKCOP7xzJAM6q0brEpHDzPj4aYtM3ACfa4BY 0DSfIEotV+4eL+ewp7oaVtg= =uAP1 -END PGP SIGNATURE-
Bug#277298: confirming workaround
On Tue, Dec 21, 2004 at 12:54:55PM +0100, Erik van Konijnenburg wrote: On Tue, Dec 21, 2004 at 09:32:19AM +0100, Geert Stappers wrote: snip/ Okay, that is the easy part :-) Does the workaround allow reboot without apci=off and without pressing Control-C ? That worked already, util-linux-2.12h has working timeout on rtc failures. In d-i rc2 the hang is gone, so the only motivation for the workaround would be to create a working hwclock. Just tested reboot: as expected the timeout error is gone now. Yes, I confirm that workaround works fine. (including reboot) The manual page of hwclock says: --directisa is meaningful only on an ISA machine or an Alpha (which imple- ments enough of ISA to be, roughly speaking, an ISA machine for hwclock's purposes). For other machines, it has no effect. This option tells hwclock to use explicit I/O instructions to access the Hardware Clock. Without this option, hwclock will try to use the /dev/rtc device (which it assumes to be driven by the rtc device driver). If it is unable to open the device (for read), it will use the explicit I/O instructions anyway. The rtc device driver was new in Linux Release 2. So this bugreport, currently filed against kernel-source, is IMNSHO not bug a kernel bug. It is about special hardware that needs special treatment. And the special treatment is provided by the hwclock programm. Cheers Geert Stappers Erik: Dank je wel. None Dutch: Thank you very much. signature.asc Description: Digital signature
Re: Bug#286756: udev gets tmpfs kernel support test wrong
reassign 286756 kernel-source-2.6.9 On Dec 22, John R. McPherson [EMAIL PROTECTED] wrote: Debian sarge/x86, custom kernel 2.6.9. I built a kernel and didn't set CONFIG_TMPFS, and after installing the kernel and rebooting, udev mounts an unusable tmpfs over /dev, so no device files are accessible. The mount doesn't fail, but the This is a known kernel bug (mount is supposed to fail), but I tought that it had been fixed in 2.6.8 (2.6.9?). I'm reassigning this bug to the kernel package. (I also accept suggestions for a better test for tmpfs presence...) -- ciao, | Marco | [9974 spV5nrM59g86E] signature.asc Description: Digital signature
Bug#286733: initrd-tools: sg.ko required by SATA machine
--- Harald Dunkel [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The sg driver was used to access scsi scanners, scsi cd writers, etc. I don't have any experience with your hardware, but using sg to access your root disk is pretty unusual. Have you tried the sata_sil driver? Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFByJ7YUTlbRTxpHjcRAjsHAKCOP7xzJAM6q0brEpHDzPj4aYtM3ACfa4BY 0DSfIEotV+4eL+ewp7oaVtg= =uAP1 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#286756: udev gets tmpfs kernel support test wrong
On Wed, Dec 22, 2004 at 01:57:13AM +0100, Marco d'Itri wrote: reassign 286756 kernel-source-2.6.9 On Dec 22, John R. McPherson [EMAIL PROTECTED] wrote: Debian sarge/x86, custom kernel 2.6.9. I built a kernel and didn't set CONFIG_TMPFS, and after installing the kernel and rebooting, udev mounts an unusable tmpfs over /dev, so no device files are accessible. The mount doesn't fail, but the This is a known kernel bug (mount is supposed to fail), but I tought that it had been fixed in 2.6.8 (2.6.9?). I'm reassigning this bug to the kernel package. (I also accept suggestions for a better test for tmpfs presence...) If /proc/config.gz exists, you can 'zgrep TMPFS /proc/config.gz' and see if it is =y/m vs n. That won't help for kernels that don't have CONFIG_IKCONFIG_PROC set, so don't have a /proc/config.gz. But if the file exists, you can tell whether or not the kernel has tmpfs support. John McPherson
