a= 1 (on)
keepsettings = 0 (off)
readonly = 0 (off)
readahead= 256 (on)
geometry = 16383/255/63, sectors = 78140160, start = 0
> > Can you look at this closer?
>
> Will do.
>
> Thanks for reporting,
>
Thanks for replay.
With regards,
Remigiusz Świc
the event is sent, the drive is supposed to be
> ready to be used.
>
I don't think that is the kernel problem. I have downgraded my kernel
to 2.6.12, 2.6.12.3, 2.6.13 and with version of hdparm and udev in sid
I still was seeing the same errors in dmesg.
With regards,
Remigiusz Świc
Package: hdparm
Version: 6.3-3
Severity: grave
During boot I see errors in dmesg. I've done little investigation
and found that is not problem with my hard drive, but only with
hdparm which is starting by udev.
Errors look like that and I find them only at start of udev:
hda: dma_intr: status=0x58
Package: linux-image-2.6.17-2-xen-686
Version: 2.6.17-9
Severity: important
Hi!
When I want to boot domU (only one) the dom0 crashes with kernel panic
and system reboots. The output is very similiar to this (this is not
my photo):
http://www.osp.fi/xen1.jpg
http://www.osp.fi/xen2.jpg
http://www.
Package: libcupsys2
Version: 1.1.99.b1-2
Severity: important
Problem occured during installation process of cupsys-bsd:
Setting up cupsys-bsd (1.1.23-15) ...
ln: accessing `/usr/share/doc/cupsys-bsd': Too many levels of symbolic links
dpkg: error processing cupsys-bsd (--configure):
subprocess po
5 matches
Mail list logo
